Migrating from WordPress to Framer involves exporting your posts and pages, rebuilding the design in the Framer editor, mapping every URL with 301 redirects, and switching DNS at the end. Most marketing sites complete the move in one to three weeks and gain dramatic performance, security, and design control without sacrificing SEO equity.
Why Teams Leave WordPress for Framer
WordPress is the most-used website platform in the world, which is also why so many teams want to leave. Plugin sprawl, security patching, theme conflicts, slow page loads, and the constant tax of keeping a self-hosted stack alive consume bandwidth that should go into the product. Framer eliminates the operational overhead entirely: no plugins, no servers, no security patches, no theme conflicts.
The most common reasons teams migrate are speed, design control, and team productivity. WordPress requires a developer for most meaningful design changes. Framer lets a designer ship a hero update in 10 minutes. Page load times that took weeks of optimization on WordPress arrive out of the box on Framer because the platform serves pre-rendered static HTML from a global CDN.
For a side-by-side comparison, see our framer vs wordpress deep dive.
What You Can and Cannot Migrate
You can migrate pages, blog posts, images, navigation, forms, and most marketing content. WordPress exports cleanly through the built-in tools, and Framer accepts the data through a combination of CMS import and manual rebuild.
You cannot migrate WordPress plugins directly. Plugin functionality often has a Framer equivalent through built-in features or third-party integrations, but plugin code itself does not transfer. Common plugin replacements include built-in forms instead of Gravity Forms, native CMS instead of Advanced Custom Fields, and direct third-party integrations instead of plugin wrappers.
WooCommerce does not have a native Framer equivalent. If you run a WooCommerce store, either keep commerce on WordPress at a subdomain while moving marketing pages to Framer, or migrate to a dedicated commerce platform like Shopify and integrate it with Framer through embed code.
Step 1: Audit Your WordPress Site
Pull the full list of pages, posts, custom post types, and active plugins from the WordPress admin. Export Google Search Console data and Google Analytics for the past 12 months to identify top-performing URLs. Note which pages drive organic traffic, conversions, and revenue. These get rebuilt first and tested most thoroughly.
Save the audit as a spreadsheet with old URL, new URL, page type, traffic volume, and notes. This becomes the master plan for migration and the source of truth for redirects later.
Step 2: Export from WordPress
Use the built-in WordPress Tools > Export feature to generate an XML file containing posts, pages, and metadata. Choose all content to capture everything in one export. The XML file is your structured data source for the rebuild.
For images and media, the WordPress export does not bundle assets. Use a plugin like All-in-One WP Migration or simply mirror the wp-content/uploads folder via FTP. Keep the media in a folder structure that matches your content so you can locate images when rebuilding pages.
For custom post types, custom fields, and ACF data, you may need a more thorough export using a tool like WP All Export. Map the data structure to a Framer CMS schema before importing.
Step 3: Plan Your Framer Project Structure
Before building, decide your Framer project structure. Define breakpoints, brand variables, typography styles, and a shared component library. Set up CMS collections for any content type you have: blog posts, case studies, team members, products, and so on. Each WordPress post type maps to a Framer CMS collection.
For variable setup, see our framer variables guide. For CMS planning, see our framer cms complete guide.
Step 4: Rebuild the Design
Recreate pages in Framer using your new component library. Start with high-traffic pages from your audit. Match the URL slugs to original WordPress URLs where possible so redirects map cleanly. Reuse components ruthlessly to keep the build fast and the result consistent.
Most teams treat migration as a chance to refresh the design. WordPress sites often look dated because the original theme has aged or accumulated visual debt from plugin overrides. The Framer rebuild is a clean slate. Keep the information architecture stable so visitors find what they expect, but upgrade the visual language.
Step 5: Import Blog Posts to CMS
Map the WordPress XML fields to your Framer CMS collection schema. Common mappings: post_title to title, post_name to slug, post_date to publish date, post_content to body, post_excerpt to excerpt, featured image URL to hero image.
For a few dozen posts, manual paste works. For hundreds or thousands, use the Framer CMS API to bulk-import from a script that parses the XML and creates CMS items. See our framer cms api guide for the API workflow.
Convert WordPress shortcodes to plain HTML or Framer components before import. Shortcodes do not render on Framer, so leaving them in causes broken content.
Step 6: Recreate Forms
Inventory every form on the WordPress site. For each, note the fields, the destination (email, CRM, ESP), and any conditional logic. Rebuild each form in Framer using the built-in form component. Route submissions to the same destination using Framer native integrations or webhooks.
For form best practices, see our framer forms guide.
Step 7: Replace Plugin Functionality
Walk through your active plugin list and identify the Framer equivalent for each. Examples: Yoast SEO is replaced by Framer built-in SEO fields. Contact Form 7 is replaced by Framer Forms. Smush is unnecessary because Framer optimizes images automatically. Some plugins require a third-party tool: live chat keeps using Intercom or Crisp via embed code, for instance.
Document each replacement and the new integration path. This document becomes useful if you ever return to WordPress for any reason, or if a future team member asks how a particular feature works.
Step 8: SEO Setup
Configure SEO settings on every page: meta title, meta description, Open Graph image, canonical URL. Match the original WordPress values where they were strong and improve where they were weak. Generate a sitemap in Framer settings and prepare to submit it to Google Search Console after launch.
Verify your domain ownership in Search Console for the new Framer site before launch day. This lets you submit the sitemap immediately at launch and monitor crawl behavior in real time. For the full SEO playbook, see our framer SEO guide.
Step 9: Configure 301 Redirects
Use your URL audit to build a redirect map. Every old WordPress URL needs a 301 redirect to its new Framer URL. Framer supports redirects in project settings. Add every entry from the audit, including blog post URLs where the slug pattern might differ.
Test each redirect before launch. Visit the old URL with curl or a browser and verify the 301 status and the new destination. Missing or broken redirects are the most common cause of SEO loss after migration.
Step 10: Test and Launch
Run a full pre-launch QA. Walk through every page on desktop, tablet, and mobile. Test every form, link, CMS template, and integration. Run Lighthouse to confirm performance and accessibility scores. Use the Framer preview QR code for real-device testing.
When ready, switch DNS to point to Framer. Framer provides exact records in the publish settings. DNS propagation typically completes within an hour but can take up to 48 hours globally. Keep WordPress hosting active during this window so visitors mid-DNS-update do not see errors.
After full propagation, submit the sitemap in Search Console, monitor crawl errors for the first two weeks, and watch organic traffic. A well-migrated site sees no major traffic drop and often improves within three months due to better Core Web Vitals.
Common Mistakes to Avoid
The biggest mistake is skipping the redirect step. Every WordPress URL not redirected becomes a 404 for crawlers, losing the SEO equity that took years to build.
Another common mistake is forgetting custom post types. Pages and posts are obvious. Case studies, team members, testimonials, or products often live in custom post types that the standard export underweights. Audit these explicitly.
Underestimating image migration time is also common. A WordPress site with thousands of media files takes hours to transfer. Plan the asset migration as its own workstream.
Frequently Asked Questions
How long does a WordPress to Framer migration take?
For a marketing site with 20 pages and 100 blog posts, expect one to three weeks. Larger sites with custom post types, complex layouts, or hundreds of posts take four to six weeks.
Will my SEO suffer?
Not if you set up redirects properly and preserve meta tags. Most migrations see no traffic drop, and many see improvements within three months due to better Core Web Vitals on Framer.
Can I keep WooCommerce on WordPress and migrate the rest?
Yes. Host commerce on shop.yoursite.com with WordPress and serve marketing pages from www.yoursite.com on Framer. This hybrid is common and works well.
What happens to my WordPress plugins?
Plugins do not transfer. Each plugin needs a Framer equivalent: built-in features, third-party integrations, or custom code components. Audit your plugin list before migration.
How much does Framer cost compared to WordPress?
Framer plans start at $5 per site per month. WordPress hosting plus premium plugins typically costs $40 to $200 per month after the first year. See framer pricing for details.