Plan your move from Next.js or a custom build to Webflow

Move a marketing site built in Next.js, Gatsby or a headless CMS to Webflow, so marketing can publish without engineering: what moves, what stays in code and how the routes carry over.

Content export
Content leaves the headless CMS through its API or export, and reaches Webflow by CSV or the Webflow API.
Rebuilt in Webflow
Page templates and visual components.
Biggest risk
Routes and rendering logic in code that nobody listed.
Can stay in code
The product, app routes and complex tools stay with engineering.

Is the move worth it?

Why teams move from Next.js or a custom build to Webflow

  • Marketing publishes without a deploy

    New pages and posts go live from Webflow, with no pull request or build.

  • Engineering gets its time back

    Developers stop maintaining marketing pages and focus on the product.

  • One place for content and design

    No syncing between a headless CMS, a component library and a build pipeline for marketing pages.

  • Hosting included

    Webflow hosts the site with a CDN and SSL, so there is no marketing infrastructure to run.

When staying on Next.js or a custom build is the better call

If the marketing pages share components and data with the product, or depend on server-side logic, personalisation or experiments built in code, a custom stack may be the right home. Moving only the content-heavy parts, such as the blog and landing pages, is a common middle ground.

What moves

Where each part of the Next.js or a custom build site goes

Everything is listed before anything moves. This is how each kind of content usually maps; your inventory decides the final plan.

On Next.js or a custom buildIn WebflowHow it gets there
Marketing routesStatic Webflow pagesRebuilt from the design system.
Headless CMS entries (Contentful, Sanity, Strapi)Webflow collectionsExported through the CMS API, transformed, then imported by CSV or the Webflow Data API.
MDX or Markdown postsA Blog posts collectionConverted to HTML and imported.
React componentsWebflow components, or code components through DevLinkVisual components rebuilt. Interactive ones can stay in code.
API routes and serverless functionsStay in code, or move to an integrationCalled from Webflow forms or custom code.
Permanent redirects in configWebflow 301 redirectsReviewed and recreated as suitable rules, keeping their intended destinations and removing chains.
Rewrites and proxy routesYour chosen hosting setupReviewed separately, then kept, rebuilt or replaced. A rewrite serves content at the requested URL, so it is not the same as a redirect.
Analytics and tag managerSite-wide custom codeAdded once in Webflow.
Preview deploymentsWebflow stagingContent changes are reviewed on staging before publishing.

Rebuilt rather than moved

  • TemplatesLayouts move from code into Webflow components and template pages.
  • Pages generated by codePages built from code logic become CMS template pages, or are simplified.
  • Build-time dataAnything fetched at build time needs a new source, such as a CMS field or an integration.

Step by step

How to move a Next.js or a custom build site to Webflow

Before the move

  1. List every route and content type

    From the router, the sitemap and the CMS, with traffic for each.

  2. Note what the code does

    Forms, gated content, calculators, experiments and anything personalised.

  3. Decide what stays in code

    And how visitors move between the two, by path or subdomain.

  4. Write the redirect map

    Including redirects that already exist in the config.

The move

  1. Rebuild the design system

    Variables, classes and components, matching the current components.

  2. Import the content

    By CSV or the Webflow API, with a sample checked first.

  3. Reconnect forms and APIs

    Webflow forms, webhooks or code components calling existing endpoints.

  4. Review on staging

    Marketing tests publishing; engineering checks the integrations.

After the move

  1. Switch the routes

    Point DNS or the proxy at Webflow and publish the redirects.

  2. Submit the sitemap

    Then watch Search Console for 404s and indexing changes.

  3. Hand editing to marketing

    With a walkthrough of the CMS and components.

  4. Agree what engineering still owns

    In writing, so nothing falls between the teams.

Search traffic

Keeping your rankings through the move

Google treats a migration as a site move. These are its rules, then the risks that are specific to Next.js or a custom build.

What Google asks for

  • A permanent (301) redirect from every changed URL straight to its closest replacement, with no chains.
  • No redirecting old pages to the home page in bulk. Pages with no replacement return a 404 or 410.
  • Redirects kept for at least a year, and a new sitemap submitted in Search Console.
  • Some ranking movement is normal while Google recrawls. On a medium-sized site it can take a few weeks or more to settle.

The migration SEO checklist lists every check before, during and after the move.

If traffic drops anyway, these are the checks to run.

  • Nested routes

    Routes such as /blog/[slug] map cleanly to a Webflow collection. CMS pages sit one level under their collection, so deeper nested routes need redirects.

  • Existing redirects

    Carry over redirects already in the framework or host config, and point each one straight at its final destination.

  • Rendering

    Pages rendered in the browser may have been indexed with less content. Webflow serves full HTML. Check key pages with URL Inspection after launch.

  • Generated metadata

    Recreate what the code produced: canonicals, hreflang and structured data.

Your part

What your team does during the move

  • An engineer for the integrations

    Someone who knows the APIs, forms and anything that stays in code.

  • A marketer who will publish

    To test the CMS and editing before launch.

  • A short content freeze

    Publishing pauses on the old site between the final content import and launch, usually a few days. Anything urgent in that window is added to Webflow by hand.

What you provide

  • Repository and CMS access, or exports
  • A list of integrations, APIs and scripts
  • Access to the domain, DNS and current host
  • Search Console access

Questions about the move

Can a Next.js site move to Webflow?

Yes, for the marketing pages. Pages and content move to Webflow, while product routes and complex logic can stay in code on their own path or subdomain.

What happens to our React components?

Visual ones are rebuilt as Webflow components. Interactive ones can be imported as code components through DevLink, or kept in the app.

How does the content get into Webflow?

Exported from the headless CMS through its API, mapped to Webflow collections and imported by CSV or the Webflow Data API.

Will we lose SEO?

Not if every changed route redirects to its closest replacement and metadata such as canonicals and structured data is rebuilt. Some movement while Google recrawls is normal.

Do developers still have a role?

Yes, for integrations, anything that stays in code and the occasional custom component. They stop being needed for routine page changes.

How long does the move take?

It depends on the number of pages and posts, how many features need replacing and how much content needs cleaning. The first step is an inventory of pages, posts, forms and integrations, and the estimate follows from it. Nothing is estimated before that list exists.