Is Moving from Webflow to Next.js Worth It? Migration Cost and Break-Even

The question usually arrives as a renewal invoice. The site works, nobody wants a redesign, and yet the platform under it costs more every year than the site seems to need. Moving to Next.js is a real option, and it is also the option agencies like ours have an obvious interest in selling. So this guide does the arithmetic in the open: what staying on Webflow actually costs, what moving costs once and then every year, when the numbers break even, and when they never will.

One real example runs through it. ELCora, an online English school, had its landing page on Webflow for a year. We rebuilt the same design on Next.js and Payload CMS and moved it to our own hosting: a $20-a-month Webflow subscription became a $5-a-month hosting bill, with no visible design change. The full story is in the ELCora case study. Everything else below is an assumption, and labelled as one.

What staying on Webflow costs in 2026

Webflow reworked its plans in May 2026: the CMS and Business site plans were merged into a single Premium plan, and existing sites on them moved across automatically (Flow Ninja, updated August 2026). According to the Webflow pricing page as checked in October 2026, all prices in USD, per site, before tax:

• Basic: $15 a month billed yearly — custom domain, 300 static pages, 10 GB bandwidth, no CMS.
• Premium: $25 a month billed yearly — the CMS with 20,000 items and 40 collections, from 50 GB bandwidth.
• Billed monthly instead, Basic is $25 and Premium $39 a month (Flow Ninja, August 2026).
• Extra bandwidth on Premium: +50 GB costs $20 a month billed yearly, +100 GB costs $40.
• Workspace seats: a Full seat (design and admin) is $39 a month per seat and a Limited seat (edit content, build pages from components) is $15 a month per seat, both billed yearly. One full seat is included for the Workspace owner.
• Team, the first platform plan, starts at $2,500 a month on an annual contract.

The site plan is the line everyone looks at. The seats are the line that grows. A content site where two people edit copy pays for the plan and for two Limited seats, every month, for as long as the site exists. That is the number to put into the break-even, not the headline plan price.

What moving to Next.js costs

Moving has one large cost and three small recurring ones. The large one is the migration itself: porting the design, modelling the CMS, moving the content, carrying the URLs and search signals over and cutting the domain across. It is a fixed, one-off project, and its size depends on the number of distinct templates, the CMS structure and the integrations, not on the page count alone. One specialist vendor publishes fixed tiers starting at $1,500 for a small site (PandaCodeGen, October 2026). For how 99 Francs scopes and prices this work, see Webflow to Next.js migration.

The recurring costs after the move:

• Hosting. A Next.js and Payload site with a Postgres database runs on a small container. For reference, Railway's Hobby plan is $5 a month including $5 of usage, and its Pro plan $20 a month per workspace including $20 of usage; Vercel's free Hobby plan is for non-commercial use only, so a business site starts on Pro at $20 a month per developer seat (both checked October 2026). ELCora runs for $5 a month.
• Editing. Payload CMS lives inside the same application and stores content in your own database, so an extra editor is a new user account, not a new monthly seat.
• Upkeep. This is the line Webflow quietly covers and a code site does not: framework and dependency updates, security patches, backups. On a site that is not otherwise changing, budget a few hours a year of a developer's time.
• Change requests. A new section type or a new page layout is now a small code change rather than a Designer session.

Staying versus moving: the yearly numbers

The table compares the running cost only. The migration fee and upkeep hours are left out on purpose, because they are the two numbers that differ by project; the next section shows how to set them against these savings. Webflow figures are from the pricing page in October 2026; self-hosted figures are assumptions chosen to be generous to Webflow, not the cheapest possible setup.

Assumptions behind the rows: all Webflow prices billed yearly unless stated, before tax; one Workspace owner seat included, so only additional editors are counted; no Workspace plan upgrade, no ecommerce, no localisation. Self-hosted figures include the database. A site with heavy traffic, file uploads or background jobs will need more than $40 a month, and a Webflow site that never adds an editor will save less than the content-site rows.

The break-even, worked through

The break-even point is simple to write down: divide the one-off migration cost by the monthly saving after upkeep. Monthly saving after upkeep is the Webflow bill, minus hosting, minus whatever a few hours of developer time a year costs you, spread over twelve months.

• Within 1 year: the migration has to cost less than the first-year saving in the table, minus a year of upkeep. For the busy content site that is a budget of up to $840 before upkeep. For a brochure site it is $120–240, which no honest migration costs.
• Within 3 years: the budget triples. The content site with two editors frees up $1,260 over three years, the busy one $2,520, the ELCora-sized site $540, all before upkeep.
• Never, on money alone: when the saving is around $10–15 a month and you pay a developer by the hour for every dependency update, upkeep can absorb the whole saving. That is the common case for a small, rarely edited Webflow site.

Read that last point carefully, because it is the honest answer for many small sites. ELCora's saving is real — a quarter of the previous running cost — but $180 a year is not why a migration is worth doing. What the client got was the rest: her own admin panel with seven collections she controls (pages, pricing plans, teachers, reviews, FAQ, media and incoming leads), enquiries forwarded to Telegram, and a site with no dependency left on a platform she no longer pays for. The hosting saving pays for itself slowly; the ownership is the larger part of the value.

When ownership and limits matter more than money

Some reasons to leave Webflow do not appear in any cost table, and they are often the decisive ones:

• You want the code, not a licence. Webflow's code export gives you the HTML, CSS and JavaScript of your pages, but CMS content is not included: exported collection lists show their empty state, and site search and forms stop working (Webflow Help Center). A Next.js repository, its database and the hosting account are yours outright.
• The site needs logic. Forms that write into your own database, notifications, calculators, gated content, scheduled jobs and real integrations run as server code in Next.js instead of embedded third-party scripts.
• The CMS has become the product. Premium includes 20,000 CMS items and 40 collections, and the content management API is rate-limited (120 requests a minute on Premium, per the pricing page). A headless CMS such as Payload gives you relationships, roles, drafts and an API that can feed an app or a second site.
• Pricing risk. A plan can be repriced or merged, as the CMS and Business plans were in 2026. A site you host can still change price, but you choose the provider and can move it.

When staying on Webflow is the better choice

Webflow is a good platform, and for a lot of teams it is the right one. The visual Designer is the real product: a marketer can build a new landing page from components, ship it the same afternoon and never open a terminal. A Next.js site with Payload gives editors control over content, but a genuinely new layout is still a developer task. If that would slow you down, the saving is not worth it.

Decision checklist: move or stay

Move to Next.js if:

• Your Webflow bill includes several seats or bandwidth add-ons, not just a site plan.
• Your team edits content (copy, prices, people, posts) but rarely builds new page layouts.
• You need server logic, your own database or integrations Webflow handles through workarounds.
• You want to own the code and content outright, or have been caught out by a plan change.
• You have access to a developer — in-house, freelance or an agency — for a few hours of upkeep a year.

Stay on Webflow if:

• Your marketing team builds and launches new pages in the Designer weekly and values that speed.
• You have no development budget at all after launch, even for occasional updates.
• Your whole bill is a single Basic or Premium plan with no extra seats, and the site works.
• You rely on Webflow-specific features you would have to rebuild, such as Localize, Optimize or ecommerce, and the rebuild costs more than years of the subscription.
• A redesign is coming within a year anyway — do the platform decision as part of it, not twice.

Moving without losing search traffic

Most migration horror stories are not about the new platform. They are about redirects nobody mapped and pages nobody checked. A Webflow to Next.js move is SEO-neutral when it carries these over:

• A full URL inventory from the live site, and identical URLs wherever the new routes allow it.
• A 301 redirect for every address that does change, verified against the inventory after launch.
• Parity for titles, meta descriptions, headings, canonicals, structured data, sitemap and robots rules.
• All images, fonts and files pulled off the Webflow CDN into the project before the subscription is cancelled.
• Forms, analytics and conversion tracking re-tested with real submissions, then Search Console checked after the cutover.

That is how the ELCora move was run: URLs, titles, meta descriptions and structured data moved with the site, and the metadata stayed editable in the CMS with the original strings as the floor. The full checklist is on Webflow migration without losing SEO.

How to get a straight answer for your site

The break-even depends on three numbers only you have: what Webflow charges you each month in total, how many people edit the site, and what you would need the site to do that it cannot do now. Send us the site URL and your current monthly Webflow costs, and we will tell you whether moving is worth it — including when the answer is to stay. If it is worth it, the scope and fixed price come from the Webflow to Next.js migration service.