Publishing migration

Webflow → Framer

Rebuild a Webflow site in Framer. Export each CMS collection as CSV, then import into Framer collections. Classes, interactions, forms, memberships, and ecommerce do not arrive with the CSV. Keep URLs and add redirects before you switch DNS.

Typical timeline12–30 business days50–110 hours active work

Statusneeds review

Source profileWebflow CMS import and export help reviewed 2026-10-31

Destination profileFramer Webflow step-by-step guide reviewed 2026-10-31

Documentation date2026-10-31

Review window2026-10-312027-01-31

Evidence4 sources

This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.

Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Webflow

Reasons to stay

Visual design, CMS, hosting, and interactions give designers strong production control
Editors get a purpose-built publishing workflow instead of raw files

Reasons to leave

Pricing, collection limits, and proprietary structure constrain portability
Themes, extensions, and content models add maintenance and portability constraints

New platform

Framer

What gets better

A Figma-like canvas, components, and effects let small teams publish marketing sites quickly
Editors get a purpose-built publishing workflow instead of raw files

What gets worse

CMS exports go through plugins, and the published site is not a portable Designer or WordPress project
Themes, extensions, and content models add maintenance and portability constraints

Best of the move

Framer: A Figma-like canvas, components, and effects let small teams publish marketing sites quickly. This removes a major source-side concern: Pricing, collection limits, and proprietary structure constrain portability.

Worst of the move

What you lose: Visual design, CMS, hosting, and interactions give designers strong production control. What you inherit: CMS exports go through plugins, and the published site is not a portable Designer or WordPress project.

Jump to a section

01At a glance

Know the shape of the move.

Transfer outcome12 features audited

Clean0

Partial4

Manual6

Lost2

Mapping route9 of 10 fields have a destination path

SourceWebflow10 mapped fields

Automatic0

Transform3

Manual6

Unsupported1

DestinationFramer9 supported paths

This timeline assumes

A marketing or content site, not a Webflow Ecommerce or Membership product you expect to import.
You can export every Webflow collection as CSV. Webflow says an import file can be up to 4 MB. Treat large collections as split work.
Webflow stays published until Framer images no longer load from Webflow or a CDN you will cancel.
The site already documents Webflow → WordPress and Webflow → Ghost if you want those destinations instead.
Design, interactions, and forms are a rebuild. Framer says Webflow code export does not recreate CMS, forms, search, localization, or ecommerce.

02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

Item	Outcome	Impact	What happens	Mitigation
Static pages and URLs	manual	critical	Framer’s guide starts with an inventory. Each page is keep, rebuild, merge, redirect, or remove. There is no page-for-page importer.	List every URL. Rebuild routes that must stay the same before DNS.
CMS collections	partial	critical	Webflow exports a collection as CSV, including archived items on a full export. Framer can import CSV into a collection you already created. References need the referenced collection first.	Create fields, import a sample, then import the rest. Import authors and categories before posts.
Rich text, images, and files	partial	critical	Webflow says most fields export as plain text or URLs. Multi-references export as a comma-separated list. Rich text needs a check after import. Images may still sit on Webflow hosts.	Open list and detail pages. Re-host images you cannot afford to lose when Webflow goes away.
Classes, symbols, and interactions	lost	high	Framer maps Webflow classes to styles, components, or variables. Interactions become effects, variants, or code. Nothing in the CSV rebuilds them.	Set type, color, and spacing styles first. Rebuild one representative page.
Forms	manual	critical	Framer tells you to recreate each form and connect its destination. Webflow form submissions and file uploads do not import.	Match fields, validation, success states, and notifications. Send a test on the production domain.
Memberships, search, and ecommerce	lost	critical	Framer says Webflow code export does not recreate these hosted features in Framer.	Exclude them or replace them with a Framer or third-party setup you already tested.
Localization	manual	high	Webflow CSV export includes items from the current locale view only. Framer localized routes need their own pages and imports.	Export each locale. Match folders before you add redirects.
Redirects	manual	critical	Framer supports exact, wildcard, capture-group, and named-parameter redirects. Old Webflow 301s do not arrive unless you copy them.	Export the Webflow redirect list. Recreate changed paths. Avoid chains.
Custom code and embeds	manual	high	Head code, analytics, consent, and embeds are a new install.	Inventory each snippet. Test on the Framer domain and again after DNS.
Editor collaboration model	partial	medium	Superthread’s first-person writeup left Webflow after single-user editing blocked a three-person team. That is their site, not a Framer guarantee.	Pilot two editors on one Framer page before you commit the rebuild.
CMS collection limits and plan features	manual	high	Ciaran Coulstock’s first-person post hit a two-collection Basic-plan limit after leaving Webflow and paid for Pro. Confirm current Framer plan limits yourself.	Count collections and locales against the plan you will buy.
Page-by-page hosting	partial	medium	Framer documents an optional Advanced Hosting rollout that serves finished Framer routes and falls back to the old site. It says to check availability first.	Use it only if the plan exists for your site. Otherwise switch the whole domain.

03Field and feature mapping

Where each thing goes.

Source	Destination	Method	Notes
Webflow site	Framer project	manual	Rebuild pages.
Collection	CMS collection with fields created first	manual	Match slugs.
Collection CSV	Framer CSV import	transform	Map columns. Import referenced collections first.
Reference and multi-reference	Framer reference fields	transform	Webflow exports names or slugs as text.
Rich text	Framer rich text	transform	Check images and embeds.
Class / symbol	Style, variable, or component	manual	No class import.
Interaction	Effect, variant, or code	manual	Rebuild the ones you still need.
Form	New Framer form	manual	Reconnect the destination.
Webflow 301	Framer redirect	manual	Copy the list. Test each path.
Ecommerce or membership	No destination	unsupported	Not in the CSV path.

04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Keep Webflow CSVs, a URL crawl, and design evidence before you rebuild.

Export every collection CSV, including archived items you still need.
Crawl public URLs, redirects, and image hosts.
Download original images, fonts, and files.
Screenshot templates and list custom code.
Create a Webflow backup if the site is large.

Proof to capture: CSV hashes, URL count, and a named restore owner.

Transformation · Webflow Export plus Framer collection Import

CMS CSV import

Load Webflow items into Framer collections you already designed.

Create the Framer collection and fields.
Import a small CSV sample.
Fix slugs, dates, rich text, and references.
Then import the full file.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · A crawl plus Framer redirects

URL and redirect map

Keep the paths that matter.

Mark each URL keep, redirect, or drop.
Rebuild keep paths first.
Enter redirects for the rest.
Test before DNS.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Content

Images still live on Webflow

criticalpossible likelihood

Imported items request Webflow or CDN URLs you will cancel.

Consequence: The new site breaks after you close Webflow.
Mitigation: Re-host required assets in Framer.

Stop if: A high-traffic CMS page still hotlinks Webflow.

Export

A locale never exported

highpossible likelihood

You exported the default locale only. Webflow exports the current locale view.

Consequence: Translated items never arrive.
Mitigation: Switch locale views and export each one.

Stop if: A published locale is missing from the CSVs.

Cutover

Forms silently drop submissions

criticalpossible likelihood

The Framer form is not connected, or it posts to a staging sheet.

Consequence: Leads disappear after DNS.
Mitigation: Send a test on the production domain.

Stop if: A production form does not deliver a test submission.

06Precise timeline

Do the work in this order.

Estimate forA marketing site with a handful of CMS collections and no ecommerce import

Total elapsed12–30 business days

Active work50–110 hours

BufferAdd time for localization, memberships, or a large design system.

Days 1–5Inventory Webflow3–5 days

Days 5–8Export CSV and assets2–3 days

Days 8–22Rebuild and import10–14 days

Days 22–27Switch DNS2–4 days

Days 27–30Observe and close4–7 days

01
Days 1–5 · inventory
Inventory Webflow
10–18 hours active3–5 days elapsedOwner review waiting
- List pages, collections, locales, forms, and integrations.
- Mark keep, rebuild, or redirect.
Depends on: Webflow admin access
Stop / go checkpoint
Export?
Go when: The URL and collection list is signed.
Stop when: Ecommerce or membership is in scope with no replacement.
02
Days 5–8 · backup
Export CSV and assets
6–12 hours active2–3 days elapsedExports waiting
- Export each collection and locale.
- Download assets.
- Crawl URLs.
Depends on: inventory
Stop / go checkpoint
Build Framer?
Go when: CSV hashes and the crawl exist.
Stop when: A required collection did not export.
03
Days 8–22 · pilot
Rebuild and import
24–60 hours active10–14 days elapsedDesign review waiting
- Set styles and components.
- Rebuild one system page.
- Import CMS samples, then full collections.
- Recreate forms and redirects.
Depends on: backup
Stop / go checkpoint
Preview OK?
Go when: Sample pages, CMS items, and forms pass on desktop and phone.
Stop when: A keep URL is missing or images still depend on Webflow.
04
Days 22–27 · cutover
Switch DNS
4–10 hours active2–4 days elapsedDNS and SSL waiting
- Freeze Webflow edits.
- Import a last CSV delta if needed.
- Connect the domain in Framer.
Depends on: pilot
Stop / go checkpoint
Framer is public?
Go when: URLs, SSL, forms, and redirects pass.
Stop when: A cornerstone URL 404s.
05
Days 27–30 · observe
Observe and close
4–8 hours active4–7 days elapsedSearch and form traffic waiting
- Watch 404s and form delivery.
- Keep Webflow readable.
Depends on: cutover
Stop / go checkpoint
Close rollback?
Go when: No trigger fires.
Stop when: Forms or images regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Framer the public site without losing the last Webflow edits.

Recommended window: A weekday with DNS, design, and content owners available.

Freeze Webflow publishing.
Re-export changed collections if needed.
Install redirects.
Connect the domain in Framer and update DNS.
Send a production form test.

Proof to capture: Framer serves the domain. Keep URLs resolve. Forms deliver. Images do not depend on Webflow.

Return to safety

Rollback

Return the domain to Webflow without losing Framer-era content you still want.

Deadline: Before you cancel Webflow or delete the project.

Restore Webflow DNS.
Export Framer CMS items created after cutover.
Apply only reviewed items back to Webflow if needed.
Keep the CSV backups.

Proof to capture: Webflow serves the domain again.

Rollback immediately when

High-traffic images still on Webflow
A keep URL 404s
A production form fails
A locale is missing
Redirect loop on a cornerstone URL

08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

ID	Check	Method	Expected result	Evidence
`V-01`Blocking	Keep URLs	Request every URL marked keep.	200 on the Framer path.	Crawl.
`V-02`Blocking	Redirects	Request changed Webflow paths.	One 301 to the approved page.	Redirect results.
`V-03`Blocking	Counts and references	Compare CSV rows to Framer items. Open a referenced item.	Counts match or variances are signed. References resolve.	Count sheet.
`V-04`Blocking	Image hosts	Inspect a stratified CMS sample.	No required image depends on a host you will cancel.	Image-host report.
`V-05`Blocking	Production submission	Submit each public form on the live domain.	The destination receives the test.	Form receipt.
`V-06`Blocking	Titles and canonicals	Crawl key pages.	Approved metadata. No accidental noindex.	SEO sample.
`V-07`	Breakpoints	Review the system page on desktop, tablet, and phone.	Accepted layout.	Screenshots.
`V-08`Blocking	Single site	Inspect Webflow and Framer publishing.	Framer alone is public.	DNS screenshot.

09Post-migration cleanup

Remove the scaffolding safely.

Safe after: Seven stable public days, no required Webflow image hosts, and a signed report.

Archive CSVs, crawls, and evidence.
Re-host leftover Webflow images.
Keep Webflow readable through the retention window.
Cancel Webflow only after images and forms are independent.
Revoke migration users.
Schedule the next Framer backup and redirect review.

10Experiences from the field

When the plan met reality.

First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.

First-person accountBrennan Topley · SuperthreadJul 11, 2025

Why we moved our website from Webflow to Framer2025

Brennan Topley writes that Superthread’s three-person team left Webflow after two years because only one person could edit the site at a time. Webflow kicked him out while two teammates were already editing. They rebuilt the marketing site in Framer for real-time cursors, components, and simple motion. The move was a rebuild, not an importer. They lost Webflow-level control over lazy loading and preloading. Tabbed screenshots flickered in Framer because images loaded on click. They still called the move a net win for speed, and they said Framer may be wrong if you need a deep CMS or tight performance control.

What they recommend

Pilot two people editing one Framer page if single-user locking is why you are leaving Webflow.
Rebuild image-heavy UI with Framer’s loading behavior in mind. They could not preload tab images the Webflow way.

Worth noticing

This was a full marketing-site rebuild. CMS CSV import is not what they described.
They traded performance knobs for simultaneous editing and faster iteration.

First-person accountCiaran Coulstock · Ciaran CoulstockApr 14, 2025

I'm kind of pissed off by Framer2025

Ciaran Coulstock rebuilt his personal site in Framer in February 2025 after years on Webflow. He liked the canvas, then hit a two-collection limit on Framer’s Basic plan when he needed a third collection for the blog. Upgrading to Pro was about €40 plus VAT a month, or about €440 a year, which he described as roughly 30% more than his Webflow plan. He also flagged a 100-redirect cap and extra-locale pricing after reading other users. The post is a pricing and CMS-limit report after a Webflow-to-Framer rebuild, not a CSV import log.

What they recommend

Count CMS collections, locales, editors, and redirects against the Framer plan you will buy before you rebuild.
Compare that bill to the Webflow plan that already holds the same collections. His Pro upgrade was the surprise.

Worth noticing

A Framer rebuild can look cheap until a third collection forces a plan jump.
He still preferred Framer’s design feel, and he still thought Webflow scaled content more cheaply.

Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

Framer: Webflow to Framer step-by-stepAccessed 2026-10-31
Webflow: import and export CMS CSVAccessed 2026-10-31
Framer: CSV importAccessed 2026-10-31
Framer: porting your data from FramerAccessed 2026-10-31

Know the shape of the move.

This timeline assumes

What survives the move.

Where each thing goes.

Make the move recoverable.

Create the source-of-truth backup

CMS CSV import

URL and redirect map

The things most likely to hurt.

Images still live on Webflow

A locale never exported

Forms silently drop submissions

Do the work in this order.

Inventory Webflow

Export?

Export CSV and assets

Build Framer?

Rebuild and import

Preview OK?

Switch DNS

Framer is public?

Observe and close

Close rollback?

Cut over with a way back.

Cutover

Rollback

Prove the migration worked.

Remove the scaffolding safely.

When the plan met reality.

Verify against the primary material.