Migrating from WordPress to Framer follows a 12-step process: audit your current site, back everything up, map your URLs and redirects, build the Framer project structure, export WordPress content as XML, convert it to CSV for Framer CMS, import and rebuild layouts, configure 301 redirects and SEO metadata, test on staging, switch DNS, and monitor post-launch. Done correctly, you keep your rankings, reduce maintenance overhead, and end up with a faster, more designable site. Done wrong, you lose organic traffic. This guide covers every step so you get it right the first time.
Whether you're a marketing lead, founder, designer, or engineer, you'll walk away with a clear timeline, checklists, tactical steps, SEO safeguards, and post-launch validation processes.
Key Takeaways
By the end of this guide you will be able to:
Evaluate if migrating to Framer is the right move for your site
Audit and prepare your WordPress site for migration
Export and restructure your content for Framer CMS
Rebuild layouts, import content, and configure redirects
Preserve SEO and maintain traffic through launch
Validate success with performance, traffic, and search analytics
Most competing guides leave these out: export/import tooling, detailed redirect planning, staging strategies, DNS transition options, and SEO stabilization checkpoints -- all included here.
Why Should You Migrate from WordPress to Framer?
Framer gives you faster page loads, cleaner design workflows, and zero plugin maintenance -- but it is not the right move for every site.
The performance difference is measurable. WordPress sites typically score 40-70 on PageSpeed, load in 3-8 seconds, make 80-150 HTTP requests, and weigh 3-8 MB per page. Framer sites routinely hit 85+ on PageSpeed, load in under 2 seconds, make 20-40 requests, and stay under 2 MB. That gap comes from Framer's static rendering, global CDN delivery, and the absence of plugin bloat.
Beyond speed, the cost structure shifts significantly. A typical WordPress site runs $1,900-$4,800 per year when you factor in hosting ($200-$600), premium plugins ($300-$800), maintenance and updates ($1,200-$3,000), and security/backup tools ($200-$400). Framer consolidates all of that to roughly $400-$1,400 per year, saving most teams $1,500-$3,400 annually.
Designers can also own more of the publishing workflow without waiting on developers for every layout change. In one migration we handled -- a 35-page marketing site with 120 blog posts -- the publishing workflow went from a multi-day process requiring developer involvement to same-day designer-led publishing.
That said, if your site depends on advanced WordPress functionality like WooCommerce, membership gating, or complex custom post types, migration requires careful scoping and possibly a hybrid setup where Framer handles the marketing site and a separate tool handles the app layer. If your team has zero Framer experience and a tight deadline under 4 weeks, the learning curve under pressure leads to mistakes. Migrate because it solves a real problem, not because Framer is trending.
What Should You Audit Before Starting the Migration?
Everything. A thorough pre-migration audit is the difference between a smooth transition and months of SEO recovery.
How Do You Inventory Your Existing WordPress Content?
Start by listing every asset that matters:
All page and post URLs
Custom post types and taxonomies
Active plugins and their specific roles (document each one -- you will need to find Framer alternatives or remove them)
Media library structure
SEO metadata (titles, descriptions, canonical tags)
Internal link structure
Run a full crawl of your site using Screaming Frog. We recommend Screaming Frog specifically because its CSV export maps cleanly to the redirect spreadsheet format you will need later. The crawl also surfaces orphaned pages, broken links, and metadata gaps you should fix during migration rather than carry over.
While you are auditing, take the opportunity to clean house. Delete spam comments, remove draft posts you will not migrate, clean up unused media, and deactivate unnecessary plugins. This reduces the volume of content you need to process and prevents you from carrying dead weight into the new site.
How Do You Benchmark Current Performance?
Before changing anything, record your baseline numbers:
Current SEO rankings and organic traffic (export from Google Search Console)
PageSpeed scores and Core Web Vitals
Bounce rates and key conversion metrics
These benchmarks are your comparison point for post-migration validation. Without them, you cannot objectively measure whether the migration helped or hurt.
How Long Will Your Migration Take?
This depends entirely on your site type. Based on migrations we have scoped and executed, here are realistic timeline estimates:
WordPress Site Type | Timeline | Complexity | Notes |
Blog (50-200 posts, basic theme) | 3-4 weeks | Medium | Content export is straightforward, design rebuild is the main effort |
Business site (10-30 pages, Contact Form 7) | 4-6 weeks | Medium | Page variety increases design time |
Marketing site (landing pages, Elementor/Divi) | 5-8 weeks | High | Page builder dependencies complicate migration |
Magazine/Publication (500+ posts, categories/tags) | 8-12 weeks | High | Phased approach required, CMS restructuring is critical |
Add 2-4 weeks if your team is learning Framer during migration, stakeholder approval cycles are slow, or content needs major rewrites.
For a more precise estimate: count your static pages (multiply by 2 hours each), CMS template pages (4 hours each), complex/custom pages (6 hours each), and blog posts to migrate (0.25 hours each). Add 8-16 hours for design system and component setup, 4-8 hours for CMS structure, and 6-10 hours for SEO and redirects. Multiply the total by 1.3 for a 30% buffer, then divide by 20 for a half-time weekly estimate or 40 for full-time.
How Do You Back Up Your WordPress Site?
A full backup is non-negotiable. If anything goes wrong during migration, this is your restore point.
Export the WordPress database (use phpMyAdmin or your hosting control panel)
Download all theme files
Download all plugin files
Export all media files (wp-content/uploads) -- use the Export Media Library plugin for bulk download
Create an XML export of your content via Tools > Export > All content
Store everything in at least two locations. Cloud storage plus a local copy is the minimum.
How Should You Plan Your URL Strategy and Redirect Map?
Your redirect map is the single most important SEO safeguard in the entire migration. Every old URL needs to either stay the same or 301 redirect to its new equivalent.
How Do You Build a Redirect Map?
Create a spreadsheet with columns for old URL, new URL, page type, priority, and notes:
Old URL | New URL | Page Type | Priority | Notes |
/blog/my-post | /blog/my-post | CMS | Medium | Keep same slug |
/services/ux | /ux-services | Static | High | Consolidate pages |
/about-us | /about | Static | High | Rename with redirect |
Pull the old URLs from your Screaming Frog crawl. Map each one to its new destination. Flag any pages you are consolidating or removing -- those still need redirects pointing to the closest relevant page.
How Do You Handle WordPress-Specific URL Patterns?
WordPress generates URL structures that Framer does not replicate natively. Plan for these conversions:
WordPress Pattern | Framer Option | Recommendation |
/2024/01/post-title/ (date-based) | /blog/post-title | Simplify and redirect all date-based URLs |
/category/design/ | /blog?category=design or /design | Simplify taxonomy or remove category archives |
/page/2/ (pagination) | Infinite scroll or "load more" button | Improves UX and eliminates thin pagination pages |
/author/name/ | /blog or /about | Redirect to relevant page |
Date-based URLs are one of the most common sources of redirect errors in WordPress-to-Framer migrations. If your WordPress site uses the /%year%/%monthnum%/%day%/%postname%/ permalink structure, you will need wildcard redirects or Cloudflare Page Rules to catch all variations.
You can configure redirects directly in Framer (available on Pro plan and above under Site Settings > Redirects) or handle them at the DNS/CDN level using Cloudflare Page Rules if you need wildcard matching or more complex routing logic. Be aware that Framer redirect limits vary by plan tier.
How Do You Build the New Framer Site Structure?
Set up the Framer project before importing any content. Getting the structure right first prevents rework later.
How Do You Configure the Framer Project?
Create your Framer project
Configure site settings, favicon, and social sharing defaults
Set up global design tokens (typography, colors, spacing)
Extract brand colors and typography from your WordPress theme so the new site maintains visual consistency
How Should You Set Up CMS Collections?
Match your Framer CMS collections to your WordPress content types:
Pages
Blog posts
Case studies or any custom content types
For each collection, define fields that mirror your WordPress export: title, slug, body, featured image, publish date, categories/tags, and SEO metadata (meta title, meta description, OG image).
One important difference: Framer CMS is lighter-weight than WordPress. It does not support multi-reference fields natively, and filtering requires custom code. This is good for speed but means you may need to simplify complex WordPress data structures. For example, a WordPress post with 8 custom fields, multi-reference relationships, and complex filtering logic might become a Framer CMS item with 5 essential fields and a simpler, flatter structure -- and that is usually a performance improvement, not a loss.
How Do You Export and Reformat WordPress Content for Framer?
WordPress exports as XML. Framer imports as CSV. The conversion step in between is where most migrations hit friction.
How Do You Export Content from WordPress?
You have several export options depending on your site's complexity:
Method | Best For | Limitations |
XML Export (Tools > Export) | Standard posts and pages | Does not export media, plugin data, or custom fields |
WP All Export (plugin) | Custom post types, ACF fields | Requires CSV-to-Framer CMS field mapping |
Manual scraping | Small sites under 20 pages | Time-consuming but gives complete control |
Database dump | Large developer-led migrations | Requires SQL knowledge to parse |
For most migrations, the built-in XML export combined with WP All Export for custom fields covers everything you need.
How Do You Convert WordPress XML to Framer-Compatible CSV?
Framer CMS requires CSV imports, so you need to convert the XML. Use a script or tool to parse the XML and output a separate CSV for each content type.
Each CSV record should include:
Title
Body content (cleaned HTML)
Slug
Meta title and meta description
Publish date
Categories and tags
What WordPress Content Breaks During Conversion?
This is where most guides gloss over the hard parts. Several WordPress content elements do not translate cleanly and need manual attention:
WordPress Element | Problem | Solution |
Embedded videos | YouTube/Vimeo iframe shortcodes break | Replace with Framer embed component |
Image galleries | [gallery] shortcode renders as raw text | Rebuild as manual image grid or slider component |
Contact forms | Contact Form 7 / Gravity Forms markup is plugin-specific | Rebuild with Formspree, Tally, or Framer's native form component |
Table of contents | Plugin-generated TOC disappears | Use a Framer code component or manual anchor links |
Related posts | Automatic algorithm-based links stop working | Switch to manual curation or remove the feature |
Shortcodes | Any [shortcode] renders as plain text in Framer | Strip all shortcodes during CSV cleanup and replace with Framer-native components |
Clean the data during conversion. Remove shortcode artifacts, fix broken HTML, and strip any WordPress-specific formatting that will not render in Framer. This is also a good opportunity to improve content quality -- rewrite weak meta descriptions, fix inconsistent slugs, and remove draft or low-quality posts you do not want to carry over.
How Do You Import Content and Upload Media to Framer?
With your CSVs cleaned and your CMS collections ready, the import itself is straightforward.
How Do You Import Content via CSV?
For each content type:
Upload the CSV to the corresponding CMS collection in Framer
Confirm that titles, body content, slugs, and metadata map to the correct fields
Resolve any CSV mismatches immediately -- do not skip errors and fix them later
How Do You Handle Media File Migration?
Download all media from your WordPress wp-content/uploads directory (the Export Media Library plugin makes bulk downloads easier). Then re-upload images to Framer's media library. During upload, verify that:
Alt text is preserved (this is one of the most common silent losses during migration -- alt text often drops during bulk operations if you are not checking)
Filenames are consistent and descriptive
Image sizes are optimized for web (compress before uploading)
Image URLs in your CMS content are updated to point to the new Framer asset URLs
How Do You Recreate Layouts and Interactions in Framer?
Framer does not auto-translate your WordPress theme. Every layout must be rebuilt using Framer's visual editor, which is actually an opportunity to improve your site rather than just replicate it.
Recreate headers and footers with Framer's component system
Rebuild content blocks, section layouts, and page templates
Implement interactions, hover states, and scroll animations
Improve UX patterns that were limited by your WordPress theme
This is the most time-intensive step. Prioritize your highest-traffic pages first, get those live, and iterate on lower-priority pages after launch.
If your WordPress site used a page builder like Elementor or Divi, expect extra work here. Page builder dependencies mean the visual layout is tightly coupled to plugin-specific markup, which makes it harder to reference the old design cleanly. Screenshot 10-15 representative pages before you start rebuilding so you have a visual reference that is not dependent on the old site staying live.
How Do You Preserve SEO During the Migration?
SEO loss is the biggest risk in any site migration. This step protects your rankings.
How Do You Set Up 301 Redirects?
Use the redirect map you built earlier. Configure permanent 301 redirects either:
Directly in Framer (available on paid plans under Site Settings > Redirects -- supports wildcard patterns like /blog/* and capture groups using :1, :2 syntax)
At the DNS/CDN level using Cloudflare Page Rules or Workers if you need complex routing, more redirect capacity, or your Framer plan has hit its redirect limit
Test every redirect before launch. A single broken redirect on a high-traffic page can cost you weeks of ranking recovery.
How Do You Transfer SEO Metadata?
Every page on the new Framer site must have:
SEO title (under 60 characters, includes primary keyword)
Meta description (under 160 characters, includes a clear value proposition)
Open Graph tags (title, description, image) for social sharing
Canonical URL pointing to the correct new URL
Framer automatically generates sitemap.xml and robots.txt, but you still need to verify that every page's metadata is complete, accurate, and not duplicated from default templates.
What About WordPress Plugin Functionality?
WordPress plugins do not transfer. You need to map each plugin to a Framer alternative:
WordPress Plugin | Function | Framer Alternative |
Yoast SEO | Meta tags, sitemaps, schema | Manual meta fields + Framer's built-in SEO settings |
Contact Form 7 | Forms and submissions | Formspree, Tally, or Framer's native form component |
WooCommerce | E-commerce | Shopify or Gumroad integration (or rebuild entirely) |
Jetpack | Stats, CDN, security | Google Analytics + Framer's built-in hosting and CDN |
WP Rocket | Caching and performance | Unnecessary -- Framer's static rendering handles this natively |
Akismet | Spam protection | Your form service (Formspree, Tally) handles spam filtering |
How Should You Test Before Going Live?
Never launch without staging. A soft launch on a preview domain catches issues before they affect real users and search engines.
Before switching your domain:
Test the Framer site on a preview or staging domain
Validate all internal links (run another Screaming Frog crawl on staging)
Check menu and navigation structure across devices
Test all forms and interactive features
Verify responsive layouts on mobile, tablet, and desktop
Confirm analytics and tracking scripts are firing correctly
Test OpenGraph sharing on Twitter and LinkedIn to verify social cards render correctly
Fix everything on staging. Once DNS switches, issues become public.
How Do You Handle DNS Transition and Go-Live?
On launch day, the process is:
Update your DNS settings to point your domain to the Framer site. You do not need to take down your WordPress site first -- the DNS update will direct traffic to Framer once it propagates.
Submit your new sitemap to Google Search Console immediately after DNS is live.
Monitor crawl activity and 404 errors in Search Console over the next 48 hours.
Confirm that analytics tracking is recording visits correctly.
DNS propagation can take anywhere from a few minutes to 48 hours depending on your registrar and TTL settings. Traffic will begin shifting as soon as records update for each user's DNS resolver.
What Should You Monitor After Launch?
The migration is not done when the site goes live. Post-launch monitoring catches issues that only surface under real traffic and real crawling.
What Performance Benchmarks Should You Expect?
Here is what a successful WordPress-to-Framer migration typically looks like in terms of measurable outcomes:
Metric | WordPress (Before) | Framer (Target) |
PageSpeed Score | 40-70 | 85+ |
Page Load Time | 3-8 seconds | Under 2 seconds |
HTTP Requests | 80-150 | 20-40 |
Page Size | 3-8 MB | Under 2 MB |
In one WordPress migration we completed -- a 35-page marketing site with 120 blog posts running on a custom Genesis child theme with 28 active plugins -- PageSpeed jumped from 52 to 91 on mobile. Load times dropped by 40%, and the team saw a 30% reduction in ongoing maintenance time. The full migration took 6 weeks with one designer and one part-time developer, and the main challenges were flattening Advanced Custom Fields data and rebuilding forms.
What Should You Track Week by Week?
Week 1-2: Watch for issues
Monitor Google Search Console for indexing warnings, crawl errors, and coverage drops
Run site:yourdomain.com in Google to verify pages are being indexed
Test a sample of 20 old URLs to confirm redirects are working
Compare traffic to your pre-migration benchmarks
Check for user feedback ("can't find X" = navigation issue, "looks broken on mobile" = responsive bug)
Week 3-4: Optimize and stabilize
Track rankings for your top 20 keywords
Monitor organic traffic trends and bounce rates
Fine-tune any images causing slow loads
Adjust CMS structure if content editing workflows feel clunky
Expect some temporary ranking movement as search engines re-index the site. A well-executed migration typically stabilizes within two to four weeks. If you see sustained drops after four weeks, check your redirects, canonical tags, and metadata for errors.
Frequently Asked Questions
Will migrating to Framer hurt my SEO?
No. As long as you preserve key SEO elements -- meta titles, descriptions, canonical URLs -- and map old URLs to new ones with 301 redirects, search engines treat your new Framer site as the same domain with upgraded infrastructure. You may even see improved ranking signals from better Core Web Vitals. The key requirement is ensuring every backlinked page either keeps its URL or has a corresponding redirect. Backlinks pointing to 404 pages forfeit their SEO value entirely.
How long does Google take to re-index a migrated site?
Google typically begins re-indexing within a few days of sitemap submission. Complete re-indexation across all pages can take several weeks depending on site size and how frequently Google already crawls your domain.
Do I need to take my WordPress site down before switching to Framer?
No. Build and test your Framer site on a staging or preview domain. Only update DNS when you are fully ready. The WordPress site stays live until DNS propagation completes, so there is effectively zero downtime.
How do I handle large blogs with hundreds of posts?
The strategy depends on volume:
Post Count | Strategy | Timeline |
Under 50 | Manual migration | 1-2 weeks |
50-200 | Semi-automated (CSV import + manual cleanup) | 2-3 weeks |
200-500 | Automated CSV import with QA spot-checks | 3-4 weeks |
500+ | Prioritize top posts by traffic, archive low-value content | 4-6 weeks |
For large blogs, migrate your highest-traffic posts first, ensure their redirects and metadata are perfect, then batch import the rest. Complex taxonomy structures (deep category/tag hierarchies) typically need simplification for Framer's flatter CMS model.
Can I automate the WordPress to Framer content import?
There is no official one-click migration tool, but you can streamline the process significantly. Use the built-in WordPress XML export for standard content and WP All Export for custom post types and ACF fields. Convert to CSV using a script or conversion tool, then use Framer's bulk CSV import. The manual work is mostly in cleaning content (stripping shortcodes, fixing HTML) and verifying field mappings.
What happens to my WordPress plugin functionality?
WordPress plugins do not transfer to Framer. You need to identify each plugin's role and find a replacement. Yoast SEO becomes manual meta fields plus Framer's built-in SEO settings. Contact Form 7 becomes Formspree, Tally, or Framer's native form component. WooCommerce requires a Shopify or Gumroad integration. Caching plugins like WP Rocket become unnecessary because Framer's static rendering handles performance natively. Any remaining functionality gaps can typically be filled with custom code injection, embeds, or API integrations.
