Webflow to Framer Migration: The Complete Guide (Pages, CMS, SEO and Redirects)

What is a Webflow to Framer migration?

A Webflow to Framer migration is the process of rebuilding a Webflow site in Framer and moving its content, URLs and search signals across without losing traffic. Because the two builders store layouts, styles and interactions in completely different ways, there's no button that converts one into the other. Pages and components are rebuilt; CMS content moves through export and import; SEO moves through a redirect sheet and careful metadata work.

That sounds like bad news, but it's the most useful fact about this kind of project. A rebuild is the cheapest moment you'll ever have to fix the copy, cut dead pages and simplify the CMS. Teams that copy the old site pixel for pixel pay for a migration and get the same site back. Teams that treat it as a rebuild get a better site for roughly the same effort.

We design and build on Webflow, Framer and Next.js, so this guide isn't selling one platform. It's the playbook we'd follow ourselves: copy first, then structure, then CMS, then redirects, then launch. If you want just the step list, read how to migrate from Webflow to Framer in 9 steps. If you're going the other way, see our Framer to Webflow migration guide.

Should you migrate from Webflow to Framer?

You should migrate from Webflow to Framer when your team values speed of design and publishing more than deep CMS structure, and your site is mostly marketing pages rather than a large content library. You should stay on Webflow when you rely on relational CMS content, large collections, Webflow's class system or its API.

What drives most switching right now is pricing and velocity. Webflow's seat and bandwidth changes from late 2024 into 2025 drew strong pushback on its own forums, and according to BRIX Templates' breakdown of Webflow's May 2026 pricing changes, the CMS and Business site plans were merged into a single Premium plan with a 20,000-item CMS limit. Framer has its own costs to check, including per-locale localization pricing and seat fees. Our Webflow vs Framer pricing comparison works through the numbers, and our Webflow vs Framer verdict for SaaS sites covers the fit beyond price.

Be honest about what you'll give up too. Our piece on why teams leave Webflow for Framer and what they lose covers the velocity gains and the real losses, and why teams move from Framer back to Webflow covers the regrets.

What moves automatically and what has to be rebuilt?

Almost nothing moves automatically except CMS content, and even that needs cleanup. Layouts, styles, components and interactions are rebuilt in Framer. The table shows how each part of a Webflow site gets across.

Interactions deserve their own plan, because some translate cleanly and some don't. Our guide to Webflow interactions in Framer shows what maps directly and what has to be redesigned.

Why should a migration start with the copy?

A migration should start with the copy because the words decide the page structure, and the structure decides what you build. If you rebuild first and fix the copy later, you'll rebuild many sections twice. Copy-first is the single biggest difference between a migration that improves the site and one that just changes the tool.

Start with a full URL inventory from a crawl, your sitemap and analytics. For each page, decide one of four things: keep as is, rewrite, merge into another page, or retire with a redirect. Then rewrite the pages that matter most, usually the home page, product or feature pages, pricing and the top-traffic blog posts, before design starts.

1. 1

   Inventory every URL

   Crawl the live site and combine it with the sitemap and analytics. Note traffic, backlinks and conversions for each URL.

2. 2

   Decide keep, rewrite, merge or retire

   Mark each page. Low-value pages with no traffic or links are candidates to retire with a redirect.

3. 3

   Rewrite the money pages

   Rewrite home, product, pricing and top landing pages in a doc first, with headlines, sections and calls to action.

4. 4

   Lock the page structure

   Turn the approved copy into a section list per page. This is the brief for design and the Framer build.

How do you map Webflow CMS collections to Framer CMS?

You map Webflow CMS collections to Framer by listing every field in each collection, choosing its Framer field type, and deciding how to handle anything Framer represents differently, before importing a single row. The field map is the document most guides skip, and it's what prevents broken references and empty fields after import.

Import order matters. Bring in collections that other collections point at first, such as authors, categories and tags, then the collections that reference them, such as posts and case studies. Webflow's CSV export is documented on Webflow's own help pages; on import, rich-text images often arrive as placeholders, so plan time to fix them. Our detailed guide to Webflow CMS to Framer CMS migration covers references, rich text and the edge cases.

How do you build the redirect sheet for a Webflow to Framer migration?

You build the redirect sheet by listing every old URL from your inventory in one column, its new URL in the next, and the redirect type and status in the rest. Every URL that changes gets a one-to-one 301 to its closest equivalent, never a blanket redirect to the home page.

Keep slugs identical wherever you can, since an unchanged URL is the safest URL. Watch Webflow's collection paths: if posts lived under /blog/ in Webflow and you change the path in Framer, every post needs a redirect. Add the rules in Framer's redirect settings, and check they don't create chains with redirects from earlier moves. Our Webflow to Framer migration checklist includes a template for this sheet.

How do you launch a Framer site without losing SEO?

You launch without losing SEO by checking metadata, redirects and indexing on staging, switching the domain at a quiet time, then crawling the old URL list immediately after launch. Most SEO losses in migrations come from missing redirects, missing metadata or a staging noindex left in place.

1. Compare every important page on staging with the live Webflow page: title, description, headings, canonical and alt text.
2. Check that the Framer site's indexing settings allow search engines once it's on the live domain.
3. Lower DNS TTLs a day ahead, then switch the domain to Framer at a low-traffic time.
4. Crawl the full old URL list: every URL should return a 200 or a single 301 to a live page.
5. Submit the new sitemap in Search Console and watch coverage and performance daily for two weeks.
6. Keep the Webflow site and its assets until the new site is stable and every image is re-hosted.

Running both platforms side by side for a while, for example moving the marketing pages first and the blog later, is possible with the right domain setup. Our guide to running Webflow and Framer on the same domain covers subdomain and reverse-proxy options. For multilingual sites, see moving a localized site from Webflow to Framer.

How much does a Webflow to Framer migration cost?

A Webflow to Framer migration costs whatever the rebuild costs, because the rebuild is the migration. Agency quotes we see for website migrations commonly range from about $1,500 to $25,000 depending on site size, and they vary with page count, CMS volume, interactions and how much copy and design work is included.

Typical range we see quoted for website migrations, by site size

$1.5k–$25k

Designify website package, up to 6 pages, custom design and build

$8,000

Per extra page beyond six in the Designify website package

+$500

The biggest cost drivers are the number of unique page templates, the size and structure of the CMS, complex interactions and whether you're improving the copy and design or copying them. Our guide to Webflow to Framer migration cost breaks this down, and if you're weighing a move to code instead, see Framer to Next.js migration cost.

Which Webflow and Framer migration guide should you read next?

Pick the guide that matches where you are in the decision. These cover each part of the move in more depth.