Migration sequence
Nothing leaves Framer automatically
Each stage recovers something Framer would otherwise lose on its own.- InventoryDocument every page and override
Framer has no full-site export to lean on.
- CMSMap Collections to Webflow CMS
Framer's CMS Collections become structured Webflow content.
- InteractionsRebuild overrides and motion
React code overrides and built-in motion don't carry over directly.
- SEORebuild metadata by hand
Framer's per-page SEO settings don't transfer automatically.
- CutoverTest, then move the domain
Forms, integrations, and DNS verified before launch.
Document every page before leaving Framer's closed editor
Framer does not offer a full-site export to another platform. Content, design, and code overrides stay inside the Framer editor and its React-based rendering engine, so the starting point is a manual, page-by-page inventory rather than a file download.
Document every page, its content, and any code overrides or Code Components built on top of it. Export media assets at their original resolution before account access changes.
- Full page and content inventory, built by hand
- Per-page SEO titles and descriptions recorded
- Code overrides and Code Components documented by function
- Media assets exported at original resolution
Decide what becomes Webflow CMS instead of static pages
Framer's CMS Collections are the direct equivalent of Webflow Collections - blog posts, case studies, or any repeating content type modeled as a Collection in Framer maps cleanly to the same structure in Webflow.
Any Code Component that renders Collection data needs to be rebuilt as a Webflow Collection list or Collection page template, since Webflow has no equivalent to a custom React component querying a CMS.
- CMS Collections mapped to Webflow Collections
- Custom fields and content types planned before templates are built
- Collection list and detail page templates planned
- Code Components rendering collection data noted for rebuild
Rebuild code overrides and animations without a React runtime
This is the step a Framer migration needs that a Wix or Squarespace migration usually doesn't: Framer sites often lean on React-based code overrides and built-in motion effects for interactions, and neither carries over to Webflow directly, since Webflow has no React runtime to execute them in.
Each override or animation needs to be rebuilt with Webflow's native Interactions panel where that covers it, or with custom script (GSAP is a common choice) where it doesn't. The goal is matching what the interaction does, not porting the original code line for line.
- Code overrides and components inventoried by function, not just copied
- Interactions rebuilt with Webflow Interactions or custom script
- Motion and scroll effects tested for behavioral parity
- Page performance checked after rebuild, since animation code adds weight
Rebuild Framer's SEO settings and prepare redirects
Framer's per-page SEO fields, sitemap, and canonical settings are configured inside Framer and don't transfer. Meta titles, descriptions, and any structured data need to be recreated directly in Webflow.
Framer URLs rarely match a clean Webflow structure once a site has grown. Treat every live URL as needing an explicit destination, map it, and configure and test 301 redirects in Webflow before the domain moves - Framer can't serve redirects for URLs it no longer hosts.
- Meta titles and descriptions recreated for every indexable page
- Structured data rebuilt where Framer applied it automatically
- Every live Framer URL mapped to its closest Webflow destination
- 301 redirects configured and tested in Webflow before DNS changes
Test forms, integrations, and the domain cutover
Framer forms and any connected integrations need to be rebuilt in Webflow and tested with real submissions before launch, not just visually recreated.
Confirm the DNS and domain transfer plan ahead of time, including who holds registrar access, so the cutover happens in a single planned window rather than an extended partial outage.
- Forms rebuilt and tested with real submissions
- Connected integrations reconnected in the new system
- DNS and domain transfer plan confirmed before cutover
- Post-launch crawl and indexing check scheduled
