Webflow to Sanity and Next.js

We move your Webflow content into Sanity and rebuild the site in Next.js, so your content, your code and your hosting are yours to control.

Why people move off Webflow

Webflow is a capable platform, and plenty of good sites are built on it. It is also a platform you rent, and in 2026 the terms of that rent changed. Webflow merged its plans in May, raised the price of monthly billing, and cut the bandwidth included with its old Business plan from 100GB to 50GB. Sites in agency and freelancer workspaces move to the new prices from 16 November.

A price rise on its own is rarely a reason to rebuild. What it does is show how little say you have: your content, your design and your hosting all sit on one company's servers, on terms that company can change. Moving to Sanity and Next.js puts each of those back in your hands.

Person working on a laptop

What you get control of

Your content. In Webflow, your content lives in its CMS and comes out one collection at a time as a spreadsheet, or through its API. In Sanity it's stored as structured content you can query, reuse elsewhere and take with you, and the editor is set up around your pages, with a live preview as you work.

Your code. The site is rebuilt in Next.js, in a repository your company owns. Any developer can work on it, and nothing depends on one platform's designer or its rules about what you can add.

Your infrastructure. The site is hosted on Vercel's global network, in an account in your name. If you ever want to host it somewhere else, you can, because the code is yours.

Your costs. You still pay for hosting and, on larger sites, for Sanity, so this isn't about running a site for nothing. What changes is that each cost is separate and visible, and no single company can raise the price of your whole website at once.

Open padlock resting on loose keyboard keys

How a Webflow migration works

The steps are the same as on every migration, but Webflow sites have a few things of their own to deal with.

  1. CMS content

    Webflow's code export leaves out the CMS, so we pull every collection through Webflow's API instead. That keeps the links between items, such as a case study's client or a post's author, which a spreadsheet export flattens.

  2. Design and interactions

  3. Forms and search

  4. Images and files

  5. Languages

Find out what moving off Webflow would involve.

Send us a link to your current site and we'll go through your collections, interactions and integrations, and what moving them would take. You'll get a fixed quote and a timeline, and there's no obligation to go ahead.

It depends on your plan, your traffic and how many editors you have. We'll compare your current Webflow bill with Sanity and hosting costs when we quote, so you can see the difference before deciding.

It works differently. The Studio is set up around your content, with a live preview of the page as you edit, and every migration comes with custom video guides.

Yes. We rebuild it from your existing site, though we'd usually recommend at least a light refresh while the site is being rebuilt anyway.

No. Every collection and item moves across through Webflow's API, along with its images and the links between items.

If you're billed monthly, Webflow lets you switch to yearly billing before the new prices apply, which keeps your current rate for another year and gives you time to plan the move.

You do: the code, the content and the Sanity project are all in your company's name.