Webflow to Framer migration
Moving from Webflow to Framer, your CMS collections come across as CSV with rich text carried over as HTML, while the class system and interactions are rebuilt as Framer components and effects. Item URLs can keep the same pattern, wildcard rules are translated, and a typical marketing site moves in about two to four weeks.
- Audit the Webflow project
- Export collections and assets
- Rebuild and import in Framer
- Redirects and switchover
Trusted by B2B and premium service brands in 17+ countries.
Why teams move
Why teams move from Webflow to Framer
Design and build in one tool
Teams that design in Framer or work closely with designers often want the live site in the same tool, so a change in the design is a change on the site rather than a handover.Simpler editing for content people
Framer's canvas and CMS are approachable for marketers who never learned Webflow's class system, so more of the team can publish safely.A clean rebuild of a drifted project
Webflow projects that grew over years often carry unused classes and interactions.A move is a chance to rebuild the site as a tidy component system rather than patch the old one.
What moves
What carries over, and what needs work
Carries over
- CMS items, exported to CSV and imported with Framer's CSV Import plugin
- Rich text, which Webflow exports as HTML and Framer imports into Formatted Text
- Images and files, downloaded from Webflow before the old project is closed
- Collection slugs, so item URLs can keep the same last segment
- SEO titles and descriptions per page and per template
Needs work in Framer
The class systemWebflow's classes and combo classes do not translate to Framer.
Styles are rebuilt as Framer components and text styles from the design, which usually ends up simpler.
- InteractionsWebflow Interactions are rebuilt with Framer's own effects, keeping the ones that help the content and dropping the ones that only add weight.
- EcommerceFramer has no native ecommerce. A small catalogue can run through a third-party Shopify plugin; a larger Webflow store is usually better moved to a dedicated commerce platform.
- Localized contentWebflow Localize content exports one locale per CSV. Each locale is moved into Framer's Localization add-on and its translated page paths are set deliberately.
Content model
How Webflow content maps to Framer
We map every field before anything moves, so content is not retyped by hand and nothing is dropped without a decision.
| In Webflow | In Framer | What we check |
|---|---|---|
| Plain text | Plain Text | Character limits checked against the new design |
| Rich text | Formatted Text | Embeds and custom code inside rich text reviewed by hand |
| Image, Multi-image | Image, Gallery | Files re-hosted on Framer, alt text kept |
| Reference, Multi-reference | Reference, Multi-Reference | Referenced collections imported first |
| Option | Option | Values kept identical so filters behave the same |
| Switch | Toggle | Same meaning, same defaults |
| Date/Time | Date | Time zone checked so dates do not shift |
| Link | Link | Internal links rewritten to the new paths |
Redirects and SEO
Protecting rankings during the move
The redirect plan
Match collection paths
Webflow item URLs follow /collection-url/item-slug, and a Framer CMS page path such as /blog/:slug can reproduce the same pattern, so most item URLs do not change at all.Translate wildcard rules
Webflow rules with (.*) and %1 are rewritten with Framer's * wildcards and :1 captures in Site Settings under Hosting, then tested against the full URL list.Static pages one by one
Static page paths are compared from the crawl. Where the new navigation renames a page, that single URL gets its own permanent redirect.
Risks we watch for
Locale URLs
Webflow Localize serves locales from subdirectories and lists hreflang in the sitemap.Framer uses its own locale paths, so every localized URL is mapped and checked.
Canonical overrides
Framer writes canonical tags automatically from the connected domain, so any page that relied on a custom canonical in Webflow is checked and handled deliberately.Images hosted by Webflow
Rich text often points at Webflow's CDN. If those links survive the import and the old site is deleted, images break, so asset URLs are rewritten on import.
Timeline and fit
How long it takes, and whether it suits you
Typical timeline
Webflow to Framer
2to4weeks
What the range assumes
Two to four weeks is our published range for migrating a typical marketing site. It assumes a design is agreed, content is final, and the page count is modest. Large collections, ecommerce or several locales take longer, and we confirm the range once we have seen the CMS structure.
We confirm the timeline for your site after the initial audit, since the number of URLs and the state of the content drive most of the work.
It fits when
- The site is a marketing site and the team wants simpler editing
- Design already happens in Framer or Figma
- The Webflow project has drifted and needs a clean rebuild anyway
- The CMS is a blog, case studies or a modest set of collections
We would advise against it when
- Your Webflow store is central to revenue
- Your team is trained on Webflow and happy with it
- The CMS relies on many collections with deep reference chains
- You only want a visual refresh, not a platform change
How we run it
How we run a Webflow to Framer move
Step 01
Audit the Webflow project
We crawl the live site, list collections, fields, interactions and redirect rules, and record what ranks so the move is planned around it.
Step 02
Export collections and assets
We export each collection to CSV, download images and files, and clean the rich text so it imports cleanly into Formatted Text.
Step 03
Rebuild and import in Framer
We rebuild pages and CMS templates as Framer components, import the collections with the CSV Import plugin and compare items with the source.
Step 04
Redirects and switchover
We translate the redirect rules, test every old URL, connect the domain and watch indexing and rankings after launch.
Common questions
Webflow to Framer: questions we get asked
Can Webflow CMS content be imported into Framer?
Yes. Webflow exports each collection to CSV with rich text as HTML, and Framer's CSV Import plugin brings it into a matching collection. Images are downloaded and re-hosted rather than linked to Webflow.
Do Webflow interactions carry over to Framer?
No. Interactions are rebuilt with Framer's effects. We keep the motion that supports the content and usually end up with fewer, simpler interactions.
Should we move from Webflow to Framer at all?
Only if it solves a real problem, such as editing friction or a drifted project. Webflow is a strong platform; if your team is happy in it, we would build there instead.
Next step
Want it moved for you? We plan the move around what already ranks.
We inventory every Webflow URL, map each one to its new address in Framer, move the content with its metadata, then switch over and watch indexing.
- Every URL inventoriedA full URL list with a ranking and traffic baseline.
- Every old URL mappedA 301 redirect map so link equity carries over.
- Watched after launchSitemap submitted, then indexing and rankings monitored.
Planning a move from Webflow?
Tell us about your current site and what needs to move, and we will come back to you with the next steps.