Webflow to Framer migration: when it pays, what imports, and a step-by-step plan

The short answer

Moving from Webflow to Framer pays when your team is small, design-led and paying Webflow for seats and languages. For a typical bilingual marketing site with three people, Framer costs USD 336 to 576 a year less than Webflow's 2026 pricing, so a rebuild takes years to pay back on price alone. Move for the workflow, not only the bill.

There's no one-click importer. As of 17 October 2026, Framer's own migration guide has you rebuild the pages and import the CMS from Webflow's CSV exports. Framer's agent can draft pages from your live URL, a third-party plugin moves related collections in one pass, and redirects need Framer's Pro plan.

Don't switch if the site has more than about 10,000 CMS items, sells online, needs more than ten editors, or depends on tools that don't work with Framer. The rest of this guide prices one site both ways, lists what imports and what doesn't, and gives a step-by-step plan and checklist.

When it pays: one site priced both ways

The site: 30 designed pages, a blog with posts, authors and categories (three collections, about 600 items), English and Spanish, 70 GB of traffic a month. A marketing lead owns it, a designer builds pages and a writer publishes posts. Prices are Webflow's and Framer's own, read on 17 October 2026 (Webflow pricing, Framer pricing).

The difference is USD 336 a year. If the Spanish pages need translated URLs, Webflow needs Localize Advanced at USD 29 a locale, and the gap grows to USD 576. Billed monthly, it's USD 1,740 against USD 1,380, a gap of USD 360.

Before the renewal, this site would have been on Webflow's old Business plan, USD 39 a month with 100 GB (Webflow pricing as archived on 11 May 2026), so the 2026 change itself added only USD 72 a year. Most of the gap is seats and languages, which Webflow didn't reprice (Webflow blog).

The break-even is simple division. At USD 336 a year, every USD 1,000 you spend on the migration takes about three years to recover; at USD 576, about 21 months. Our website migration cost guide collects published prices for Webflow moves, and our Webflow renewal calculator prices your own site on both platforms.

Two timing notes:

• Sites in Freelancer or Agency Workspaces, and sites on 2022-or-earlier pricing, move to Webflow's new prices at a renewal on or after 16 November 2026. Switching to yearly billing before then keeps the current plan for one more year (Webflow blog).
• The case reverses for content-heavy sites. With 15,000 CMS items in 12 collections, Webflow Premium still costs USD 25, while Framer Pro needs USD 40 for items and USD 40 for collections on top of USD 30. With the same two seats, that's USD 948 a year on Webflow and USD 1,680 on Framer.

What Framer can import from Webflow in 2026

Sources: Framer's step-by-step guide, Migrating with Agents, the Webflow Import plugin (published 29 September 2026) and Framer Help on bulk redirects.

Framer is explicit that Webflow's code export won't help much: it's useful for collecting assets and inspecting markup, but the CMS, forms, search, localization and ecommerce don't come with it (Framer's guide).

If a Framer Expert runs your move, ask about Switch: Framer gives Experts up to 50,000 AI credits per approved client site moving to Framer, valid for three months (Framer Switch). Framer's own advice is to treat the agent's output as a first pass that a person checks.

The plan, step by step

1. Take inventory

List every URL (static, CMS, localized and campaign pages), every collection with its fields and references, every form and where it sends, and every integration: analytics, consent, CRM, chat, embeds and custom code. Mark each page keep, rebuild, merge, redirect or remove. Crawl the live site and save each URL's title, description, canonical and status code; you'll compare against this list at launch.

If your site once used Webflow Logic or User Accounts, those features are gone (retired on 27 June 2025 and 29 January 2026), so the site already runs on a replacement such as Zapier, Make, Outseta or Memberstack (Webflow). Check that the replacement works with Framer before you plan anything else.

2. Export everything from Webflow

• Each collection to CSV, from the CMS panel. The file holds only the locale in view, so export once per language. Multi-references come out as comma-separated text, rich text as HTML, and images and files as links to Webflow's hosting (Webflow Help).
• Every image and file. Webflow warns that those links break if you delete the site, including images inside rich text. Download them now, or have the import copy them into Framer.
• Your 301 redirects, from Site settings, Publishing, 301 redirects, as CSV (Webflow Help).
• Form submissions, as CSV.

3. Pick the Framer plan

Most migrations need Pro. Basic can't hold redirects, staging, more than two collections or more than 30 designed pages, and its limits don't grow (Framer pricing). Our Framer pricing 2026 guide has every limit and add-on.

4. Build the system on one page

Framer's guide recommends rebuilding one representative page first, one with the navigation, repeated sections, CMS content, a form and the responsive patterns, then reusing that system everywhere. Webflow classes become Framer text and color styles, variables and components; Webflow symbols become components; breakpoints are set up again for desktop, tablet and phone. A Webflow site with years of one-off class combinations usually comes out simpler.

5. Move the CMS

1. Create the collections and fields in Framer first.
2. Import referenced collections (authors, categories) before the ones that point at them (posts).
3. Test a handful of representative items, then import the rest.
4. Check slugs, dates, rich text, images, options and references on a real list page and a real detail page.

Keep every slug unchanged unless you have a reason not to. Each unchanged URL is one redirect you don't need.

6. Rebuild the interactions

Webflow's interactions don't transfer. Framer's guide maps them to effects, component variants or code. List them, rebuild the ones that help the story, and drop the rest. This is often where a migration pays off in page speed.

7. Recreate the languages

Map each Webflow locale to a Framer locale, at USD 20 a month each, up to 20 (Framer pricing). Framer can translate page paths and CMS slugs per locale (Framer Help), so you can match your current Spanish URLs or improve them with redirects. Framer sets the lang and hreflang tags itself, and you can't edit them (Framer Help). Webflow exports one CSV per locale; bring in the translations for a few items first and check them in every locale, since how translated fields map depends on the import route you use.

8. Rebuild forms and integrations

Framer's native forms send to email, Google Sheets or a webhook, and it has built-in integrations for HubSpot, Typeform and Formspark; anything else embeds (Framer Help). Match required fields, consent text, success messages and tracking. Then add analytics, tag manager and the consent banner, and test each on the production domain.

9. Set up redirects

Only changed or removed URLs need one. In Framer, redirects live in Site Settings, Hosting, Redirects, on Pro (Framer Help):

• * matches any path segment: /blog/* covers every post.
• :1, :2 reuse what the wildcard matched in the new URL.
• Named segments such as /blog/:year/:month/:day match exact patterns.
• Only paths on the same domain can be redirected. A domain change is redirected at the old domain's host.
• Renaming a page or CMS path in Framer doesn't update existing redirects. Update them by hand.

For bulk imports, the Redirect Sync plugin takes a CSV with from and to columns, plus an optional expandToAllLocales column:

from,to
/post/old-pricing-guide,/blog/pricing-guide
/team/*,/about

Our redirect map generator matches your Webflow and Framer sitemaps and exports the CSV.

10. Check SEO before the switch

On the Framer staging domain, check:

• every important URL returns the page or a single redirect, with no chains;
• titles, descriptions, canonicals and Open Graph images match your crawl from step 1;
• structured data is back: Framer takes JSON-LD as custom code (Framer Help);
• the sitemap, robots.txt and the 404 page;
• the staging domain isn't indexable.

Framer's SEO migration guide adds one point people miss: use Google's Change of Address tool only if the domain changes, not for a platform move on the same domain.

11. Switch the domain

Connect the domain in Framer, update DNS, wait for SSL and run the checks again on the live domain. Keep the Webflow site and plan until everything is verified.

Large sites can move in stages. With Framer's Advanced Hosting add-on (USD 200 a month billed yearly), a Multi Site rule sends any path Framer doesn't have yet back to the Webflow site, so pages go live one by one at the same URLs (Framer Help).

12. Watch the first weeks

Submit the sitemap in Search Console, inspect your top pages, and fix 404s and redirect chains as they appear. Keep redirects in place for as long as possible, generally at least a year, as Google's site-move guidance recommends. Cancel Webflow only after every image and file has been re-hosted. Our website migration SEO checklist covers the 90 days after launch.

When not to switch

• A large CMS. Framer Pro includes 2,500 items and 10 collections and stops at 40,000 and 40 with add-ons. Webflow Premium includes 20,000 items and 40 collections. Past about 10,000 items, Framer usually costs more, as the example above shows.
• Selling online. Framer has no built-in store, and its own comparison page says Wix "deserves the shortlist" when native commerce, bookings or payments matter (Framer). If you sell through Webflow Ecommerce, stay, or plan a separate store.
• More than ten editors. Framer's Basic and Pro stop at ten people with edit access; an eleventh means Enterprise. Webflow sells as many seats as you need.
• Fine-grained roles. Framer's Pro roles are Design, Content and Deploy per project (Framer Help). If you rely on Webflow's site-level roles and publishing permissions across many sites, compare carefully.
• Member areas or app logic. Framer's pricing page lists password protection but no member accounts, so whatever replaced Webflow's User Accounts has to support Framer.
• Code you'll want back. Webflow's paid Workspace plans export a site's code. Framer says it doesn't offer HTML export for self-hosting (Framer Help). If owning the code matters, look at moving Webflow to Astro instead.

For every other destination and its running cost, see Webflow alternatives in 2026. For the platform choice itself, Webflow vs Framer compares editing, CMS, languages and lock-in.

The checklist

Before:

• Crawl of every URL with title, description, canonical and status saved
• URL map: keep, redirect, merge or remove for each URL
• Each collection exported to CSV, once per locale
• Every image and file downloaded
• 301 redirects and form submissions exported
• Replacements for Logic, User Accounts and other integrations confirmed to work with Framer
• Framer plan chosen (Pro if you need redirects or staging)

During:

• One representative page rebuilt and approved
• Referenced collections imported first, then the rest
• Interactions rebuilt or dropped on purpose
• Locales, translated paths and slugs checked
• Forms, analytics and consent tested
• Redirects added and tested, no chains
• Metadata, canonicals and JSON-LD restored
• Staging domain kept out of search

After:

• DNS and SSL live, checks repeated on the domain
• Sitemap submitted, top pages inspected
• 404s and redirect errors fixed weekly for the first month
• Webflow cancelled only after assets are re-hosted

What to do next

Price your site on both platforms in the Webflow renewal calculator, then build your redirect list with the redirect map generator. If you'd rather hand the move over, Dardo runs it as a website migration or a full Framer development project.