It usually starts the same way. A client opens a Webflow renewal email, or asks for a German version of their site, or hits a CMS warning they did not know existed. The site they were happy with three months ago suddenly feels like a contract they cannot escape.
I have been building on Webflow for years. It is a brilliant tool for a lot of projects. But once a business grows, scales languages, or starts caring about performance and ownership at a serious level, Webflow becomes the bottleneck instead of the solution.
This is a plain-English look at why we move clients off Webflow to a Next.js site with Sanity as the CMS. No code samples, no jargon. Just the pattern I see week after week, and what the alternative actually looks like from a non-technical business owner’s chair.
Why are agencies moving clients off Webflow in 2026?
The base price stays small. Everything else does not.
What we keep seeing is the same pattern. A Webflow site that looked affordable on day one ends up with three or four extra subscriptions stacked on top of it by year two. Site plan. Editor seats. A localization add-on for each language. A CMS upgrade because the content library grew. Sometimes a separate Workspace fee.
None of these are huge on their own. Together they quietly become one of the larger software bills the business runs.
On top of that, Webflow has restructured its pricing twice in the last two years. Even loyal users say they cannot plan around a vendor that keeps changing the rules (Webflow forum: Webflow has become annoying to use). The reason agencies like ours are moving clients off the platform is not that Webflow is bad. It is that the math, the control, and the future have all stopped working in the client’s favour.
What is the real cost of running a Webflow site long-term?
You do not pay once. You pay forever, and the bill grows with you.
Webflow is built around add-ons. The base site plan covers the website itself. After that, almost everything else is a separate paid line. Adding a second language is a paid add-on per locale. Adding editors for your team is a paid seat. Outgrowing your CMS plan means moving up a tier with a meaningful price jump.
The trap is not the price tag on the homepage. It is that you cannot predict what your bill will be in twelve months. As your business grows, every direction of growth (more languages, more team members, more content, more traffic) triggers another subscription.
What clients want at year two is the opposite of that. They want a fixed cost base they understand, and they want growth to make the site cheaper per visitor, not more expensive. Webflow is structured the other way around.
What happens when you outgrow the Webflow CMS?
You either pay more, or you re-architect the site. Neither is fun.
Webflow caps CMS items and CMS collections at every plan tier. A small blog can live on a low plan for years. A site that grows into a real content library (case studies, services, locations, team members, articles) eventually hits a wall.
When you hit it, you have two choices. Upgrade the plan, which is fine until the next ceiling. Or restructure the CMS to use fewer items and collections, which often means re-doing months of editorial work.
This is the part clients hate the most. They paid for a site, the site is finally working, the marketing engine is producing content, and the platform punishes them for using it. The 2026 pricing structure simplified some of this but did not remove the ceiling (Webflow plan update). The cap moved up, the principle did not change.
Why is multilingual content so painful on Webflow?
Every language you add is a separate paid subscription.
For service businesses in Europe, this is the single most painful Webflow problem. Want your site in English and German? That is a localization subscription on top of your site plan. Add French and Spanish? More subscriptions. Each language gets billed monthly, forever.
The actual title of one of the most-upvoted threads on Webflow’s own forum is “Localization is WAY too expensive” (source). The localization UX itself has issues beyond price too. Each language has its own quirks, the editor flow is awkward for clients, and asset localization sits behind a higher tier.
For a Potsdam-based studio like ours, serving German and international clients, this is the moment the conversation about migrating usually starts. A four-language site on Webflow becomes a permanent recurring expense. A four-language site on Next.js with Sanity is a one-time setup. The languages cost nothing extra after that.
Do you actually own a Webflow site?
You own the design. You do not own the engine underneath it.
Webflow lets you export HTML, CSS, and JavaScript. What it does not export is the CMS content, the form submissions, the membership system, or the e-commerce backend. Animations and interactions break when you export. The site is fundamentally tied to Webflow’s servers (Webflow Help Center: Site ownership).
In practice, this means you cannot leave Webflow without rebuilding from scratch. The site you “own” is a static shell, not the working product. If Webflow raises prices, removes a feature you depend on, or has an outage that takes down your business for a day, you have no fallback. You are renting forever.
That is fine when the business is small. It becomes a serious issue when your website is a real revenue source. A site you own outright (the code lives in your GitHub, deployable to any host) puts the power back where it should be. With the business, not the vendor.
Is Webflow safe to use under DSGVO in 2026?
Legally usable, yes. Procurement-safe for serious clients, often not.
Webflow hosts on US infrastructure (Fastly and AWS). The new EU-US Data Privacy Framework from 2023 made Webflow legally usable in Europe again, but Webflow still offers no option to host a site exclusively in the EU. The “European Hosting to comply with GDPR” request is one of the highest-voted items on Webflow’s own public wishlist and remains open (Webflow Wishlist: European Hosting for GDPR).
For most small service businesses this is manageable with a proper data processing addendum and a clear privacy policy. For larger clients (public sector, healthcare, legal, financial, or any business that handles sensitive client data) it remains a blocker. Their compliance teams will ask where the site is hosted, and “the US, under the new framework” is increasingly not a satisfying answer.
A Next.js site can be hosted on an EU-only provider, or even on German infrastructure. The codebase is portable, the data is portable, the hosting decision is yours rather than the platform’s. For DACH businesses with EU enterprise clients, that is often the difference between winning the deal and not.
Why Next.js with Sanity is the stack we move clients to
It removes the ceilings Webflow keeps hitting, without making the editor experience worse.
Next.js is the framework behind some of the largest production sites on the web (Next.js showcase). For a marketing site, the things that matter to a non-technical owner are simpler.
Hosting starts free on Vercel for most service-business sites. You pay only when traffic genuinely scales. Languages are built in with proper hreflang for search engines, and adding new ones costs nothing extra. Performance is dramatically higher (near-perfect Core Web Vitals are normal), which both Google and AI search engines reward. And the code is yours, in your GitHub, deployable anywhere.
Sanity is the CMS we pair with it. Sanity is free for most small to mid-size businesses on its free tier (Sanity pricing). We build a custom editor for each client so they see only the fields they need. It looks and behaves like the Webflow Editor, but it scales without billing surprises.
But can my team actually edit a Next.js site?
Yes, and most clients find Sanity easier than the Webflow Editor.
This is the question every business owner asks, and rightly so. A site you cannot update without a developer is not a real marketing tool.
With Sanity, your team gets a clean dashboard in the browser. Writing blog posts, swapping hero images, editing service pages, publishing case studies, updating team bios. All of it happens without code. Real-time collaboration is built in. Live preview shows the change on the actual site before publishing.
The difference from the Webflow Editor is that we configure the Sanity Studio specifically for each client. We hide everything you do not need. Service pages have only the fields that matter to service pages. Blog posts only show blog fields. The editor is shaped around your business, not the platform’s defaults. That alone is enough for most teams to prefer it within a week of switching.
What does a migration from Webflow to Next.js actually look like?
The timeline depends entirely on the scope of the project. Pages, languages, animation complexity. Each one moves the number.
A simple landing page is usually one to two days now. A few years ago this kind of work took much longer. With AI coding agents in the workflow, it has become dramatically faster, especially in the right hands. The bottleneck used to be writing the code. Today the bottleneck is design taste and judgment.
It is important to be clear that this is not a one-to-one copy where someone runs a tool that turns Webflow code into Next.js code. It is a complete rebuild. The design gets translated, the content gets cleaned up, and the new site gets built properly from the ground up.
It sounds like more work than it is, and it is a worthwhile one. The result is that businesses and individuals break free from monthly fees, platform constraints, and the unpredictable changes that come with renting your website from someone else.
So, is it time to leave Webflow?
If your site is small, single-language, and not central to revenue, stay. Otherwise, it is worth a serious look.
Webflow is genuinely good at the start of a project. If your business is small, you have one language, and the site is mostly a brochure, the recurring bill is manageable and the platform stays out of your way.
The moment the site becomes a real part of the business (adding languages, growing the content library, serving European enterprise clients, sitting at the centre of a marketing engine) the picture changes. The bill stops feeling fair. The ceilings start to bite. The ownership question stops being abstract.
That is the moment we start the conversation about moving to Next.js with Sanity. Not because the new stack is fashionable. Because clients who switch tell us the same thing six months later: the site is faster, the bill is predictable, and the platform finally feels like it belongs to them.
