Webflow and Framer are the closest of any two platforms you could migrate between. Both are visual, both host your site, and both produce clean, fast pages. That makes a Webflow to Framer move simpler than most, but not automatic.

Teams usually make the switch for speed of design and editing: Framer’s canvas works like a design tool, and day-to-day edits don’t need someone who understands Webflow’s class system. This guide covers what moves cleanly, what has to be rebuilt, and how to protect your rankings along the way. For the general picture, see our overview of migrating to Framer.

Should You Move at All?

Be honest about this one first. If your Webflow site runs a large content operation, hundreds of CMS items, multi-reference fields and programmatic SEO pages, Webflow may still be the better home. We cover that trade-off in detail in Framer vs Webflow for B2B.

If your site is a design-led marketing site with a modest blog, Framer is usually the better fit, and the move is very manageable. One exception: Framer has no built-in store, so a site using Webflow Ecommerce needs a separate commerce service.

What Moves and What Gets Rebuilt

Before You Start

Pick the right Framer plan

Plan for Framer’s Pro plan. Framer lists site redirects as a Pro feature, and Pro includes staging so you can review the site before switching your domain. Pro allows 10 CMS collections with 2,500 items each, so check your Webflow collections fit.

Record your baseline

Export your top pages and queries from Google Search Console before anything changes, so you can compare after launch.

Note your existing Webflow redirects

If your Webflow site already has 301 redirects set up in its site settings, list them. They live in Webflow, so they disappear when you move unless you recreate them in Framer.

Moving Your CMS Content

Export each collection as CSV

Webflow lets you export a CMS collection as a CSV from the Designer’s Collections panel. You export one collection at a time, so work through blog posts, case studies, team members and any others separately.

Keep Webflow live until the import is done

Image and file fields export as URLs pointing to Webflow’s hosting. Framer downloads images from those URLs when you import, but if the Webflow project is gone, the links break. Don’t cancel or delete anything in Webflow until every image is confirmed in Framer.

Check images inside rich text

Images placed inside rich text fields export as HTML with links back to Webflow. After importing, open a few posts and check every inline image actually loads from Framer. Any that still point to Webflow should be re-uploaded before you close the old project.

Import linked collections in the right order

Reference and multi-reference fields (a post linked to an author, a case study linked to an industry) can be reconnected on import, matched by slug, but only if the collection they point to already exists. If your Blog collection references an Authors collection, import Authors first, then Blog. Otherwise the references have nothing to connect to and need relinking by hand.

After each import, check slugs, dates, rich text, images and references on a few items before moving on.

Rebuilding Design and Interactions

Webflow’s interactions and animations don’t transfer. They’re rebuilt in Framer’s animation system, which is usually faster to work with and often a good moment to simplify motion that had grown over time.

Layouts are rebuilt too. Before you start, write down your type scale, colours, spacing, grid and breakpoints, then turn repeated sections into Framer components. Rebuilding one full page end to end first sets the pattern for the rest and surfaces problems early. A clean component setup is also what makes the new site easy for your team to edit later.

Forms also need rebuilding, either with Framer’s native forms or by embedding the form tool you already use, then reconnecting them to your CRM or email.

Redirects

Your URLs may already match

Webflow CMS pages usually live at paths like /blog/post-name. If you set up your Framer CMS page with the same path and keep the same slugs, those URLs stay identical and need no redirects at all. This is the biggest advantage of a Webflow move.

Map everything anyway

Matching paths only cover pages that don’t change. Any page you rename, merge or drop needs a 301 redirect to its closest new page, not the homepage, and so does every redirect you listed from your old Webflow settings. Point old URLs straight to their final destination to avoid redirect chains. Framer supports wildcard redirects, so a changed path like /resources/* to /blog/:1 can be handled in one rule.

Carry over metadata and schema

Make sure each CMS item’s SEO title and meta description come across in the CSV, and map them to dedicated fields in Framer. Webflow sites often have SEO settings spread across collection templates, so check those templates specifically. Any schema you had in Webflow’s custom code gets added back in Framer the same way.

Launch and After

Review everything on staging, including the 404 page and sitemap. Then point your domain to Framer, leaving your email (MX) records alone, and keep the Webflow project available until the new site and redirects are verified. Submit your new sitemap in Google Search Console and compare traffic and rankings against your baseline over the next 8 to 12 weeks. Because so many URLs stay the same, a well-mapped Webflow migration often shows very little movement at all.

Planning a Webflow Move?

A Webflow to Framer migration is mostly about the details: images that still point back to Webflow, collections imported in the wrong order and redirects you forgot existed. Budget-wise, it usually sits at the lower end of what a Framer site costs, because so much of the structure carries over.

If you’d like it handled for you, we migrate Webflow sites to Framer with your CMS, rankings and integrations carried across. Get in touch and tell us about your current site.