Webflow Migration: What Leaving Webflow Actually Involves

The short version

This page is the map, not the manual. Leaving Webflow is four decisions: do you need to move at all, what breaks when you do, where you land, and who does the work. Each gets a short answer here and a link to the page that goes deep.

The number, up front: $5,000 to $25,000 and 4 to 8 weeks for a 50 to 100 page site, and that band barely moves whichever destination you pick.

One correction first, because it drives a lot of bad advice. There is no Webflow "CMS item wall". The May 13 2026 change raised item limits to 20,000 on Premium and Team. A pitch built on a 2,000 item cap is quoting a plan that no longer exists.

Decision 1: do you actually need to move?

Start here, because for a meaningful share of Webflow owners the answer is no.

Four reasons to stay put

Your site is small and stable. Under roughly 20 static pages, one or two editors, nobody asking for a feature Webflow refused. The migration costs more than the platform does and hands you back a codebase to maintain.

Nobody on your team will own a repo. A design team with no developer ends up with worse lock-in after migrating, not less. A codebase you cannot change is a harder trap than an account you can log into.

You are reacting to the legacy Editor sunset on 2026-08-04. Real date, not a migration trigger. Replacement seats are free with no announced end date, affected users were moved automatically from 2026-05-04 with no action required, and nothing changes about how the live site hosts, renders or handles forms. The one genuine loss is whitelabeling, which only ever applied to Growth and Agency Workspaces.

You think Webflow cannot be driven by AI. It can. Webflow shipped an official MCP server at mcp.webflow.com/mcp in early 2026, listed in Anthropic's connector directory for read and write. It reads site structure, bulk creates and updates CMS items, creates Collections and fields, edits page SEO and Open Graph metadata, and publishes a site. If that was your reason for leaving, it has expired.

Three reasons that hold up

Per-seat pricing. $39 per full seat per month billed yearly, $15 limited. It scales with headcount rather than traffic, and it did not change in May 2026, so it is a standing cost rather than a recent shock.

Where the connector stops. It cannot upload assets to the media library, an open issue on Webflow's own repository since February 2026 with no maintainer response as of July 2026. It cannot create IX3 Interactions. One workspace per authorization. Rate limited to 60 requests per minute on Starter and Basic, 120 above. And no git underneath: no branch, no review, no revert when a bulk edit goes wrong.

Work Webflow will not do. Custom application logic, real site search, anything needing a server you control.

One reason people cite that usually does not apply: the bandwidth cut from 100GB to 50GB hit Business-plan sites moving to Premium. Sites on the old CMS plan saw limits go up. Check which you were on first.

If none of this is you, stay on Webflow. That is a real answer, and we would rather you got it here.

Decision 2: what actually breaks

Most disappointment traces to one belief: that the export button gives you your site. It does not.

• Export is gated on your Workspace plan, not your Site plan. Core, Growth, Freelancer and Agency include it. A free Starter Workspace does not.

• You get HTML, three CSS files, the JS folder, Assets panel images, and *empty* Collection template pages.

• CMS content is not in the export. Collection items and Collection lists are excluded outright. Content moves separately, through the Data API. This is the biggest surprise in the process.

• Also excluded: User Accounts, Ecommerce, password protection, form submission processing, reCAPTCHA, site search, non-primary locales, code components.

• IX2 interactions do export and do work, through the JS folder. Earlier versions of this page said otherwise and were wrong. Lottie needs a web server.

• Forms stop the moment you leave. They post to Webflow's own endpoint. Every one needs a new handler.

The export is a reference for markup and design tokens, not a shippable site. The sequencing that works, phase by phase with the SEO checks in the right order, is in the Webflow migration checklist.

Decision 3: where do you land?

Astro, for content and marketing sites. It ships almost no JavaScript by default, usually the single biggest win over a Webflow build. See the Webflow to Astro guide.

Next.js with Payload CMS, when non-technical people need an admin UI or the site is really an application wearing a marketing site's clothes. See the Webflow to Payload guide.

Another headless CMS, if seat counts or editor habits decide it. Payload, Sanity and Storyblok differ far more in recurring cost and seat limits than in migration effort: the headless CMS guide makes that comparison.

If the choice feels hard, the real question is usually who edits the site after launch, not which framework renders it.

Decision 4: who does the work?

In-house, if you have a developer with spare capacity and the site is not carrying revenue. The risk is not the build. It is the redirect map and the CMS field mapping, which are boring and unforgiving.

Outsourced, if organic traffic matters or the deadline is fixed. What that costs and what to ask a vendor before signing is on the Webflow migration services page, and the money side is broken down in the cost breakdown.

Running costs after launch: $0 to $20 per month on a static-first stack hosted on Cloudflare Pages, or roughly $20 to $50 per month on Vercel with a managed database. Vercel Hobby is non-commercial only, so it is not a licensed option for a site anyone is paid to build.

Two special cases

Ecommerce is not sunset, so moving it is a choice on your timeline rather than a deadline. Products, variants, SKUs, orders and the payment provider are their own project: Webflow ecommerce migration guide.

Gated content. Webflow's User Accounts product was sunset on 2026-01-29, so anyone still gating pages is already running a workaround. The job is porting that workaround plus member records plus per-page access rules: gated content migration guide.

Start where your question is

• Process and sequencing: migration checklist

• Budget: cost breakdown

• Schedule: how long a Webflow migration takes

• Content site: Webflow to Astro

• Admin UI needed: Webflow to Payload

• Choosing a CMS: headless CMS comparison

• Hiring: Webflow migration services