FREEFirst project with us? Your landing page design is on the house.See the offer
Booking for Q4'26

Next.js to Webflow, marketing ships alone.

Your developers built the marketing site in Next.js because it was there. Now a headline change needs a pull request, and landing pages wait behind the product. We move those pages to Webflow, leave the real app in code, and map every route.

  • Routes sorted into marketing, product and needs a closer look
  • Metadata, sitemap and redirects read from the code, then matched
  • Product features stay in Next.js, on a subdomain or a path
★★★★★5.0Trusted by ClanX, Petavue, Tata and more

Plan my Next.js move

Tell us a little. We reply within one working day with a price and timeline.

🔒 No spam. No sales calls unless you ask for one.

Got it. Thanks!

We will reply within one working day.

A Next.js to Webflow migration moves your marketing routes to Webflow, so the marketing team can publish without a deploy, while the product stays in Next.js. Redirects, metadata and sitemap logic are read from the code and rebuilt, and changed paths get a 301. It is a trade: you give up some code freedom for faster marketing work.

Why teams split it

A headline should not
need a pull request.

Next.js is excellent for products. For marketing pages it can be a lot: a change waits for a developer, a review and a deploy. Your engineers would rather work on the product, and your marketers would rather not wait.

Moving does not have to touch the app. The usual result is a split, with Webflow for the public site and Next.js for everything behind the login. If your team likes shipping pages in code and nobody is waiting, stay as you are.

Route by route

Moves, stays or
needs a closer look.

The code holds details a crawl will not show, so we start in the repo.

Pages and layouts

React components are rebuilt as Webflow components. There is no import of JSX into the Designer.

MDX and headless content

MDX files or a headless CMS feed get converted and imported into Webflow collections.

Metadata and sitemap

generateMetadata, metadata exports and sitemap code run at build time. We read what they output, then match it.

Forms and API routes

Form handlers in API routes get replaced by Webflow forms or kept as a small app, depending on the logic.

next/image and assets

Webflow makes its own responsive images when assets are uploaded. We upload originals, not optimised copies.

Middleware

Geo routing, A/B tests or auth in middleware or proxy have no match in Webflow, so each is planned separately.

Keeping the app

Your app can stay
on the same domain.

A simple split is app.kookies.io for the product and Webflow on the main domain. Nothing about your Next.js deployment needs to change, other than where marketing links point.

If you want it on a path, such as /tools, Webflow Cloud can deploy a Next.js app from GitHub at a mount path on the same site. It runs on its own runtime and has limits, and some apps would need changes. We check whether yours fits before suggesting it.

Launch checklist

Checked against
what the code did.

A crawl sees the output. The repo explains why, so we test both.

  • next.config redirects and rewrites are each rebuilt or retired on purpose.
  • Dynamic routes map to Webflow collection paths, or get a 301.
  • Generated metadata matches on each page and template.
  • Sitemap and robots output cover the same pages, minus the app.
  • Trailing slash behaviour is checked, so no redirect chains appear.
  • Links between site and app work in both directions, including login.
  • Analytics and tag loading still fire on every page type.
  • Cookies shared with the app still work if they are set on the root domain.

What moves

Your site,
moved layer by layer.

Moving from Next.js to Webflow is more than copying pages. These are the seven layers we move, in the order we move them.

  1. 01
    Audit

    Every URL, page, form and script on your Next.js site, listed in one sheet before anything moves.

  2. 02
    Content

    Pages, posts and collections moved into Webflow, field by field, so nothing is retyped by hand.

  3. 03
    Design and build

    Pages rebuilt in Webflow as reusable components, matching the look you have or a new design.

  4. 04
    Redirects

    Every old URL gets a 301 to its new address, so old links and search results still land on the right page.

  5. 05
    SEO carried over

    Titles, descriptions, schema and image alt text move with each page.

  6. 06
    Forms and tracking

    Forms, analytics and connected tools set up again and tested before launch.

  7. 07
    Launch and watch

    DNS switched and the sitemap submitted, then we watch Search Console for errors.

Become 301

Next.js sends 308 for permanent redirects. We rebuild each rule in Webflow, where they run as 301s.

App routes moved

Logged-in screens and server logic stay in Next.js unless they are simple enough to replace.

Safe changes included

Text, image and link edits on the new site for a month, so marketing has backup while it gets going.

Review before launch

Marketing builds
a page first.

The test is simple. On staging, someone from marketing makes a real landing page from the components, without help, while we watch where it is hard. We fix those spots.

Your team reviews each screen size and comments on the page. Engineering signs off on the links into the app, and then we pick a day.

staging.fieldandclay.comStaging
Field & ClayShop
STONEWAREMade slowly. Used daily.
1Field & Clay teamCan the photo be bigger?Resolved
DesktopSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
2Field & Clay teamMenu feels crampedResolved
TabletSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
3Field & Clay teamButton text too smallResolved
MobileSigned off
Waiting for sign-off on 3 screensAll screens signed off. Checklist green.Switch domain

Next.js vs Webflow

For marketing pages,
not for your product.

This only compares the public site. Your app needs Next.js or something like it.

FeatureWebflowNext.js
Who ships a pageMarketing, from componentsDevelopers, through a deploy
Server logic and logged-in screensWebflow Cloud or a separate appBuilt for it
Code ownershipLimited exportYour repo, your rules
Shared components with the productRebuilt separatelyOne component library
Hosting and SSLIncludedYours to run or pay for
Motion without codeInteractions in the DesignerWritten by developers
Best forMarketing sites run by marketersProducts, and teams who like code

What you get

What comes with
every Next.js move.

No add-on surprises. These come with every project.

01

Repo audit

Each route sorted: moves, stays or needs a closer look.

02

Redirect rebuild

Config rules plus 301s for each changed route.

03

Webflow components

React sections rebuilt so marketing can reuse them.

04

Content import

MDX or headless content moved into collections.

05

Output parity

Titles, canonicals, schema and sitemap matched to the live site.

06

Forms and tags

Handlers replaced or kept, and analytics reconnected.

07

Domain routing

Main domain and app domain set up with you on a call.

08

Search Console reads

One each day for two weeks, then weekly.

Our process

How a Next.js to
Webflow move runs.

A common plan for marketing routes only. The app is not part of this timeline. Coloured bars are ours, striped bars are yours.

Next.js to Webflow · scope to launchYou

Our work

Webflow sites
we have shipped.

Try us first · Try us first · Try us first ·

Does marketing really need to move? Ask us first.

We read your repo and live site for free, and send a list of which routes would move and what would stay. If your team ships fine in code, we will say so.

Get my free route listFree, no strings

The guide

The Next.js to Webflow migration guide

How to move marketing pages to Webflow, keep the product where it is, and keep your URLs working.

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

  1. We agree the domain plan: app on a subdomain, or on a path with Webflow Cloud.
  2. On a call, the main domain points to Webflow, and DNS for the app stays as it is, or moves as planned.
  3. We test login links, cookies, redirects and tags straight away.
  4. 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.

Wall of love

Don't take
our word for it.

Hear it from the founders and teams we have built for.

Bailey McElligott, Design Director
Bailey on working with Kookies.
Bailey McElligott · Design Director0:17
Verified review
5.0
★★★★★
"They are very professional and the best at what they do."

Juned Khatri, Chief, BubbleWrap
Web development · Dec 2022 to Jan 2023 · Quality, schedule, cost and willing to refer: 5.0

Read it on Clutch
"Fast, efficient and beautifully designed! Kookies nailed our website with pixel-perfect execution and smooth interactions."
Juned KhatriFounder, ClanX
"They are very professional and the best at what they do. Kookies surpassed expectations with Webflow. Thrilled with the results!"
Juned KhatriChief, BubbleWrap
"Kookies' professionalism, dedication and exceptional design skills exceeded our expectations. Highly recommended for high-quality work and timely delivery."
AA
Ali Al MuttawaCo-founder, Artal Invest
"A thorough job, with high-quality work in a short timeframe. Abdul and his team were prompt, professional and patient with all our inputs. Happy to recommend them."
Sejal SinghiManaging Consultant, Baraka Impact Finance

FAQs

Next.js to Webflow
questions.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

No. The product stays in Next.js. We move only marketing routes, and agree the list with your engineers before starting.

Not into native Designer elements. We rebuild them as Webflow components with classes and variables, so marketers can use them without code.

Yes. The simple route is a subdomain. A path on the main domain is possible too, with Webflow Cloud for apps that fit its runtime and limits. We check yours first.

Webflow does not run your middleware. Geo routing, experiments and auth checks get planned separately, either with another tool or by keeping those pages in code.

It could, briefly. So we map every old URL, match titles, canonicals and schema to the live pages, and check Search Console daily for two weeks. Some movement is normal. No one can guarantee rankings.

A fixed quote after a 20 minute call. It depends on routes, content and how much logic sits in the pages. First-time clients get $500 off projects of $2,000 or more.

If marketers should build pages themselves, Webflow. If developers should stay in control and you want a lighter stack, Astro with a CMS. We build both.

For 30 days after launch we make safe changes for free: copy edits, image swaps, colour tweaks and link updates, and we fix anything we built that does not work. New sections, page redesigns and new features are not part of it. We quote those separately, or they are covered by a care plan.

Ready when you are

Let's get marketing
out of the sprint.

Send the form and get a price and timeline within one working day. Or book a quick call with our team.

WebflowPremium PartnerProud to build the Webflow way★★★★★5.0 on Clutch
Abdul Quadir
Talk to our teamA senior lead runs your call. Abdul, our founder, often joins.

Book a free 20 minute call

Pick a day that works for you.

See open timesOpen calendaror email hello@kookies.io
Book a callGet a quote