Migrate Wix to Next.js: Process and Cost
Migrate Wix to Next.js: why there is no clean export, how a 1:1 redirect map protects your rankings, and what the timeline and the cost look like.
Migrating a Wix website to Next.js means pulling content out through CMS collections, a crawl or by hand, mapping every old URL to a new target, and rebuilding the frontend. Wix ships no export another system can ingest. We walked this path in 2026 with our own website, moving from Wix to Next.js, Sanity and Vercel. What follows is the Wix-specific part: getting content out, the forced path prefixes, the redirect map, and when Webflow is the more honest destination for you. Timeline, cost and the order of steps come after that.
Key takeaways
- Wix ships no export that feeds a new frontend: content comes out through Wix CMS collections, a crawl, or manually.
- The Wix paths /post/ and /service-page/ disappear on the move, so every old address needs exactly one permanent redirect.
- Our own website ran on Wix until 2026 and has been live on Next.js, Sanity and Vercel since June 2026: 49 knowledge articles, 10 service pages, 17 city pages from one database.
- Wix costs 17 to 159 $ per month per website; after the move, Sanity Free plus Vercel usually lands you at 0-20 $ hosting per month.
- Up to roughly 30 pages, one or two languages, and no programmatic pages planned, Webflow is the more honest way out of Wix.
- For 10-30 pages, plan 3-6 weeks to go-live plus two weeks of monitoring; our relaunch packages start at 8,000 € net.
The short answer
Migrating from Wix to Next.js is not an export and import, it is a rebuild that carries the content over. Wix does not hand you your content as a package another system can read. You pull text and images from Wix CMS collections, from a crawl of your live website, or by hand, translate them into a content model, and rebuild the frontend, the visible website, in Next.js.
What decides your visibility here is not the frontend, it is the URL work. Wix forces path prefixes: blog posts sit under /post/, service pages under /service-page/. Those prefixes vanish the moment you control your own addresses. Every old URL therefore needs a permanent redirect to its content counterpart, otherwise visitors and crawlers hit dead ends and the signals you built up decay.
For a B2B company with up to roughly 30 pages, one or two languages and no programmatic pages planned, Webflow is a fair destination, and for English searches that is usually the real question behind leaving Wix. Once content has to run as a database, more languages arrive, or custom logic is needed, Next.js with Sanity is the answer. We took that route with our own website.
Why Wix has no clean export
Wix is built as a closed system. There is no button that hands you content, images and structure in a format another system picks up. What you can retrieve depends on how your content was created, and that single fact decides the workload of week one.
- Wix CMS collections: content inside a collection can be pulled as CSV or queried through the Wix API, the vendor's programming interface. This is the clean case.
- Pages built in the editor: anything typed straight into the builder exists only as a rendered page. A crawl with Screaming Frog or Ahrefs collects titles, copy and image addresses.
- Blog posts: they live under /post/ and can usually be captured via feed or crawl, including date and author. Category mapping normally has to be decided again.
- Media: images sit on the Wix delivery infrastructure. Download them and upload them again, otherwise your new website keeps pointing at someone else's servers.
Out of that raw material comes the content model: which content types exist, which fields each type carries, what is translatable, what references another type. We import the result into Sanity as NDJSON, a line-based record format. How a structured content database works is covered in Sanity CMS, and the basics of systems that manage content without their own frontend in headless CMS.
Wix versus Next.js with Sanity: the criteria
Run this comparison before the project, not halfway through it. These ten points are the ones our clients actually notice in daily operation.
Wix versus Next.js with Sanity: the criteria
| Criterion | Wix | Next.js with Sanity |
|---|---|---|
| Content model | pages in the editor, collections with preset field types | modelled freely, one content type serves several templates |
| URL structure | fixed prefixes such as /post/ and /service-page/ | your choice, per language and content type |
| Multilingual setup | tied to the platform | hreflang, the reciprocal language markup for search engines, in code, translated URL segments possible |
| JavaScript shipped | set by the vendor, no access | you decide per page what loads |
| Schema, sitemap, llms.txt | whatever the platform provides | FAQPage schema, sitemap logic and an llms.txt for AI crawlers, built by you |
| Programmatic pages | not supported | templates pull from the database, real substance per page stays mandatory |
| Editing and preview | builder editor | Presentation Mode shows the edit inside the real layout |
| Recurring platform fee | 17 to 159 $ per month per website | close to no platform fee, hosting usually 0-20 $ |
| Dependency on developers | low day to day, total on the technical side | editing without developers, setup and templates with them |
| Moving to another vendor | no usable export | content as documents, the code is yours |
On performance we stick to our own measurement from 13.09.2026 rather than promises: leanwave.com, which we build statically with Astro, loads around 39 KB of JavaScript in three files on its homepage, while one of our Webflow client sites loads around 740 KB in thirteen files at the same spot. That is not a Wix figure, but it shows what access to the delivery layer buys you. What that feeds into is covered in Core Web Vitals.
How we moved our own website off Wix
in-sync.io ran on Wix until 2026. That same year we moved to Next.js, Sanity and Vercel, and the new website has been live since June 2026. Candour belongs here: for the search terms that bring us business, the old Wix website was effectively invisible. The new one has been building positions step by step since launch, and we can see in our own data which chapters pull.
What we carried over
We kept everything that holds value independently of the platform. That is less than most people expect, and more important than most people think.
- Content: copy and images from the existing pages as raw material for the new content model, not as finished pages.
- URL list: every reachable address from the pre-launch crawl, the basis for the redirect map.
- Ranking snapshot: where positions stood before the switch, so that a comparison after launch is possible at all.
- Brand and contact paths: logo, visual language and the destinations of the forms stayed, everything else was decided again.
What we rebuilt
The real change is that content is now a system instead of a pile of individually maintained pages. That changes how fast we can ship anything.
- One database for everything: 49 knowledge articles, 10 service pages and 17 city pages come out of a single Sanity database, not out of 76 hand-maintained pages.
- Two languages: German and English marked up reciprocally with hreflang, so search engines serve the matching version.
- Server rendering: Next.js assembles the page on the server before it reaches the user, SSR for short. Crawlers get the finished content with no detour.
- A machine-readable layer: FAQPage schema, an llms.txt for AI crawlers, and IndexNow, which actively tells search engines about new and changed URLs.
Why that matters beyond plain Google rankings is laid out in generative engine optimization.
URLs and redirects: where your rankings are decided
Leaving Wix produces an unusually long redirect list, because the prefixes are baked into every old address by design. A website with thirty pages and a blog reaches three-digit numbers quickly. These four steps run the same way in every project we do.
Pre-launch crawl and ranking snapshot
: collect every reachable URL with Screaming Frog or Ahrefs and record current positions. Without that list you can prove nothing after launch.
A 1:1 redirect map
: every old address gets exactly one new target, permanently redirected. /post/article becomes /wissen/article, /service-page/service becomes /service. Bulk redirects to the homepage burn signals.
Launch checklist
: canonical tags, the pointer to the authoritative version of a page, plus hreflang, sitemap and robots.txt, all checked before the domain switches.
Follow-up
: submit the sitemap to Search Console and Bing, trigger IndexNow, then run two weeks of monitoring with a 404 report and a ranking comparison.
We have written out the generic six-phase process elsewhere, for Webflow and for WordPress. It applies to Wix in the same way. The difference sits in getting the content out and in the sheer number of redirects. What can go wrong in detail is covered in website relaunch without SEO loss and in technical SEO.
When Webflow, when Next.js
Not every exit from Wix has to end at Next.js. Webflow is an honest intermediate step: strong on design, fast in the editor, and enough for plenty of B2B websites. The line runs along the structure of your content, not along the visuals.
Choose Webflow if
You want out of Wix without opening a project with a development budget. Then Webflow is the obvious target, as long as these points hold.
- Your website has up to roughly 30 pages and you are not planning programmatic pages.
- You need one or two languages; the localisation add-on costs 9 $ per language per month up to three languages, 29 $ up to ten.
- Your team should change layouts without waiting for a developer.
- A hosting fee per website is acceptable to you: Premium sits at 25 $ per month with 20,000 CMS items and 40 collections.
Choose Next.js with Sanity if
Once content becomes the operating layer of your marketing, the maths flips. These four points are the usual triggers we see.
- You run more than two languages, or you want translated URL segments instead of language folders with English paths.
- One content type should serve several templates and pages should be generated programmatically, with real substance on each one.
- You need login, form logic, or data that comes from the server per request.
- Schema, sitemap, caching and internal linking should live in code rather than in a vendor's feature list.
For the head-to-head between the two destinations, read Webflow vs Next.js. If you want help with either, that runs through our Webflow work or our web development.
What a Wix migration costs and how long it takes
On the Wix side the fee is charged per website: Light 17 $, Core 29 $, Business 36 $ and Business Elite 159 $ per month. After the move it stops. Sanity Free covers 20 seats, 10,000 documents, 100 GB of assets and 100 GB of bandwidth per month, including Presentation Mode and Visual Editing. Vercel Pro is 20 $ per month per developer seat with 20 $ of usage credit and no base fee per project. Net result: 0-20 $ hosting per month and close to no recurring platform fees, with no per-language surcharge on our side.
The project cost sits on the other side of the ledger. We bill a migration as a relaunch project, and our relaunch packages start at 8,000 € net. A marketing website with 10-30 pages is typically live within 3-6 weeks, with monitoring on top. How budgets like that are put together is shown in web development costs.
Our verdict
For a serious B2B website, Wix is rented ground: you pay per website, you get no access to delivery, schema or sitemap logic, and on the way out there is nothing another system can ingest. That is the real price, and it only shows up on the day you leave.
One note on AI systems, because a lot of nonsense circulates here: Webflow, Wix, Contentful and Storyblok all run official MCP servers, standardised interfaces for AI agents, plus APIs. The difference lies in item and collection limits, the binding of one template to one collection, rate limits, and the missing access to rendering, caching, schema, sitemap and internal linking in code. And for programmatic pages the rule holds: without real substance per page, Google devalues them as doorway pages, pages that exist only to cover a keyword. We lived through that on our own old website.
Our recommendation stays two-tiered. Stay on a builder successor like Webflow if your website stays small and single-language. Move to Next.js with Sanity if content, languages and templates are meant to grow, and plan the switch as a relaunch with a redirect map, not as a design refresh.
Frequently asked questions
In four steps: pull content out through CMS collections, a crawl or manually; set up a content model in Sanity and import via NDJSON; build the frontend in Next.js; and map every old URL to its new target with a 1:1 permanent redirect. Then Search Console, Bing, IndexNow and two weeks of monitoring.
Not completely. Content held in Wix CMS collections comes out as CSV or through the Wix API. Pages typed into the editor exist only as rendered output and have to be collected with a crawl using Screaming Frog or Ahrefs. Images get downloaded and uploaded again into the new system.
Only without clean redirects. Because Wix forces paths like /post/ and /service-page/, almost every address changes. So every old URL gets exactly one new target, permanently redirected, backed by a pre-launch crawl, a ranking snapshot, and two weeks of monitoring with a 404 report after launch.
We bill it as a relaunch project, and our relaunch packages start at 8,000 € net. Recurring, the Wix fee of 17 to 159 $ per month disappears afterwards. With Sanity Free and Vercel you usually land at 0-20 $ hosting per month, and extra languages carry no surcharge with us.
A marketing website with 10-30 pages is typically live within 3-6 weeks, followed by two weeks of monitoring with a 404 report and a ranking comparison. The pace is usually set by getting content out, not by development, because Wix releases nothing in a usable form.
Up to roughly 30 pages, with one or two languages and no programmatic pages planned. You get design control and an editor without a development budget. Budget 25 $ per month for Premium and 9 $ per language per month for localisation up to three languages.
Next step
Send us your Wix domain and we will look at URL structure and content, then tell you how large the redirect map will be.
Wix vs. Webflow
The tier below, if Webflow is the destination.
Website relaunch without losing SEO
The checklist that carries rankings through a move.
Getting 301 redirects right
Status codes, redirect map and the mistakes that cost rankings.
CMS migration: process and cost
The overview of any system change, whatever you run today.
