What is a Next.js to Webflow migration?
You take the public pages out of your Next.js codebase and rebuild them in Webflow, so the marketing team can edit and publish on its own. Anything that is really product stays where it is.
This is a trade rather than an upgrade. You give up some code freedom and a shared component library, and you get marketing moving without engineering.
When staying on Next.js is the better call
- Pages depend on logged-in users, live data or server logic
- A shared component library between product and site matters to you
- Engineers like the setup, and marketing is not waiting
Marketing may also just need a better CMS, or a faster framework if you want to stay in code. Read Webflow vs Next.js and Astro vs Next.js. We also do Next.js development.
Split marketing from product
Go through the routes with an engineer and sort them. Home, features, pricing, about, blog and legal usually move. Dashboards, login and account pages stay. Calculators, gated downloads and personalised pages need a closer look, as they are sometimes simple and sometimes small apps.
That list drives the whole project, and it is the main thing we want to get right early.
Reading what the code does
Next.js redirects live in next.config.js. Permanent ones return 308, and they can match on headers, cookies or hosts. Some of those conditions have no direct match in Webflow, which handles path-based 301s with capture groups. So each rule gets a yes, no or rethink.
Metadata and sitemaps are often generated, so we compare the live output, not just the code. Middleware or proxy logic gets listed separately.
Dynamic routes and collections
Webflow gives collection pages a single path pattern, such as /blog/post-slug. Deep routes like /blog/category/post do not map one to one. Where a route has to change, it gets a 301 and the old pattern can often be handled with one wildcard rule.
Content in MDX or a headless CMS becomes collection items. See Webflow CMS for what the fields can do.
Launch, with the app in mind
- We agree the domain plan: app on a subdomain, or on a path with Webflow Cloud.
- On a call, the main domain points to Webflow, and DNS for the app stays as it is, or moves as planned.
- We test login links, cookies, redirects and tags straight away.
- Search Console gets the new sitemap, then a check every day for two weeks.
We map every old route to protect your rankings. Expect some movement after launch, as that is normal, and we do not promise fixed positions.







