The Brief
Webflow to Framer Migration: What Actually Breaks
Moving a SaaS site from Webflow to Framer? What breaks in the CMS, rich text, interactions, forms, redirects and SEO settings, and how to handle each one.
Most teams I talk to don't leave Webflow because it's bad. They leave because the marketing team wants to ship a landing page on Tuesday without waiting for the one person who understands the class system.
The pages themselves are the easy part of a migration. You rebuild them, and usually improve them along the way. What breaks is everything around the pages. Here's the list I work through on every Webflow to Framer move.
1. CMS collections
Webflow lets you export each collection as a CSV, and Framer's CMS imports CSV. That gets you most of the way.
Where it gets fiddly:
Reference and multi-reference fields export as IDs or slugs, not as linked items. You need to import the referenced collection first, then reconnect them.
Images come over as links to Webflow's asset CDN. Re-upload them into Framer. Don't rely on those URLs staying up once you cancel the Webflow plan.
Option fields and switches need matching field types set up in Framer before the import, or they arrive as plain text.
2. Rich text
Plain paragraphs, headings, lists and images move cleanly. Custom embeds inside rich text don't: code snippets, videos, tweet embeds, HTML widgets. Each one needs rebuilding as a Framer component or replacing.
Search your export for embed markup before you quote a timeline. Ten posts with embeds is an afternoon. Two hundred is a week.
3. Interactions
Webflow interactions don't transfer. Every scroll animation, hover state and tab component gets rebuilt with Framer's own effects and variants.
Use that as a chance to cut. Most sites I migrate have interactions nobody on the team remembers adding. Keep the ones that explain the product and drop the rest. Your mobile load time will thank you.
4. Forms
Webflow forms are tied to Webflow's form handling. In Framer you rebuild each form and point it at email, a webhook or your CRM integration.
Make a list of every form on the site: demo request, newsletter, contact, gated content. Then test each one on the new site before launch. A demo form that silently stops sending leads is the most expensive bug a migration can ship.
5. Custom code and tracking
Analytics, the cookie banner, chat widgets, ad pixels and schema markup usually live in Webflow's site-wide custom code. Copy all of it into Framer's Site Settings, then check what's still needed. Duplicated tracking scripts are one of the most common reasons a freshly migrated site is slower than it should be.
6. URLs and redirects
This is where migrations lose traffic. Webflow and Framer both let you choose your URL structure, but teams often change it during the move, like going from /post/slug to /blog/slug.
Every old URL needs to point to its new equivalent on launch day. Pull the full list from your sitemap and from Google Search Console, map each one, and enter the redirects before you switch DNS. Check your Framer plan includes redirects before you start.
7. SEO settings per page
Meta titles, descriptions and social images need setting on every static page, and binding to CMS fields on every template page. If you skip the binding, every blog post goes live with the same title.
Watch the canonical tags too. On my own site, a hand-written snippet once set every page's canonical to the homepage. Google quietly treated every blog post as a duplicate of the homepage until I removed it. Framer generates correct canonicals on its own. Let it.
Launch day checklist
Every redirect from the old URL list tested
Every form submitted once and received
Analytics firing, and only once
Sitemap submitted in Search Console
Meta titles checked on a sample of CMS pages
Webflow plan kept live for a few days as a fallback
Moving from WordPress instead? I wrote about that one separately: should you migrate WordPress to Framer yourself, or hire someone.
If you'd rather hand the whole move to someone who has done it before, get in touch. I'll ask for your sitemap and your Search Console access, and tell you what's going to break before it does.
Related reading
10 things about Framer nobody tells you before you commit to it
Your Framer site isn't ranking. It's not the platform's fault.
The 6 Pages Every SaaS Website Needs (Most Startups Skip Three)
Want this handled for your startup? See how I work as your Framer developer.
New to Framer? Get 3 months free on the Pro plan when you sign up yearly with my referral link: framer.link/framerexpert or click the text here.
Keep reading