migrating toBrowse playbooks
← All playbooks
Publishing migration

Framer → Webflow

Rebuild a Framer site in Webflow. Export each Framer CMS collection with a plugin as CSV or JSON, then import into Webflow collections. Framer says published output is HTML, CSS, JavaScript, and assets you can download. That download is not a Webflow project. Forms and interactions are a rebuild.

Typical timeline12–30 business days50–110 hours active work
Statusneeds review
Source profileFramer data portability article reviewed 2026-10-31
Destination profileWebflow CMS import help reviewed 2026-10-31
Documentation date
Review window
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

Framer

Reasons to stay
  • 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
Reasons to leave
  • 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
New platform

Webflow

What gets better
  • Visual design, CMS, hosting, and interactions give designers strong production control
  • Editors get a purpose-built publishing workflow instead of raw files
What gets worse
  • Pricing, collection limits, and proprietary structure constrain portability
  • Themes, extensions, and content models add maintenance and portability constraints
Best of the move

Webflow: Visual design, CMS, hosting, and interactions give designers strong production control. This removes a major source-side concern: CMS exports go through plugins, and the published site is not a portable Designer or WordPress project.

Worst of the move

What you lose: A Figma-like canvas, components, and effects let small teams publish marketing sites quickly. What you inherit: Pricing, collection limits, and proprietary structure constrain portability.

Connected catalog

2 destinations are documented from Framer. Compare nearby routes before committing.

Also from Framer
Jump to a section
01At a glance

Know the shape of the move.

Transfer outcome12 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 5, Manual rebuild: 5, Not transferred: 2.
Clean0
Partial5
Manual5
Lost2
Mapping route9 of 10 fields have a destination path

This timeline assumes

  • A marketing or content site. Webflow Ecommerce and Membership are out of this playbook unless you already have a replacement plan.
  • You can export Framer CMS collections through a plugin as CSV or JSON. Framer’s 15 September 2026 portability article says that is the CMS path.
  • Framer stays published until Webflow no longer loads Framer-hosted images.
  • The site already documents Webflow → Framer and Framer → WordPress as nearby routes.
  • Webflow CSV import is limited to 4 MB per file. Split large collections.
02What transfers

What survives the move.

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

ItemOutcomeImpactWhat happensMitigation
Published HTML exportpartialhighFramer’s portability article, updated 15 September 2026, says you can download published HTML, CSS, JavaScript, and assets and host them elsewhere. That package is not a Webflow Designer project.Use the download as a visual and asset reference. Rebuild pages in Webflow.
CMS collectionspartialcriticalFramer CMS exports through plugins as CSV or JSON. Webflow imports CSV into a collection you already created. You can update matching items if the CSV has IDs Webflow can link.Create collections and fields first. Import a sample. Then import the rest.
Rich text and referencespartialcriticalPlugin CSV columns for rich text, images, and references need a mapping pass. Image fields may still point at framerusercontent.com.Keep HTML where you can. Import referenced collections first. Re-host images.
Components, effects, and variantslosthighFramer components and effects do not become Webflow symbols or interactions.Rebuild the system page first. Recreate only the motion you still need.
FormsmanualcriticalFramer form destinations do not become Webflow forms.Recreate fields, validation, and notifications. Test on the Webflow domain.
RedirectsmanualcriticalFramer redirects do not import into Webflow. Copy the list from Framer site settings.Enter Webflow 301s for every changed path. Test before DNS.
LocalizationmanualhighExport each locale or collection view you still publish. Webflow import can target a locale view.Import locale by locale. Compare counts.
Custom code and analyticsmanualhighHead snippets, consent, and embeds are a new install.Inventory each snippet. Test after publish.
Editor and plan limitspartialmediumCiaran Coulstock compared Framer Pro pricing with Webflow CMS and Business plans after a Framer rebuild. That is one person’s 2025 plan math, not current pricing.Check today’s collection, editor, and locale limits on both sides.
Hosting and DNSmanualcriticalYou will replace Framer’s published records with Webflow’s. Keep Framer live until SSL and redirects pass.Connect the domain in Webflow first. Switch DNS second.
Draft versus published itemspartialhighConfirm the plugin export marks drafts. Webflow import can create new items or update matches.Do not publish imported drafts by accident.
Page-by-page Framer hostinglostmediumAny Advanced Hosting split you used on the way into Framer does not help you leave.Treat this as a full domain cutover unless you build your own split.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
Framer projectWebflow sitemanualRebuild pages.
CMS collection CSV or JSONWebflow collection importtransform4 MB cap per file.
Reference fieldWebflow referencetransformImport the referenced collection first.
Rich textWebflow rich texttransformCheck inline images.
Image URL on FramerWebflow assettransformRe-host.
SlugWebflow slugtransformKeep keep-URLs identical.
Component or effectWebflow symbol or interactionmanualRebuild.
FormWebflow formmanualNew destination.
Framer redirectWebflow 301manualCopy the list.
Published HTML zipNo destinationunsupportedReference only. Not a Designer import.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Keep Framer CMS exports, a URL crawl, and the published file download.

  1. Export each CMS collection as CSV or JSON.
  2. Download published site files if you need a static snapshot.
  3. Crawl URLs and redirects.
  4. Save images that still sit on Framer hosts.
  5. Screenshot components and forms.

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

Transformation · Framer CMS export plugin plus Webflow Import

Webflow CSV import

Load Framer items into Webflow collections.

  1. Create the Webflow collection.
  2. Upload a CSV under 4 MB.
  3. Map columns, including slugs and references.
  4. Choose update-matches or import-as-new on purpose.

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

Transformation · Webflow Assets

Asset re-host

Stop production pages from depending on Framer file hosts.

  1. Find framerusercontent or other Framer hosts in rich text.
  2. Upload originals.
  3. Replace the URLs.
  4. Recheck after publish.

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.

Design

You treat the HTML download as a Webflow import

highpossible likelihood

Someone unzips Framer HTML and expects Designer classes.

Consequence
Weeks of broken layout work.
Mitigation
Use the download as reference. Rebuild in Designer.

Stop if: The launch plan depends on pasting exported HTML into Webflow.

Import

CSV larger than 4 MB

highpossible likelihood

Webflow rejects the file.

Consequence
A collection never loads.
Mitigation
Split the export. Import in batches.

Stop if: A required collection cannot import after a split attempt.

Content

Images still on Framer

criticalpossible likelihood

Webflow rich text still requests Framer asset URLs.

Consequence
The site breaks when you cancel Framer.
Mitigation
Re-host before cleanup.

Stop if: A high-traffic page still hotlinks Framer.

06Precise timeline

Do the work in this order.

Estimate forA Framer marketing site with a handful of CMS collections moving into Webflow
Total elapsed12–30 business days
Active work50–110 hours
BufferAdd time for localization or a large component system.
01
Days 1–5Inventory Framer3–5 days
02
Days 5–8Export CMS and snapshot2–3 days
03
Days 8–22Rebuild and import10–14 days
04
Days 22–27Switch DNS2–4 days
05
Days 27–30Observe and close4–7 days
  1. Days 1–5 · inventory

    Inventory Framer

    10–18 hours active3–5 days elapsedOwner review waiting
    • List pages, collections, forms, and redirects.
    • Mark keep URLs.

    Depends on: Framer admin access

    Stop / go checkpoint

    Export?

    Go when: The collection list is signed.

    Stop when: A required collection has no export path.

  2. Days 5–8 · backup

    Export CMS and snapshot

    6–12 hours active2–3 days elapsedExports waiting
    • Run the CMS export plugin.
    • Download published files if needed.
    • Crawl URLs.

    Depends on: inventory

    Stop / go checkpoint

    Build Webflow?

    Go when: Export hashes exist.

    Stop when: A collection export is empty.

  3. Days 8–22 · pilot

    Rebuild and import

    24–60 hours active10–14 days elapsedDesign review waiting
    • Rebuild the system page.
    • Import CMS samples.
    • Re-host images.
    • Recreate forms and redirects.

    Depends on: backup

    Stop / go checkpoint

    Preview OK?

    Go when: Sample pages and forms pass.

    Stop when: Images still depend on Framer.

  4. Days 22–27 · cutover

    Switch DNS

    4–10 hours active2–4 days elapsedDNS and SSL waiting
    • Freeze Framer edits.
    • Import a last CSV delta.
    • Point the domain at Webflow.

    Depends on: pilot

    Stop / go checkpoint

    Webflow is public?

    Go when: URLs, SSL, and forms pass.

    Stop when: A keep URL 404s.

  5. Days 27–30 · observe

    Observe and close

    4–8 hours active4–7 days elapsedSearch and form traffic waiting
    • Watch 404s.
    • Keep Framer 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 Webflow the public site without losing the last Framer edits.

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

  1. Freeze Framer publishing.
  2. Re-export changed collections.
  3. Install Webflow redirects.
  4. Switch DNS to Webflow.
  5. Send a production form test.

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

Return to safety

Rollback

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

Deadline: Before you cancel Framer or delete the project.

  1. Restore Framer DNS.
  2. Export Webflow items created after cutover.
  3. Apply only reviewed items back to Framer if needed.
  4. Keep the Framer CMS exports.

Proof to capture: Framer serves the domain again.

Rollback immediately when
  • High-traffic images still on Framer
  • A keep URL 404s
  • A production form fails
  • CSV import corrupted a collection
  • Redirect loop
08Verification report

Prove the migration worked.

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

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingKeep URLsRequest every URL marked keep.200 on Webflow.Crawl.
V-02BlockingCountsCompare export rows to Webflow items.Counts match or variances are signed.Count sheet.
V-03BlockingImage hostsInspect a CMS sample.No required image depends on Framer.Image-host report.
V-04BlockingProduction submissionSubmit each public form.The destination receives the test.Form receipt.
V-05BlockingRedirectsRequest old Framer paths that changed.One 301.Redirect results.
V-06BlockingTitles and canonicalsCrawl key pages.Approved metadata.SEO sample.
V-07BreakpointsReview the system page at two breakpoints.Accepted layout.Screenshots.
V-08BlockingSingle siteInspect Framer and Webflow publishing.Webflow alone is public.DNS screenshot.
09Post-migration cleanup

Remove the scaffolding safely.

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

  1. Archive CMS exports and the HTML snapshot.
  2. Re-host leftover Framer images.
  3. Keep Framer readable through the retention window.
  4. Cancel Framer only after images and forms are independent.
  5. Revoke migration users.
  6. Schedule the next Webflow backup and redirect review.
Sources and evidence

Verify against the primary material.

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

  1. Framer: porting your data from FramerAccessed 2026-10-31
  2. Webflow: import and export CMS CSVAccessed 2026-10-31
  3. Framer: Webflow to Framer step-by-stepAccessed 2026-10-31
  4. Webflow: migrate your site overviewAccessed 2026-10-31