A WordPress to Next.js migration usually costs between about $4,500 and $38,000. That range runs from the small-site floor SEOParity publishes to the mid-size ceiling DevCritters publishes. Very small brochure sites can come in below it, and large WooCommerce, membership or 3,000+ URL sites can go past $50,000. Small and medium sites take roughly 6 to 16 weeks.
Page count matters less than you'd think. What sets the price is the number of distinct templates, how messy your content model is, how many URLs need redirects, which forms and integrations have to be rebuilt, and whether WordPress stays on as a headless CMS or goes completely.
I rebuilt procol.ai on Next.js, TypeScript and Tailwind CSS and I still maintain it. I've shipped 100+ websites, most of them on WordPress, so I know what goes into both kinds of build. I don't list my own rates here. If you want a number for your site, tell me about the project and I'll scope it.
How much does a WordPress to Next.js migration cost?
Published agency tiers run from about $1,500 for a very small site to $75,000+ for large or e-commerce builds. Most projects land between $4,500 and $38,000. Nearly every result on page one of Google is an agency selling its own tiers, so the most useful thing I can do is put them side by side.
| Source | Small site | Mid-size site | Large or e-commerce |
|---|---|---|---|
| DevCritters | $10,000–$18,000 (up to 20 pages) | $18,000–$38,000 (20–100 pages) | $38,000–$75,000+ |
| SEOParity | $4,500–$8,000 (under 100 URLs, 5–8 templates) | $8,000–$18,000 (content-heavy B2B) | $18,000–$35,000 (WooCommerce, membership), $35,000–$50,000+ for 3,000+ URLs |
| PandaCodeGen | From $1,500 | From $3,500 | From $5,000 when templates, data or integrations multiply |
| Tasken | From $5,000, fixed scope | Quoted after audit | Quoted after audit |
| Social Animal | Standard migrations from $15,000 | Quoted per project | Quoted per project |
Budgeting in pounds for a UK project? DevCritters gives £8,000–£15,000 for a small site, £15,000–£30,000 for a medium one and £30,000–£60,000+ for a large or complex build.
Two things jump out. A "from" price is only where the bidding starts. PandaCodeGen says plainly that its tiers are for planning and the signed statement of work sets the final price. And the gap between $1,500 and $15,000 for a "small site" isn't all markup. Mostly it's about whether SEO work, content migration and post-launch monitoring are in the quote at all.
Where the developer lives moves the number too. Second Talent puts a mid-level Next.js developer at $89–$140 an hour in the US and $21–$54 an hour in India. Same hours. Very different invoice.
One trap to avoid: moving the same WordPress site to a new host is a different job entirely, and plenty of hosts do it free, as PandaCodeGen notes about Kinsta. If better hosting is all you want, you don't need Next.js.
What drives the cost of a Next.js migration?
Five things: the number of templates, the state of your content model, the number of URLs that need redirects, the forms and integrations to rebuild, and whether you add a redesign. Here's how each one adds hours.
Templates, not pages
This is the most common misunderstanding about migration cost. If 500 blog posts share one layout, that's one template. If 40 pages each have a one-off Elementor layout, that might be 40 templates. SEOParity estimates 4 to 6 hours for a simple blog post template, and 20 to 40 hours for a complex landing page with animated sections, conditional blocks and marketing integrations.
Now do the maths. Dignizant puts freelance Next.js rates at $25–$60 an hour in South Asia or Eastern Europe and $70–$150 in North America or Western Europe. One 30-hour landing template then costs roughly $750–$1,800 at the first range and $2,100–$4,500 at the second. Ten of those and it adds up fast.
Page-builder sites are where template counts balloon. Over a few years, sections that look the same get built slightly differently each time. A good migration folds them into one Next.js component library, and every page you add afterwards gets cheaper.
Your content model
WordPress posts and pages move easily. Custom post types, ACF fields, page-builder shortcodes and image URLs hardcoded into post content don't. DevCritters warns that builder shortcodes don't export cleanly and that the mess only shows up once migration starts. I've built content models on CPT UI and ACF, for example on the IIID Inscape publication site. Well-structured fields map neatly onto a Next.js frontend. Badly structured ones need cleaning up first, and that time goes on your bill.
Redirects and SEO parity
Redirect work scales with your URL count, not your template count. SEOParity says full SEO parity work usually adds $1,500–$4,000 to a small or medium migration. That isn't padding. WordPress quietly creates lots of URLs nobody thinks about: category and tag archives, author pages, feeds, dated permalinks, attachment pages.
I built the free Redirect Map Builder for this job. Paste in your old WordPress URLs and you get a redirects() array for next.config.js. It flags chains, loops, duplicates, trailing-slash mismatches and query strings, and suggests pattern rules for archives, feeds and dated permalinks. Run your URL list through it before you ask for quotes and you'll know how big this part is. I've written up the full SEO process in how to move from WordPress to Next.js without losing SEO, so I won't repeat it here.
If you'd rather hand this part off, redirects, metadata, schema and Search Console checks are all part of my technical SEO and Core Web Vitals work.
Forms and integrations
Every WordPress plugin that does real work turns into its own line in the scope. SEOParity's examples show the spread: about $500 to swap a Gravity Forms form for a simple API-connected form, and about $15,000 for a full custom checkout rebuild. Write a list: contact forms, HubSpot, newsletter sign-ups, bookings, site search, memberships, WooCommerce.
On WordPress I've wired HubSpot forms and Stripe bookings for Ravens Ait and Google Sheets lead capture for Taxocity. In Next.js, each of those becomes an embed, an API route or a third-party service. Someone has to build it and test it.
Same design or a redesign?
Rebuilding your current design closely in Next.js is the cheapest route. Want a new look while you're at it? Design is a separate cost on top, whether you use an agency or my design partners.
The cheapest quote often leaves out redirects
If a proposal doesn't name the redirect map, metadata migration and Search Console checks as deliverables, assume they aren't included. Fixing lost rankings later costs more than doing it upfront.
Headless WordPress or a full rebuild: which costs less?
Headless WordPress is usually cheaper upfront, because content and editors stay in WordPress. It costs more each month, though, because you're running two hosting setups. A full rebuild on a new CMS costs more to migrate but is simpler to live with.
| Option | What stays | Upfront effort | Running costs | Best for |
|---|---|---|---|---|
| Headless WordPress (Next.js frontend, WordPress backend) | Your content, editors and admin screen | Lower content migration, but REST API or WPGraphQL setup, previews and two systems | WordPress hosting plus Next.js hosting | Teams that publish often and know wp-admin |
| Full rebuild on a new CMS (Sanity, Contentful, Payload) | Nothing from WordPress | Content migration scripts, cleanup and editor training | CMS plan plus Next.js hosting | Sites where WordPress itself is the problem |
| Full rebuild with content in code or Markdown | Nothing from WordPress | Lowest CMS work | Next.js hosting only | Small marketing sites that rarely change |
DevCritters frames it as a trade-off: headless WordPress spares the team retraining, while a full CMS move costs more to migrate but leaves a cleaner long-term setup. On running costs, Vercel Pro is $20 per user per month before usage overages, and with headless WordPress you still pay for WordPress hosting on top. I compare hosting and running costs side by side in how much a Next.js website costs vs WordPress.
If you'd rather keep WordPress as the editing screen, I build headless WordPress sites with a Next.js frontend too. The numbers are in more detail in how much a headless WordPress site costs.
How long does a WordPress to Next.js migration take?
DevCritters' published timelines are 6–10 weeks for a small site, 10–16 weeks for a medium one and four to six months or more for a large or complex build. They also note that small projects mostly get held up by slow client approvals, and on medium projects content migration and CMS setup eat more time than the code. That's what I'd tell any client anyway. Have your content, logins and decisions ready before kick-off.
Should you migrate, or fix WordPress first?
If speed is your only complaint, fix WordPress first. Migrate when the platform itself is getting in your team's way. Not every slow or awkward WordPress site needs a new stack. Brambla, a UK studio that builds on Next.js, says that on a budget under £8,000 a well-built WordPress site can be the more sensible spend. DevCritters points out that a Next.js site can even score worse than the WordPress site it replaced if nobody looks after images, JavaScript bundle size and rendering strategy.
If speed is the main reason, try Core Web Vitals fixes on your WordPress site first, or paste your PageSpeed report into my free Page Speed Fix Planner. Migration starts to make sense when your marketing team can't ship landing pages without a developer, when plugin conflicts keep breaking things, when you need app-like features, or when your in-house developers already work in React.
What should you ask a developer before you sign?
Get six things in writing: the template inventory, the redirect map plan, the content migration method, the plan for each integration, expected running costs and the SEO deliverables. With those answers you can actually compare quotes.
- 1
Template inventory
Ask for the list of templates and components they plan to build. A quote with no template count is a guess.
- 2
URL inventory and redirect map
Who builds the redirect map, and is it finished before development starts? Ask how archives, feeds and old permalinks are handled.
- 3
Content migration
Is it scripted or manual, and who cleans up shortcodes, ACF fields and hardcoded image URLs?
- 4
Integrations, one by one
For each form, CRM, booking or payment tool: rebuild it, replace it with a service, or drop it.
- 5
Running costs
Which hosting, which CMS plan and what monthly cost should you expect, including WordPress hosting if you go headless?
- 6
SEO deliverables and launch support
Metadata, schema, sitemaps, Search Console checks and how many weeks of monitoring after launch.
No brief yet? My free Project Scope Generator turns a two-line description into a list of pages, features and a build order. Handy to have before you talk to anyone.
Get a scoped quote for your migration
Send me your sitemap URL, the plugins you rely on and why you want to move. I'll tell you whether headless WordPress, a full Next.js rebuild or a WordPress tune-up fits better, and what's likely to drive the cost. You can see how I work on my Next.js and React websites page, or book a 20-minute call and we'll go through it together.
