Dardo
Start a project
ENESPT
ENESPT

Webflow to Framer migration with your CMS, languages and URLs intact

We rebuild Webflow sites in Framer: styles and components recreated on the canvas, collections imported locale by locale, interactions remade as Framer effects and Webflow's redirects carried into Framer Pro. Every URL that earns traffic keeps its path or gets a redirect, and the full list of old URLs is tested on staging before DNS moves.

By Nicolas Ceron13 min read
Get a proposalMessage us on WhatsApp
Dardo / Editorial illustration
On this page

Why teams move from Webflow to Framer

Teams usually move for the workflow and find that the bill helps. Framer suits a small, design-led team that changes pages often and wants a preview before anything goes live. Framer Pro includes staging and branches, and publishing to the live site is limited to members holding the Deploy permission; on Webflow, isolated staging comes only with the Team plan at USD 2,500 a month.

People and languages also cost less on Framer. Prices as of October 2026, billed yearly, per month:

  • A designer who publishes: USD 20 as a Framer editor, against USD 39 for a Webflow Full seat
  • A writer who updates the CMS: USD 10 as a Framer content editor, against USD 15 for a Webflow Limited seat
  • A language with translated URLs: USD 20 a locale on Framer, against USD 29 on Webflow Localize Advanced
  • Bandwidth: 100 GB included on Framer Pro, 50 GB on Webflow Premium

The site plan itself costs more on Framer, USD 30 for Pro against USD 25 for Webflow Premium, so any saving comes from seats and locales. On fees alone, a rebuild takes years to pay back. Move when the team will work better in Framer.

Webflow and Framer compared for this move

Both are hosted visual builders, so this move trades one platform for another rather than buying code ownership. In a migration, the differences that matter are content limits, redirects, languages and who can publish. Plans are as listed in October 2026; our Webflow vs Framer comparison goes further into editing and motion.

Webflow and Framer compared for this move
AreaWebflowFramer
HostingWebflow's CDN on every site planFramer's hosting; 300+ CDN locations on Pro
PublishingFull and Limited seats; staging only on the Team planEditors and content editors; staging, branches and a Deploy permission on Pro
CMS limits20,000 items and 40 Collections on Premium2,500 items and 10 collections on Pro; add-ons up to 40,000 and 40
LanguagesLocalize: 3 locales on Essential, 10 with translated URLs on AdvancedUp to 20 locales with translated paths and slugs; hreflang set automatically and not editable
RedirectsOn every paid site planOn Pro and Enterprise, with wildcards and CSV import through a plugin
Structured dataSchema markup supported in the platformJSON-LD added as custom code
Code exportHTML and CSS on paid Workspace plans, without CMS contentNo HTML export for self-hosting
Edit seatsAs many as you buyUp to 10 people on Basic and Pro

What comes across from Webflow, and what doesn't

Framer has no importer for whole Webflow sites. Framer's own migration guide has you rebuild the pages and bring CMS content in from Webflow's CSV exports. It also notes that Webflow's code export helps to collect assets and inspect markup, but doesn't recreate the CMS, forms, search, localization or ecommerce. Our Webflow to Framer guide lays out the steps in order; item by item, this is what travels:

  • CMS collections: each comes out as a CSV per locale, rich text as HTML and multi-reference fields as comma-separated text
  • Images and files: exported as links to Webflow's hosting, which Webflow warns break once the site is deleted, rich-text images included
  • 301 redirects: exported as CSV from Webflow's publishing settings and brought into Framer through the Redirect Sync plugin
  • Interactions: don't transfer, so each is rebuilt or dropped
  • Forms: rebuilt; past submissions stay in a CSV downloaded from Webflow
  • Logic and User Accounts: gone from Webflow since 27 June 2025 and 29 January 2026; the tools that took their place, such as Zapier, Make, Outseta or Memberstack, need to work with Framer too
  • Ecommerce: Framer's plans include no native store, so a Webflow Ecommerce site keeps its store elsewhere
  • Several linked collections at once: Webflow Import, a third-party plugin, carries references, galleries and images inside rich text, for USD 49 per project or USD 99 for unlimited projects

How a Webflow build maps to Framer

Nothing converts automatically, so the mapping is a design decision as much as a technical one. Framer's guide advises settling the system on a single representative page, one with the navigation, repeating sections, CMS content, a form and the responsive layouts, before rebuilding anything else. Years of one-off Webflow classes are a chance to cut the style list down.

How a Webflow build maps to Framer
In WebflowIn FramerHow it moves
Classes and global stylesText and color styles, variables and componentsRebuilt on the representative page, then reused
Symbols and componentsComponents with variantsRecreated once and placed everywhere
BreakpointsDesktop, tablet and phone breakpointsSet up again and checked at each size
Interactions on scroll, hover and loadEffects, component variants or codeListed, then rebuilt or dropped on purpose
CMS collections and fieldsCollections with matching fieldsCSV per collection, referenced ones first, a few test items before the rest
Reference and multi-reference fieldsReferences between collectionsLinked once both collections exist, or carried by the Webflow Import plugin
Localize localesFramer locales with translated paths and slugsOne CSV per locale, translations checked item by item
301 redirectsRedirects in Framer's hosting settingsCSV with from and to columns, through Redirect Sync
FormsFramer forms to email, Google Sheets, a webhook, HubSpot, Typeform or Formspark, or an embedSame fields, consent text and destinations
Custom code and schemaCustom code; JSON-LD for structured dataAdded back per page or template
Images and filesAssets hosted by FramerDownloaded from Webflow, then uploaded or copied by the import plugin

How we move a Webflow site to Framer

The inventory lists every URL Webflow serves (static pages, CMS items, localized versions and campaign pages), each collection with its fields and the references between them, each form and its destination, and each script, from analytics and consent to CRM, chat and embeds. Landing pages from a year or more of Search Console and analytics data, and pages with links from other sites, are flagged, and every URL gets one of four decisions: keep, redirect, merge or retire.

Nothing in Webflow is touched until the exports are safe: each collection once per locale, every image and file, the current 301 list and past form submissions. The Framer project starts on Pro, because Basic has no redirects or staging and stops at 30 designed pages and two collections. We build on Framer's staging domain, blocked from indexing, import referenced collections first and leave CMS slugs as they are unless there's a reason to change them, because an unchanged URL needs no redirect.

Framer's redirect rules take wildcards, yet they only work for paths on the same domain, and renaming a page or CMS path later leaves existing rules unchanged, so they can end up pointing at a dead path. So the map is written 1:1 from the inventory and tested against every old URL in every locale. Our free redirect map generator matches the Webflow sitemap with the Framer staging sitemap and exports a CSV ready for Redirect Sync.

On switch day the domain is connected in Framer, DNS updated and SSL confirmed, with redirects active and each form sending a real submission; the checks then run again on the live domain. A large site can go over in stages: Framer's Advanced Hosting add-on, USD 200 a month on yearly billing, passes any path Framer doesn't serve yet back to the Webflow site. Indexing and clicks are measured against the baseline at 30 and 60 days. The whole scope is set out under website migration, and new design work in Framer under Framer development.

Checks before and after the Framer switch

Each check runs on Framer's staging domain and again once DNS points at Framer. Our website migration SEO checklist carries the list through the 90 days after launch.

  • The full list of old URLs, in every locale, returns the page itself or one redirect to it, never a chain
  • Titles, descriptions, canonical tags and social images match the pre-move crawl
  • Localized paths match the plan for each language; Framer writes lang and hreflang itself, so the output is checked rather than edited
  • Structured data is back as JSON-LD custom code and passes a test
  • Forms deliver real submissions to each destination, with the same consent text
  • Analytics, tag manager and the consent banner fire on the production domain
  • Sitemap, robots.txt and the 404 page are checked, and the staging domain stays out of search
  • The sitemap goes to Search Console; Framer's SEO guide reserves Change of Address for a new domain, not a platform move
  • Redirects kept for a year or longer, with indexing and clicks compared at 30 and 60 days

The migration scope closes after the 60-day comparison. Content and technical search work past that point is a separate SEO engagement.

When to stay on Webflow

Framer is not an upgrade for every Webflow site. Stay, or choose a different destination, in these cases:

  • A large CMS: Premium's 20,000 items and 40 Collections cost USD 25 a month on Webflow, while Framer Pro starts at 2,500 items and 10 collections, with add-ons stopping at 40,000 and 40
  • For example, 15,000 items in 12 collections cost USD 30 + 40 + 40 = USD 110 a month for the Framer site plan, against USD 25 on Webflow Premium
  • A store on Webflow Ecommerce that you want to keep on the same platform
  • More than ten people with edit access: Framer's Basic and Pro stop at ten, and the eleventh means Enterprise
  • Site-level roles and publishing rights across many sites; Framer's Pro roles are set per project: Design, Content and Deploy
  • Code you may want back: Webflow exports a site's code on paid Workspaces, and Framer offers no HTML export for self-hosting
  • Speed as the only reason: in September 2026, 80.2% of Webflow sites and 81.7% of Framer sites in the United States passed Core Web Vitals on mobile

When a renewal prompted the question, check where the site is billed. A site on monthly billing in a Freelancer or Agency Workspace that moves to yearly billing before 16 November 2026 keeps its current Webflow plan for one more year, time enough to decide without pressure. If owning the code is the goal, Webflow to Astro moves the same content into a repository in your name.

What Framer costs to run after the move

Framer charges each site its own plan, and each person with edit access per workspace. Framer's October 2026 prices are shown in US dollars, excluding tax. The workspace owner and viewers are free.

What Framer costs to run after the move
LineBilled yearly, per monthBilled monthlyNotes
BasicUSD 10USD 1530 pages, 2 collections, 1,000 items; no redirects
ProUSD 30USD 45150 pages, 10 collections, 2,500 items, 100 GB, redirects and staging
EditorUSD 20USD 30Designs, edits and publishes
Content editorUSD 10USD 15CMS, translations and on-page text
LocaleUSD 20USD 25Up to 20, translated paths included
10,000 more CMS itemsUSD 20USD 30Pro only, up to 40,000
10 more collectionsUSD 40USD 50Pro only, up to 40
100 GB more bandwidthUSD 40USD 50Pro only, up to 2 TB
Advanced HostingUSD 200USD 250Framer serves some paths while another platform serves the rest

Our step-by-step guide prices one bilingual 30-page site with a blog and three people both ways: USD 960 a year on Framer Pro and USD 1,296 on Webflow's 2026 pricing, a gap of USD 336. Put your own plan, seats and locales into the Webflow pricing calculator, which sets Framer next to Webflow, and read Framer pricing in 2026 for every limit and add-on.

Dardo has no fixed price for this move. A proposal is built from the URL inventory, and its size follows the URLs and templates, collections and references, locales, interactions worth rebuilding, forms and integrations. Published market prices for Webflow moves are collected in what a website migration costs.

Questions before you choose

Will we lose rankings moving from Webflow to Framer?

Avoidable losses, no. Google warns that rankings move around while a migrated site is recrawled, and that movement is temporary. Lasting damage comes from a dropped URL, title or canonical, so CMS slugs stay, every changed URL gets a redirect on Framer Pro, and metadata and structured data are restored and checked. No one can promise rankings; the 30 and 60-day reviews measure them against the baseline.

Can Framer import our Webflow site directly?

Not as a whole. Framer's migration guide, as of October 2026, rebuilds the pages on Framer's canvas and brings collections in from the CSV files Webflow exports. Webflow Import, a third-party plugin, can move several linked collections in one pass with their references and images. Layouts, components and interactions are always rebuilt.

Can we keep our Webflow URLs and CMS slugs?

Usually. Keep each page path and CMS slug as it is on Webflow and that URL needs no redirect. Framer can also translate paths and slugs per locale, so Spanish or Portuguese URLs can match what you have now. Any URL that does change needs a redirect, and redirects require Framer Pro.

What happens to our Webflow Interactions?

They don't transfer. Framer's migration guide maps each one to a native effect, a component variant or code. Each interaction is rebuilt or dropped on purpose, and the ones that carry the page's story are the ones worth the time.

How do our Webflow Localize languages move to Framer?

Every Webflow locale gets a Framer counterpart. A Framer locale costs USD 20 a month on yearly billing at October 2026 prices, up to 20 of them, and translated page paths and CMS slugs come with it. Since Webflow exports one CSV per locale, translations are imported and then checked item by item. Framer writes the lang and hreflang tags on its own; they can't be edited.

Can our editors still publish in Framer?

Yes. A designer who publishes needs an editor seat, USD 20 a month on yearly billing, and a writer a content editor seat, USD 10, for CMS items, translations and page text. On Pro, pushing staging to the live site takes the Deploy permission. Basic and Pro both cap edit access at ten people.

When should we cancel the Webflow plan?

Only after the Framer site answers every old URL on the live domain and every image and file is re-hosted. Webflow's CSV exports point images at Webflow's hosting, and Webflow warns those links break if the site is deleted. The handover lists when each old plan can be canceled.

How long does a Webflow to Framer migration take?

The rebuild depends on the number of URLs, templates, collections, locales and interactions, plus how quickly approvals come back. Search settles more slowly than the build: Google's site-move guidance puts it at a few weeks for most pages on a modest-sized site, and the 30 and 60-day reviews cover that period.

What does a Webflow to Framer migration cost?

We quote it from the URL inventory: URLs, templates, collections and references, locales, interactions and integrations set the scope. Framer's own fees come on top: Pro is USD 30 a month on yearly billing in October 2026, before seats and locales. For prices other providers publish for Webflow moves, see our website migration cost article.

From the blog

Sources & further reading

Sources behind this page, with further detail from the original publishers.

Plan the Framer move before your Webflow renewal

Send your Webflow URL, your plan and renewal date, and a count of collections and locales. We reply with the questions that set the scope: which URLs change, how references move and which interactions are worth rebuilding.