Webflow's own help centre says there is no automated way to convert a Framer site into a Webflow site, and that a Framer to Webflow migration "is a rebuild, not a transfer". Layouts, styles and interactions are recreated by hand. Content can travel as CSV, and in most cases the URLs can stay exactly as they are.
This guide covers when the switch is worth it, what exports, how CMS fields and URLs map, and how to carry the design system across. Every limit comes from Webflow, Framer or Google documentation, read in November 2026.
When a Framer to Webflow migration makes sense
We build marketing sites in Webflow, so read this section knowing we are not neutral. Framer is a good tool for a small site that a designer owns. The case for moving usually appears when the site stops being small or stops being one person's.
The CMS has outgrown its plan. Framer sells CMS items and collections in paid blocks above each plan's allowance. A blog plus case studies fits. A glossary, an integrations directory and a resource centre on the same site start to press on it. Our Webflow vs Framer comparison sets the two CMS limits side by side.
Marketing wants control of technical SEO. Framer automates canonicals, sitemaps and language tags, which is a feature until someone needs to change one by hand.
More people edit and publish. With several marketers and an agency on the site, role and publishing controls start to decide the platform.
The switch rarely pays back for a portfolio or a ten-page launch site that one designer updates.
What you can export from Framer, and what you rebuild
Framer's documentation disagrees with itself on export. Its article on porting data says every Framer site is published as HTML, CSS, JavaScript and assets that you can download and host elsewhere. Its article on HTML export, updated the same day, 15 September 2026, says Framer does not offer HTML export for self-hosting because published sites rely on server-side rendering, image resizing and other platform services. For a migration plan, assume the second: there is no supported way to take a working site out.
| Part of the site | Out of Framer | Into Webflow |
|---|---|---|
| Pages and layouts | No supported export | Rebuild by hand, using the live Framer site as reference |
| CMS content | CMS Export plugin, CSV per collection | CSV import per Collection, up to 4 MB per file |
| CMS images | Image URLs inside the CSV | Imported by URL, without responsive variants |
| CMS files | Not covered by the CSV route | Upload by hand; no data maps to File fields |
| Canvas images and icons | PNG or JPG at 1x to 4x from the desktop app | Upload to the Assets panel; get SVG and source files from the designer |
| Redirects | Redirect Sync plugin exports a CSV | Rewrite to Webflow's syntax, then add or import |
| Fonts | Not exported | Upload files or connect Google or Adobe Fonts, after checking the licence |
| Interactions | Not exported | Rebuild with Interactions with GSAP or custom code |
Sources: Webflow Help Center, Framer Help Center and Framer Marketplace, read 2026-11-04
Framer's asset export produces PNG and JPG only, so take logos and icons from the designer's source files. And budget design time for motion: Webflow notes some Framer animations "may not translate directly".
Moving the CMS: the field map
Webflow warns that some Framer setups need manual extraction. In practice, Framer's own CMS Export plugin writes each collection to a CSV file, with a preview first. Check each file in a spreadsheet, then map every Framer field type to its Webflow counterpart.
| Framer field | Webflow field | Import rule to check |
|---|---|---|
| String | Plain text | Name and Slug must be under 256 characters |
| Formatted text | Rich text | Embedded HTML may be cleaned of unsupported elements and attributes |
| Image | Image | Direct image URL; no srcset or sizes generated |
| File | File | Nothing maps; upload after the import |
| Link | Link | Any URL |
| Date | Date/time | Use a supported date format |
| Boolean | Switch | Two unique values; choose which means yes |
| Color | Color | Hex codes need the # sign |
| Number | Number | No commas, currency symbols or units |
| Enum | Option | Up to 100 unique values become options |
| Collection reference | Reference | Matched by name converted to slug, or by custom slug |
| Multi collection reference | Multi-reference | Values separated by semicolons |
Sources: Framer developer reference, Field type; Webflow Help Center, How do I import content into the Webflow CMS?
Import referenced collections first. Webflow turns a reference value such as "Jane Smith" into jane-smith and looks for an item with that slug. If the author item has a custom slug, the match fails and the field stays empty. Import Authors and Categories before Posts, and check what the Framer export holds in reference columns before you map them.
Re-upload hero images. CSV images arrive without responsive variants. We would re-upload the featured image of every post that ranks, and accept URL imports for the rest.
Pull images before you cancel Framer. CMS image URLs in the export point at Framer's hosting. Import while the Framer project is still live. Our guide to Webflow CMS import tools covers the API and apps for collections too large for a clean CSV.
The URL plan: keep what you can
This is where a Framer move is gentler than a WordPress one. Both platforms serve a CMS page at a fixed path plus one dynamic slug. Framer uses a Collection path such as /blog/ followed by the item slug, and allows static segments before it. Webflow uses a Collection URL followed by the item slug, and since 2023 its CMS Folders add static segments in front. A Framer post at /blog/my-post can live at /blog/my-post in Webflow.
| Framer pattern | Example | In Webflow | Redirect needed |
|---|---|---|---|
| Static page | /pricing | Same path | No |
| Static page in a folder | /company/careers | Same path, using a folder | No |
| CMS page | /blog/my-post | Collection URL blog, same slug | No |
| CMS page with a prefix | /resources/guides/my-guide | CMS Folder resources, Collection URL guides | No |
| Suffix after the slug | /blog/my-post/amp | Not possible | Yes, to the main post |
| Locale folder | /es/blog/my-post | Webflow Localize subdirectory | Check per locale |
| Slug with uppercase or accents | /blog/Café-Guide | Lowercase Latin only | Yes |
Sources: BRIX Templates, Framer and Webflow URL structure guides, 2026
Webflow only accepts lowercase Latin letters, numbers and hyphens in slugs. It lowercases capitals, transliterates non-Latin characters and drops special characters. Any Framer URL that breaks those rules changes, and needs a redirect.
Translate the existing redirects. Export Framer's redirects with the Redirect Sync plugin. Framer writes a wildcard as an asterisk, with :1 captures and named segments such as :year. Webflow writes the same rule with a (.*) capture group and %1 in the target, and needs a % before special characters in the old path, including the hyphen and underscore. Webflow runs redirects oldest first, so add specific rules before wildcards. It has no hard cap but recommends 1,000 rules at most.
Our website migration SEO checklist covers the crawl, the redirect map and the 30 days after launch.
Carrying the design system across
Nothing converts, so the aim is to rebuild the system, not each page. Webflow's migration article asks you to record "reusable layout patterns and design tokens" during the audit, then build a global style guide before any page.
Tokens first. List Framer's colour styles, text styles, spacing and radii. Recreate them as Webflow variables, then build classes on top, so the brand colour still changes in one place.
Components second. Rebuild the navigation, footer, cards and CTA blocks as Webflow components, with properties for the parts that change.
Breakpoints third. Framer's Academy explains that the width shown for a breakpoint is the minimum viewport width at which it applies. Webflow works from a desktop base: tablet applies at 991 pixels and below, mobile landscape at 767 and below, mobile portrait at 479 and below, with optional larger breakpoints at 1280, 1440 and 1920 that cascade upwards.
Test each template at the widths where the two systems disagree, such as 800 to 1000 pixels. A layout that switched to tablet at one width in Framer will switch at another in Webflow.
Fonts and motion last. Webflow's article tells you to confirm a licence for every font before you upload it. Motion that relied on Framer's built-in effects needs redesigning with Webflow's GSAP-based interactions or custom code.
The cutover
When the URLs stay the same, Google's guidance on changing hosting applies, not the one for site moves with URL changes. Its steps: prepare and test the new host, lower DNS TTL in advance, switch DNS, monitor, and shut the old host down once everyone, Googlebot included, reaches the new one.
- Publish to Webflow's staging subdomain and test every template and form.
- Lower the TTL. Google suggests a few hours, at least a week in advance; Webflow suggests its lowest value, often 30 seconds, one full TTL period ahead.
- Add redirects before the switch, as Webflow's migration article insists.
- Find out who holds the domain. A domain claimed through Framer's free domain offer is managed at Hover; any other sits with the registrar you bought it from.
- Point DNS at Webflow: an A record to 198.202.211.1, a CNAME for www to cdn.webflow.com, and the _webflow TXT record. Webflow issues SSL once the records point at it.
- Check that canonicals point at the live domain, then keep the Framer project running until Search Console shows clean crawling.
Our WordPress to Webflow migration checklist has the long version of these launch steps.
What this means for your Framer to Webflow migration
If URLs stay the same and the CMS is modest, the risky part of this move is small. The work sits in the rebuild: tokens, components, breakpoints and motion. In our four-week marketing-site process, we would spend the first week on the URL inventory, the field map and the design tokens, before building any page.
Our own Webflow builds run two to three weeks per site, and our largest Webflow CMS holds over 1,200 items. We quote each migration per project once the URL list and the collection count are known. Our marketing website service page explains how we scope a Framer to Webflow rebuild.
