Skip to content
Blog 14 min read

Framer to Webflow migration: when it makes sense and how to keep your rankings

Category:
SEO
Updated:
Oct 31, 2026

Ask AI about this article

When moving from Framer to Webflow is worth it, when it isn't, and how to move the CMS, redirects, metadata, forms and analytics without losing rankings.

Artyum Grebenyuk, founder of AGR Studio Artyum Grebenyuk Founder, AGR Studio

TLDR:

Move from Framer to Webflow when you've outgrown Framer's CMS, need deeply nested CMS pages or a static code export, or your team already runs Webflow; don't move for SEO alone, since both give you the same controls. It's a rebuild: CMS collections move as CSV, while layouts, components and interactions are rebuilt by hand. Keep every URL or 301 it in Webflow's syntax, rebuild forms and analytics, and expect a few weeks of ranking movement.

Move from Framer to Webflow when your content has outgrown Framer's CMS, when pages need deeply nested CMS content or you want a static code export, or when the team that will own the site already works in Webflow. Don't move for SEO alone: both platforms give you titles, descriptions, sitemaps, canonicals, 301 redirects and structured data, and any platform move brings a few weeks of ranking movement. If you do move, treat it as a rebuild with a content import, not a transfer: keep every URL or redirect it, carry over metadata and schema, and rebuild forms and analytics before the domain switches.

Our bias, stated once: we're an Official Framer Expert, we also build on Webflow, WordPress, Next.js and Astro, and our own site left Framer in October 2026 for Astro and Sanity, not for Webflow. Prices and limits below are as of October 2026 and link to each vendor's own pages. The checklist that applies to any platform is in how to migrate your website without losing SEO; this guide covers what is specific to Framer and Webflow.

Framer vs Webflow on the limits that usually trigger a move

FramerWebflow
CMS items1,000 on Basic, 2,500 on Pro; up to 40,000 on Pro with add-ons20,000 on Premium
CMS collections2 on Basic, 10 on Pro; up to 40 with add-ons40 on Premium, 100 on the Team plan
Pages30 on Basic; 150 on Pro, then $20 per 100, up to 700300 static pages on Basic and Premium; CMS item pages don't count toward it
RedirectsPro plan onlyAny paid Site plan, with CSV import and export
Editor seatsContent editor $10/month, full editor $20/month; up to 10 edit seats on Basic and ProLimited seat $15/month billed yearly ($19 monthly); full seat $39 ($45)
Languages$20 per locale a month, up to 20 localesLocalize: $9 per locale a month (up to 3) or $29 (up to 10), billed yearly
Code exportFramer's help centre contradicts itselfStatic HTML, CSS and JavaScript on paid Workspace plans, without the CMS, forms or code components
Custom code componentsReact, "React 18 compatible"React, server-rendered by default
Agent access (MCP)Official server, free during previewOfficial server on all Site plans

Sources: Framer pricing, Webflow pricing, Webflow dynamic content limits, Webflow code export, Framer code components, Webflow code components, Webflow MCP.

When does moving from Framer to Webflow make sense?

When you've hit a limit Framer can't lift at a price you accept, or the people who will run the site already know Webflow. These are the cases where we'd say yes.

  • The CMS is outgrowing Framer. Framer Pro includes 2,500 CMS items and 10 collections; add-ons take a Pro site to 40,000 items and 40 collections (Framer pricing). Webflow Premium includes 20,000 items and 40 collections at $25 a month billed yearly, $39 monthly (Webflow pricing). A blog, a resource library, a changelog and an integrations directory together can pass a few thousand items. Price Framer's add-ons against your own item count before deciding.
  • Pages pull in a lot of related content. Webflow allows up to 40 Collection lists per page, up to 10 nested lists and three levels of nesting (Webflow). That matters for directory pages, such as an integrations hub where each integration lists its use cases and each use case lists customers.
  • You want a code export as an exit or a backup. Webflow exports static HTML, CSS, JavaScript and assets on paid Workspace plans, though without CMS content, form processing, site search, code components or secondary locales (Webflow). Framer's position on code export is unclear (see below).
  • The team that will own the site already knows Webflow. A new head of marketing who runs Webflow, or an in-house Webflow developer, is a good reason on its own. The editor your team opens every week matters more than any row in a feature table.
  • The site needs app-like parts on the same platform. Webflow Cloud deploys full-stack apps built with frameworks such as Next.js and Astro from GitHub. Mounting them on your custom domain isn't available on the Starter or Basic plans.

When should you stay on Framer?

When the reason to move is SEO, editor cost or a sense that Webflow is "more serious". None of those hold up on their own.

  • For SEO alone. Framer delivers pre-rendered HTML and has per-page titles and descriptions, an automatic sitemap, canonical URLs, 301 redirects and JSON-LD through custom code (Framer SEO). Webflow has the same set. Google says to "expect temporary fluctuation in site ranking during the move" (Google), so a move made only for rankings starts by costing some.
  • Your editors are designers who live on the canvas. A Figma-like editor is one of the three reasons clients gave us for choosing Framer, and Webflow's Designer works differently.
  • Editor seats are your biggest running cost. A Framer content editor is $10 a month. Webflow retired its legacy Editor on 5 October 2026, so new editors on your own Workspace need a limited seat at $15 a month billed yearly or $19 monthly (Webflow).
  • You run more than 10 languages. Framer's locale add-on goes up to 20 locales. Webflow Localize Advanced stops at 10 and Essential at 3 (Webflow pricing).
  • The real problem is the content. A rebuild on another builder won't fix a homepage that leads with the solution before the problem.
  • You want full control of the code. Then the move is to a framework and a headless CMS, not to another builder. That's what we did with our own site; the options are compared in our website platform comparison for 2026.

What can you export from Framer?

Your CMS content, yes. Your design, no. Plan for a rebuild.

  • CMS collections. Framer says its CMS content "can be exported using plugins into structured formats such as CSV or JSON" (Framer). Framer's own CMS Export plugin exports a collection as a CSV file. Export each collection and open the file before planning the import: check that slugs, formatted text and image links came through the way you expect.
  • Site code. Framer's help centre contradicts itself. One article says "Framer does not provide a way to export published sites as HTML files or static website bundles" (Framer); the porting article says you can download the published files "at any time and move them to any hosting provider". For a move to Webflow it doesn't matter, because Webflow imports content as CSV, not a site's code.
  • Design, components and interactions. Webflow's own Framer migration guide is plain about it: "There's no automated way to convert a Framer site into a Webflow site," and "Framer designs, layouts, and interactions can't be imported directly into Webflow" (Webflow).
  • Assets and fonts. Framer exports images and pages from the canvas as PNG or JPG, so take SVG icons, logos and font files from the original design files, and confirm your font licences cover use on Webflow.

How do you move Framer CMS collections into Webflow?

Build the content model in Webflow first, then import one CSV per collection, starting with the collections other collections point to. The details below are from Webflow's CSV import guide.

  1. Model before you import. One Webflow Collection per Framer collection, with matching field types. On non-Enterprise plans a Collection can have up to 10 reference fields (Webflow).
  2. Import referenced collections first. Authors and categories go in before posts. Webflow turns a plain-text reference into a slug ("Charles Dickens" becomes charles-dickens) and matches it; if the item has a custom slug, put that slug in the CSV, or the reference stays empty. Separate multi-reference values with semicolons.
  3. Keep each file under 4 MB. That's the upload limit per CSV, so split long collections into batches. Webflow offers a backup before each import; take it.
  4. Rich text comes in as HTML. Webflow accepts any value in a rich text field, including embeds, but it "may clean up embeds to remove elements, classes, and attributes it doesn't support". Check every item that had a custom embed.
  5. Images import by URL, without responsive variants. Image fields take a direct URL, but those images "don't get responsive image variants (srcset and sizes)", so import images that are already sized, or upload the important ones directly. Keep the Framer site published until the import is done, so every image URL still resolves.
  6. Files don't import. No CSV data maps to Webflow's file field. Upload PDFs and other downloads by hand.
  7. Option fields take up to 100 values. An option field created from a CSV column holds at most 100 options; a longer list becomes its own Collection with a reference field.

How do you rebuild Framer components and interactions in Webflow?

By hand, with the live Framer site as the reference, and with a chance to drop what doesn't earn its place.

  • Styles and components first. Rebuild the type scale, colours, spacing and global components such as navigation, footer and cards, then the pages from them. It's the order Webflow's guide recommends, and the order we build any site in: homepage first, then the remaining pages from its components.
  • Interactions. Framer's appear, hover and scroll effects become Interactions with GSAP, the default on new Webflow sites, with ScrollTrigger, SplitText and staggers built in. Keep the motion that explains the product and drop the decoration.
  • Code components. Framer's are React and "must use React 18 compatible code" (Framer). Webflow's are React only, brought in through DevLink, and need the Premium plan. Because both sides are React, the component logic can often be reused; Framer's property controls and anything tied to Framer's runtime get rewritten. Webflow server-renders code components by default (Webflow); leave that on for anything with text you want indexed.
  • Overlays. In Framer, "overlays are not rendered in the HTML during the first load" (Framer). If important copy sits in a Framer overlay, the rebuild is the moment to put it on the page.

How do you keep your URLs and redirects?

Keep every URL that can stay the same, and give every other one a 301 in Webflow before the domain switches. Framer's redirects stop working the moment DNS moves, so every rule is rebuilt in Webflow's syntax.

  • Static pages. Webflow supports nested folders for static pages, so paths like /solutions/fintech can stay as they are.
  • CMS pages. The Collection URL is "the slug for the folder that holds your Collection pages", so items live at paths like /blog/post-name (Webflow). Set it to match Framer's path and most CMS URLs need no redirect. Webflow says "only static pages can be organized in folders", so a Framer CMS path two levels deep, such as /resources/guides/:slug, can't be copied as is and needs redirects.
  • Languages. Webflow's 301s "won't apply to localized slugs or subdirectories", so /old-url and /es/old-url are two separate rules. If your Framer site translates its paths, you need Localize Advanced, which adds localized URLs.

The redirect syntax differs between the two (Framer, Webflow):

FramerWebflow
A whole folder/blog/* to /articles/:1/blog/(.*) to /articles/%1
Several captured parts/blog/*/post/* to /article/:1/entry/:2/blogs/(.*)/(.*) to /articles/%1/%2
Rule orderDrag to set priorityOldest rule runs first, so add specific rules before wildcards

Two Webflow details catch teams out. A CSV import of redirects "removes any existing redirects on your site", so export first and merge (Webflow). Characters such as ? and = in an old path need a % in front of them. And there is no hard limit on rules, but Webflow recommends 1,000 at most, because the rules add to a file visitors' browsers download; use wildcards where a whole folder moves.

What happens to metadata, structured data and llms.txt?

Nothing carries over by itself, so capture it from the live site and rebuild it deliberately.

  • Titles and descriptions. Crawl the live Framer site and record each URL's title, description, canonical and Open Graph image. That's the final output, with CMS variables already filled in. Import the CMS ones as fields and bind them on the Collection template; set static pages in page settings.
  • Canonicals. Set Webflow's global canonical tag to your domain with https and without a trailing slash; with the slash, every subpage's canonical gets a double slash (Webflow).
  • Sitemap. Webflow generates sitemap.xml on each publish, with a lastmod date per URL, and adds it to robots.txt (Webflow).
  • Structured data. In Framer, JSON-LD goes in custom code with CMS variables, including fields pulled through a reference, such as an author's name (Framer). Webflow has a schema markup field in page settings, Collection pages included, where you bind CMS fields, but "Reference, Multi-reference, and Multi-image Collection fields aren't supported in schema markup" (Webflow). If your Article schema names the author, add a plain-text author field to posts.
  • llms.txt. Framer serves it as an uploaded well-known file. On Webflow you upload it in the SEO settings; it's served on the custom domain only, UTF-8 and under 100 KB (Webflow).

What about forms, analytics and integrations?

Every form and tracking script is rebuilt and tested, because the old endpoints stop receiving anything once the domain points at Webflow.

  • Forms. Framer forms send to email, Google Sheets or a webhook (Framer). Webflow forms store submissions in the site settings, send notification emails and export to CSV (Webflow), with unlimited submissions on Basic and Premium. Rebuild each form or embed your CRM's own, re-point every Zapier, Make or CRM automation, and send a real test through each one. If your backend checks the signature on Framer's webhook requests, that check needs replacing too.
  • Analytics. Framer's built-in analytics keep 30 days of history on Basic and 90 on Pro, and they stay with the Framer project. Run GA4 for a few weeks before the switch so you have a baseline. Webflow's Google Analytics integration takes a GA4 measurement ID; Webflow's own analytics, Analyze, is a paid add-on.
  • Scripts. Move consent banners, tag manager, verification tags and chat widgets into Webflow's site or page custom code.
  • Search Console. Verify the domain through DNS, so the property keeps working after the switch.

What does it cost to run the site on Webflow instead of Framer?

About the same in platform fees. The rebuild is the real cost.

Assumptions: a 20 to 40 page B2B site with a blog, English only, under 50 GB of bandwidth a month, one owner plus two content editors, list prices in USD as of October 2026, excluding tax, domain and build work.

Per monthFramerWebflow
Site planBasic $10 (up to 30 pages) or Pro $30 (redirects, staging)Premium $25 billed yearly, $39 monthly (Basic has no CMS)
Two content editors$20$30 billed yearly, $38 monthly
Total$30 to $50$55 to $77
Each added language$20 per locale$9 to $12 per locale (Essential) or $29 to $35 (Advanced)

Sources: Framer pricing, Webflow pricing. If your Framer site uses redirects, it's already on Pro, so the like-for-like comparison is closer to $50 against $55 to $77.

The rebuild is where the money goes. We quote 3 to 5 weeks for a standard B2B site, and in our estimate a Framer site rebuilt in Webflow sits in that range even with no redesign, because layouts, components and interactions are rebuilt rather than copied. That assumes a clean content model and no new pages; a large CMS or several languages push it longer.

How long does a Framer to Webflow migration take?

Plan on the build time above, plus a few weeks after launch for search engines to catch up.

  • Week one. Audit URLs, collections, existing redirects, forms, scripts and fonts. Build the content model, export the CSVs and draft the redirect map.
  • The middle weeks. Styles and components, then pages; CMS imports; interactions; forms and integrations.
  • The final week. Metadata and schema pass, a crawl of the staging site against the live one, redirects loaded, QA on every breakpoint and locale, then the DNS switch. Webflow's guide says redirects "should be added before your domain cutover".
  • After launch. Google says a small to medium-sized site "can take a few weeks for most pages to move", and to keep redirects "generally at least 1 year" (Google). On the same domain, that means keeping the rules in Webflow.

Before and after the switch, run the usual checks: crawl both sites and compare pages, titles and canonicals; make sure no redirect points at another redirect or at a missing page; on day one, run every old URL and confirm a 301 to the right page, then a 200; submit the new sitemap in Search Console and Bing Webmaster Tools; then watch the Pages report for new 404s for a month. Keep the Framer project until those checks are done.

What we've seen on client projects

  • Why teams pick Framer is why they hesitate to leave it. In 101 client conversations from January to October 2026, platform choice came up in 46% and Framer was named in 34. The reasons given for Framer: the marketing team edits without a developer, hosting is included, and the editor feels like Figma.
  • The Framer issue we flag most is content inside custom code components that may not render without JavaScript; native components are server-rendered. A move to Webflow fixes that only if the rebuilt components render on the server, which Webflow's code components do by default.
  • What we ask for in any migration: CMS access, because it shows hidden pages and existing redirects a crawl misses, plus GA4 and Search Console access to see which pages earn traffic. The migrations we've run came from Craft, Squarespace, WordPress, React and Webflow.
  • Our own move off Framer put about 80 redirect rules live at the switch, 91 today after later renames, and we compared the old and new sites page by page before moving DNS. The destination was different, the mechanics are the same.
  • What a Framer team gives up. We gave up on-canvas editing and instant publishing by a designer when we left Framer for code. Webflow keeps a visual canvas, so a Framer team moving there loses much less of that than we did.

If you're weighing a move off Framer and want a second opinion on whether it's worth it, tell us about the site.

FAQ

Can you export a Framer site to Webflow?

Not automatically. Webflow's own migration guide says there's no automated way to convert a Framer site and that Framer designs, layouts and interactions can't be imported. What does move is CMS content: Framer's CMS Export plugin produces a CSV per collection, which Webflow imports into its CMS. Pages, components and interactions are rebuilt in Webflow using the Framer site as the reference.

Will I lose SEO if I move from Framer to Webflow?

Not if every URL either stays the same or gets a 301 redirect in Webflow before the domain switches, and titles, descriptions and structured data are carried over page by page. Expect some movement anyway: Google says rankings fluctuate during a move and a small to medium site can take a few weeks to settle. Keep the redirects for at least a year, as Google recommends.

Is Webflow better than Framer for SEO?

Neither ranks better by default. Both offer per-page titles and descriptions, sitemaps, canonical tags, 301 redirects and structured data, though Framer's redirects need the Pro plan. The differences are in details: Framer overlays and code components that skip pre-rendering are missing from the HTML, while Webflow's schema field can't bind reference fields. Content and links matter more than the platform.

How much does Webflow cost compared with Framer?

As of October 2026, a 20 to 40 page site with a blog and two content editors costs about $30 to $50 a month on Framer and $55 to $77 on Webflow. Framer is Basic $10 or Pro $30 plus $10 per content editor; Webflow is Premium at $25 billed yearly or $39 monthly plus $15 to $19 per limited seat. The rebuild costs more than either.

How long does a Framer to Webflow migration take?

For a standard B2B site, plan on roughly 3 to 5 weeks of rebuild work, which is our estimate based on our usual build quotes, because layouts, components and interactions are rebuilt rather than copied. A large CMS or several languages push it longer. After launch, allow a few weeks for Google to process the new site.

Do Framer redirects carry over to Webflow?

No. Framer's redirects stop working once the domain points at Webflow, so each one is recreated in Webflow's syntax: a folder rule like /blog/* to /articles/:1 becomes /blog/(.*) to /articles/%1. Webflow can import redirects from a CSV file, but an import replaces all existing rules. Localized paths need their own rules.

Blog

Continue reading our latest blogs

Free 20-min intro call

Tell us what you’re building

Tell us about your goals and we will reply within a day with a clear scope and next steps.

Trusted by founders and marketing teams Rated 4.95 out of 5 across 40 reviews on Contra