A Webflow migration, in either direction, is a development project. The code export carries static HTML, CSS and JavaScript only: CMS content stays behind, forms stop sending data, site search and ecommerce stop working. Collections export separately as CSV files, to be reimported by hand. The question became urgent again in 2026, because the May repricing removed the CMS and Business plans and cut the included bandwidth.

The marketing director of a B2B company with 45 million in revenue opens the renewal email in July 2026. The Business plan the site runs on no longer exists. The renewal moves to the new Premium plan, and at current traffic it will need an extra bandwidth package too. Time to redo the maths on staying and optimising versus moving elsewhere.

Evaluate both directions with the same data. What changed in the 2026 pricing, what you actually take with you from the export, how much work it takes to rebuild the rest, and the checklist that keeps your organic rankings intact.

Key Takeaways

• From 13 May 2026 Webflow replaced the CMS and Business plans with a single Premium plan at $25 per month billed annually. More CMS items included (20,000), but bandwidth down to 50 GB against the 100 GB of the old Business plan. Existing sites move over at their first renewal from 29 June 2026.

• The code export is partial by design: HTML, CSS, JavaScript and static assets yes; CMS content, forms, site search, ecommerce and memberships no. Collections come out as CSV files only.

• Migrating to Webflow makes sense when the bottleneck is marketing autonomy. Migrating away makes sense when you need a custom backend and deep integration with your business systems.

• A migration without traffic loss rests on three pillars: a one-to-one 301 redirect map, parity of titles, meta and structured data, and 90 days of monitoring in Search Console.

• If the site is more than three or four years old, migrating it pixel-for-pixel is usually a wasted opportunity: the right moment to migrate is also the right moment to rethink it.

What changed in 2026: the new Webflow pricing

On 13 May 2026 Webflow reorganised its site plans. The two plans most business projects ran on, CMS and Business, were replaced by a single plan, Premium.

• Price billed annually: $25 per month

• Price billed monthly: $39 per month

• CMS items included: 20,000

• Collections: 40

• Static pages: 300

• Bandwidth included: 50 GB

• Extra bandwidth: packages at $20 per month for 50 GB

Included CMS items go up sharply: the old CMS plan allowed 2,000, Premium allows 20,000. Webflow removed the CMS item add-ons, because at that ceiling they are no longer needed. Bandwidth goes the other way: the old Business plan included 100 GB, Premium includes 50.

The repricing moves the bill in two different directions. For a content-heavy site with moderate traffic the bill goes down, sometimes a lot. For a high-traffic site that sat comfortably inside the old 100 GB, it goes up, because extra packages are now required.

There are three transition dates. New purchases follow the new pricing from 13 May 2026. Existing sites move at their first renewal or first billable change from 29 June 2026. Sites managed inside Freelancer and Agency workspaces follow from 16 November 2026.

Practical note

Before any strategic assessment, do a ten-minute job: open the dashboard, check the bandwidth used over the last twelve months and your plan's renewal date. Those two numbers tell you whether the repricing is a saving or an increase for you. Plenty of teams decide to migrate over a feeling of being overcharged that the numbers do not confirm. Current pricing is published at webflow.com/pricing.

Migrating to Webflow: when it makes sense

Companies moving into Webflow almost always come from WordPress, and for the same reason: the marketing team cannot publish on its own.

It makes sense when the bottleneck is organisational before it is technical. Marketing wants to change a page without opening a ticket. Plugin maintenance has become a job of its own. The site is slow, and isolating which plugin is slowing it down takes a dedicated audit. In cases like these Webflow solves a real problem, and solves it well: the visual editor is mature and the animations are high quality without writing JavaScript.

It is worth knowing what entry costs, because quotes rarely include it. WordPress content has to be remapped onto Webflow collections, which are structured differently. Features that were plugins on WordPress (complex forms, member areas, advanced search, ecommerce) have to be rebuilt or replaced with external services. It is a rebuild with the same content.

Migrating away from Webflow: the signals it is time

Webflow does not "go bad" at some point. You take the project past the boundary where Webflow is excellent. Five concrete signals.

The CMS item ceiling. The Premium plan includes 20,000 items and 40 collections. Generous for an editorial site, tight for a product catalogue or a records database: past that ceiling the only option is Enterprise, on quote. You hit it after launch, when the catalogue fills up, and it is one of the best documented reasons for leaving.

You need deep integration with business systems. When the site has to read from and write to an ERP, a CRM or a management system in real time, you reach the limits of a closed platform quickly. Sending a form to an automation service is a different kind of job.

You need business logic on the server. Member areas with real permissions, custom calculations, approval flows and dynamic pricing all require a backend of your own.

The costs at scale stop adding up. Bandwidth over the threshold, localisation features, extra workspace seats: these grow with the business, and past a certain volume they exceed the cost of owning your infrastructure.

You want full ownership. Not just of the design, but of the system: data, code, runtime. That is a strategic choice, not a technical one.

For projects like these the usual destination is a custom build on Next.js and a headless CMS. Marketing keeps its editorial autonomy, and underneath there is a backend you can extend without waiting for someone else's roadmap.

What you take with you, and what you don't

This is the section that determines the real cost of the migration. Webflow allows a code export, but the export has a precise perimeter.

• HTML, CSS, JavaScript: Exported, working

• Images and static assets: Exported

• CMS collection content: Not included in the code: collection lists come out empty and template pages do not generate the individual item pages

• Contact forms: Exported visually, but they do not send data: they depended on the Webflow backend

• Site search: Does not work: it depended on Webflow-side indexing

• Ecommerce: Does not work: catalogue, cart and checkout are platform features

• Member areas and user accounts: Not included

• Localised pages: Not included

CMS content exports separately: one CSV per collection, from the export icon in the collection panel. It has to be repeated for each one, one at a time.

Inside that CSV sits the trap that costs the most. Image and file fields do not contain the files: they contain URLs pointing at the hosting of the original Webflow project. As long as that project stays active the links work, and the migration looks successful. The day you cancel the subscription and delete the project, every image on the new site breaks along with the old one. Webflow itself recommends keeping the original project alive as a backup, or downloading the assets before closing it.

The second sore point is reference and multi-reference fields, the links between one collection and another. In the CSV they come out as text, and the relationships have to be rebuilt at the destination, through the API or by hand.

Two line items come out of this, and they need a name and a price in the quote. First: who downloads the assets from Webflow's CDN and uploads them to the new platform. Second: who rebuilds the links between collections. If neither is there, you are holding a quote that treats a migration as an export followed by an upload.

The SEO checklist for a migration without traffic loss

It is identical in both directions. It is the part of the project that never shows up in the mockup, and it decides whether organic traffic holds.

1. A complete URL inventory. Not just the sitemap: a crawl of the site plus the page export from Search Console, to catch URLs that receive traffic but are linked from nowhere.

2. A one-to-one 301 redirect map. Every old URL points to its equivalent new page, not all of them to the homepage. A blanket redirect to the homepage costs more traffic than any other migration mistake.

3. Parity of on-page elements. Titles, meta descriptions, H1s and structured data get transferred, not rewritten during the migration. If you want to rewrite them, do it afterwards, as a separate and measurable change.

4. Parity of performance. Measure Core Web Vitals before and after. If LCP and INP get worse after the migration, you have paid for a slower site.

5. New sitemap submitted in Search Console. With a crawl request for the main pages.

6. 90 days of monitoring. Query by query and page by page against the previous period. Some settling in the first weeks is normal. A drop that has not recovered after a month has a specific cause, almost always in the redirect map.

The reference documentation is Google's guide to site moves with URL changes: it is the document to validate the plan against before executing it.

What drives the cost of a Webflow migration

The cost of a Webflow migration depends on four variables, and the source platform is not one of them. Measure them yourself before asking for a quote: they are the same four questions anyone serious will ask you.

How many pages and how many collections. Count static pages, collections and the items inside each one. An eight-page brochure site and a site with four collections and eight hundred items are not the same project. The number that drives the quote is the CMS item count, more than the number of designed pages.

How many features have to be rebuilt. Forms, search, member areas, ecommerce: each one is a piece of work in itself, as the export table above shows. Count them one by one and get a time estimate for each, instead of a single total.

Whether you migrate at design parity or redesign. Replicating an existing design on a different technology is more laborious than it looks, and it is worth deciding before you start.

How much content has to be remapped by hand. Count the fields per item, the references between collections and the images to reassociate: this is the line that scales worst, and the one quotes underestimate most often.

If the site is more than three or four years old, migrating it identically is a waste. You are paying for the most tedious work there is, replicating something dated, to end up with the same site on different infrastructure. During a migration the marginal cost of rethinking the project is at its lowest, because everything is being rebuilt anyway.

When not to migrate

In a good share of cases the correct conclusion is to stay.

If the reason for migrating is only irritation at the new pricing, and the site works, the numbers do not add up. On subscription alone you are talking about a few hundred dollars a year: $25 a month for Premium, $20 a month for each extra bandwidth package. A migration costs many multiples of that. If the site is recent and the design holds, and the limits you feel are about content, the right move is to optimise. Clean out unused collections, compress assets to cut bandwidth, review the plan.

A migration makes sense when there is a structural limit: impossible integrations, a backend you need, ownership of the system, or costs that grow with the business faster than the value they generate.

What to do now

Before committing to a Webflow migration in any direction, three actions you can run this week.

1. Check your plan's transition date and your bandwidth usage over the last twelve months. Those are the two numbers that say whether the repricing hits you as an increase or a saving.

2. Export the inventory of URLs and collections. You need it in any scenario, and it tells you the real size of the project.

3. Calculate your Webflow cost for the next twelve months under the new pricing, extra bandwidth included. Then compare it with what you are spending today, not with what you imagine you will spend.

We work on both sides of the migration: we build on Webflow and on our own Next.js and Payload CMS stack, so we have no structural interest in pushing you in either direction. Some of the work is in our case studies. If the numbers say it is time to move, let's talk with the inventory in hand. And we will tell you when the right answer is to stay where you are.