Leaving Webflow
Getting out of Wix
Webflow to Framer migration
The site gets rebuilt in Framer, not exported into it. Your CMS content, your URL structure and your search rankings come across. The class soup, the hosting bill and the plan renewal stay behind.
Wix will not give your site back. There is no export, the layout is a set of fixed coordinates, and the mobile version is a second site you maintain by hand. All of it gets rebuilt in Framer — and the content, the URLs and the rankings come with you.
301
0
Redirect for every path that changes
Files Wix lets you export
1:1
1
CMS collections, fields and items
Responsive site instead of two
2–5
301
Weeks for a typical marketing site
On every path Wix auto-named
What actually moves
A migration is six separate transfers, and each one fails differently. Every tile below runs the real thing rather than describing it.
Every old URL still resolves
The redirect map is written before launch, not reconstructed from 404s afterwards. Paths Webflow forced into a collection prefix get shorter, and a 301 carries the old one. Paths that do not change are confirmed unchanged in a crawl diff rather than assumed.
What happens to rankings
A complete redirect map costs you a dip of a week or two while Google recrawls, then recovery. An incomplete one costs you the traffic and does not give it back. This is the whole reason the map comes first.
The CMS comes across
Collections, fields and items transfer with references and multi-references intact. Field types map one to one where an equivalent exists, and item counts are checked against the original rather than assumed.
Class soup becomes a style set
This is the part an export cannot do. Forty-odd Webflow classes and combo classes — hero-heading, hero-heading-2, hero-heading-copy — collapse into a handful of Framer text styles, colour styles and components that your team can actually edit without breaking a neighbour.
Interactions get rebuilt
IX2 keyframe timelines become Framer variants and transitions. Most get simpler. The occasional one with no native equivalent becomes a small code component.
Nothing goes live on a guess
Staging gets crawled and diffed against the live Webflow site before anything switches. If the diff finds a missing page or a broken redirect, the run goes back to staging instead of forward to DNS. Only after the switch holds for 48 hours in Search Console does the old plan get cancelled.
What happens to each part of the site
Four things come across as they are, three get rebuilt, and one has no equivalent in Framer at all. You should know which is which before you agree to anything, not on invoice day.
When moving is worth it, and when it is not
Framer is not better than Webflow at everything, and a migration you did not need is an expensive way to change logos. These are the four cases that pay for themselves, and the four that do not.
How the move runs
01
Content audit
Every URL, collection and template is listed before a price exists. That inventory is what the quote is built from, and you keep it whether or not you hire me for the rest.
02
Rebuild
Design system first, then templates, then pages. You review the work in a browser on a staging URL rather than as a deck of screenshots.
03
Content move
Collections and items transfer with their references intact, then get checked field by field against the original counts.
04
Redirect map
Every old path is mapped to a new one before anything goes live. Paths that do not change are confirmed unchanged rather than assumed.
05
Cutover
Staging is crawled and diffed against the live Webflow site, redirects go in, DNS switches, and the first 48 hours are watched in Search Console before the old plan is cancelled.
What it costs
The content audit always comes first, because the page and item counts decide the number. You get a fixed figure after it, not an hourly rate before it.
Small site
$2,400
and up · under 15 pages
A marketing site with no CMS or one simple collection. Redirect map and schema included.
Site with a blog
$4,500
and up · several templates
Multiple collections, blog and case-study templates, full redirect map and a crawl diff before cutover.
Larger or unusual
Quoted
after the content audit
Hundreds of pages, heavy integrations, or a redesign folded into the move. The audit is priced separately if that is all you want.
Frequently asked questions
Can you move a Webflow site to Framer without losing rankings?
Yes, provided the redirect map is complete before launch. Every old path gets a 301 to its new home, metadata transfers per page, and the internal link structure is rebuilt rather than flattened. Expect a dip in the first fortnight while Google recrawls, then recovery. Anyone promising zero movement is guessing.
Does the Webflow CMS transfer to Framer?
Yes. Collections, fields and items all come across, including reference and multi-reference fields. Field types are mapped one to one where an equivalent exists — plain text to text, rich text to formatted text, switch to boolean — and item counts are checked against the original after the transfer rather than assumed.
Will my URLs stay the same?
Wherever Webflow allowed a sensible one, yes. Where Webflow forced a collection prefix like /blog-posts/, the URL usually gets shorter and the old path is carried by a 301. Paths that do not change are confirmed unchanged in the crawl diff instead of being taken on trust.
Can you just export the Webflow code into Framer?
You can, and you should not. Exported Webflow markup carries its class structure with it and produces a Framer project nobody on your team can edit — which defeats the reason for moving. The site gets rebuilt against a real design system instead.
What about Webflow Ecommerce?
Framer has no direct equivalent, so this is not a migration but a replatform: products and checkout move to Shopify and Framer becomes the storefront. If Webflow Ecommerce is running your checkout today, treat that as a separate project with its own scope.
How long does a Webflow to Framer migration take?
Two to five weeks for a typical marketing site with a blog, counted from the end of the content audit. Sites with hundreds of CMS items, several templates or heavy integrations take longer, which is exactly what the audit is for.
What happens to my Webflow interactions?
IX2 timelines are rebuilt as Framer variants and transitions. Most become simpler, because Framer expresses hover and scroll states directly instead of as keyframe tracks. The occasional interaction with no native equivalent becomes a small code component.
Send me the Webflow URL and I will tell you what moving costs
One link is enough to see the page count, the collections and the URL structure. You get a list of what comes across, what needs rebuilding and what has no equivalent — before you commit to anything.