By Mehdi HassanShould you migrate a WordPress site to Next.js?
You should migrate a WordPress site to Next.js when the site does more than present content: logged-in areas, pricing calculators, product data, many programmatic pages or a design system shared with your app. If it's mainly pages and a blog, Next.js is more power and more maintenance than you need.
Next.js is a React framework for building websites and web apps with server rendering, static generation and API routes in one codebase. We build marketing sites in it ourselves, and we still tell many teams not to use it. The right destination depends on your team and content, which our hub on where to move when you migrate from WordPress covers in full.
When is a WordPress to nextjs migration worth it?
A WordPress to nextjs migration is worth it in four situations: product logic on the site, large-scale or programmatic pages, custom integrations, and a shared design system with your app. Outside those, simpler options usually win on cost.
- Product logic. Signup flows, account areas, calculators, gated content or live product data that a builder can't handle cleanly.
- Scale. Thousands of pages generated from data, such as integrations directories, locations or templates.
- Custom integrations. Pulling pricing, docs or changelog data from your own APIs, or tight coupling with your product.
- Shared design system. The marketing site and the app use the same components, tokens and engineering team.
- Full ownership. You want the code in your own repository, hosted where you choose, with no platform lock-in.
If none of those apply, you're paying for flexibility you won't use. Framer or Webflow will let marketers ship pages without a developer; see WordPress to Framer or WordPress to Webflow.
Next.js vs Astro vs Framer for a former WordPress site
Next.js suits sites with logic and scale, Astro suits content-heavy sites that want static speed with less framework overhead, and Framer suits page-led marketing sites edited by non-developers. Choose by what the site does and who edits it.
Factor | Next.js | Astro | Framer |
|---|---|---|---|
Best for | Product logic, scale, shared design system | Content-heavy, mostly static sites | Page-led marketing sites |
Who edits | Developers, or marketers via a headless CMS | Developers, or marketers via a headless CMS | Designers and marketers directly |
Interactivity | Full React app capability | Static by default, interactive islands where needed | Built-in effects and components |
Hosting | Vercel, Cloudflare or self-hosted | Any static host or server | Framer hosting |
Ongoing upkeep | Dependency and framework updates | Lighter, still code | Handled by the platform |
Build cost | Highest of the three | Moderate | Usually lowest |
Astro deserves more attention than it gets from teams leaving WordPress. Our research found one public account of a 2,224-page site moved to Astro with coding agents, which shows how far static builds scale. See WordPress to Astro migration for that route.
Which CMS should you pair with Next.js?
Pair Next.js with a CMS that matches your editors: headless WordPress if they love WordPress, Sanity or Payload for structured content with a modern editor, or Markdown files in the repo if only developers publish. Decide this before anything else, because it shapes the content model and the import.
CMS option | Good fit when | Trade-off |
|---|---|---|
Headless WordPress | Editors want to keep WordPress | Two systems to maintain; front-end plugins need replacing |
Sanity | You want flexible structured content and live previews | Hosted service with its own pricing tiers |
Payload | You want a self-hosted, code-configured CMS in the same stack | You host the database and admin |
Files in the repo | Developers publish and content changes rarely | Marketers can't edit without help |
Our guide to headless WordPress with Next.js covers the first option's hidden costs. Whatever you choose, plan the content model with the marketing team, since they'll live in it every week.
How do you rebuild a WordPress site in Next.js?
Rebuild a WordPress site in Next.js by inventorying content and URLs, choosing the CMS, building a component library, creating templates, importing content and wiring redirects and metadata before launch. AI coding agents speed up the build step a lot; they don't replace the planning or QA.
Inventory URLs and content
Crawl the site, export posts, pages, media and taxonomies, and pull traffic and backlink data to decide what to keep.
Choose the CMS and model content
Define content types, fields and references, then build import scripts from the WordPress export or REST API.
Build components and templates
Create a small design system and the page templates. A design system for a Next.js marketing site keeps new pages consistent.
Recreate routes and slugs
Use dynamic routes so post URLs match WordPress where they can. Next.js lets you reproduce almost any permalink structure, including root-level and date paths.
Add redirects and metadata
Define redirects in config or middleware, and generate titles, descriptions, canonicals, sitemaps and structured data from CMS fields.
Replace plugins
Forms, search, analytics, consent and SEO output become services or code. Test each one.
QA, launch and monitor
Test templates on real devices, run the old URL list through a redirect checker, then watch Search Console daily.
Where AI coding agents help, and where they don't
Our research found public accounts of agent-led rebuilds off other platforms finishing fast: one team migrated off Webflow in a week, and one site was reported rebuilt in three days for $260 in usage. Agents are good at turning screenshots and specs into components, and at writing content import scripts.
The same research concluded that the real cost of a code migration is still SEO and QA, not tokens. Agents don't know which URLs earn backlinks, which content to retire, or whether the form actually reaches your CRM. Budget people-time for those parts, whatever tools write the code.
What does a Next.js site cost to run after WordPress?
A Next.js site costs hosting, any hosted CMS fees and developer time for updates and new pages. WordPress also needed hosting and maintenance, so the difference is mostly in who does the work and how often.
Hosting a marketing site on Vercel or Cloudflare can be inexpensive at startup traffic levels; check each provider's current plan page. The bigger line is people: framework and dependency updates, security patches and new templates. Our guides to keeping a Next.js marketing site healthy and hosting Next.js on Cloudflare Workers cover both.
- Designify website: up to 6 pages, custom design, Next.js, CMS
- $8,000
- Per extra page beyond six
- +$500
- Retainer for ongoing design and development
- $6,000/mo
- Quoted range for WordPress to headless Next.js in our research
- £13k–£30k
Can you go back if Next.js isn't right?
Yes. Teams sometimes move from code back to a visual builder when the marketing team needs to publish without engineers. It's another rebuild, so it's better to choose carefully the first time.
If you're already on Next.js and marketing is blocked, read Next.js to Framer migration, Next.js to Webflow migration or our broader guide to moving from code to a visual builder. If you're starting on Framer and outgrowing it, Framer to Next.js covers the opposite path.
