Upfront: migrating from WordPress to Next.js is not a small project. Depending on the size of your site and how much custom functionality you're carrying, you're looking at £8,000–£40,000 / $10,000–$50,000 and anywhere from six weeks to six months. Whether that's money well spent depends entirely on why you're doing it—and a lot of teams don't get that question answered before they start.
This page covers what drives the cost, what a realistic timeline looks like, and where migrations from WordPress to Next.js go wrong. We do these for UK and US clients regularly, so the numbers here come from actual projects rather than guesswork.
First: is the migration from WordPress to Next.js actually necessary?
No, Migrating from WordPress to Next.js is not automatically necessary
The situations where a migration genuinely makes sense: your mobile PageSpeed scores are in the 30s and the theme vendor has given up on fixing it. Your marketing team wants landing pages and the current setup makes every new page a small crisis. You're running plugins that conflict with each other and your developer's solution is always "just add another plugin." You're expanding internationally and need proper multilingual routing that WP Multilite can't actually handle at scale.
If none of those sound familiar, a migration might not be the right project. A comparison of the two stacks is worth reading before you commit to anything.
What you're actually migrating
People say "migrate our WordPress site".
Content is usually the most tedious part. If your WordPress site has been running for five years and has 300 posts, someone has to move all of that to the new CMS—whether that's Sanity, Contentful, or WordPress itself staying in place as a headless backend. Automated migration scripts help but they never get everything right. Budget time for cleanup.
Design gets rebuilt from scratch in React components. This is actually one of the better parts of the process—you're not inheriting a theme's weird CSS decisions. But it takes time and it needs a designer and a developer working together, not one person doing both badly.
Functionality is where surprises happen. Contact forms are fine. WooCommerce is a full separate conversation. Custom post types with complex relationships, membership plugins, booking systems wired into third-party APIs—each of these needs to be assessed individually. Some are straightforward to rebuild. Some are not.
The CMS question is often the most important one nobody asks early enough. Are your editors staying in WordPress (headless) or moving to a new CMS entirely? Staying in WordPress is less disruption for the team but adds architectural complexity. Moving to a new CMS requires training and data migration on top of everything else.
Cost breakdown by project size
Small site £8,000–£15,000/$10,000–$18,000
20 or less than 20 pages site, not hectic work. You're rebuilding a brochure site and maybe a blog. The main cost here is design and build—getting the components right, hitting performance targets, making sure SEO doesn't fall off a cliff during the transition.
6-10 weeks if all things are ready. Actually this is true that delay in small migrations are from client not from agency due to late approval.
Medium site £15,000–£30,000/$18,000–$38,000
This is for the sites which have more content to manage, multiusers and integrations. B2B businesses, education platforms, service companies with several locations—this is where most migrations actually land.
Ten to sixteen weeks. Content migration and CMS configuration eat more time than most clients expect. The development itself is rarely what extends the timeline.
Large or complex site £30,000–£60,000+/$38,000–$75,000+
Four to six months minimum. Sometimes longer. If an agency quotes you eight weeks for a WooCommerce migration with 5,000 products and twelve payment methods, ask them to show you a similar project they've done before.
The risks people don't ask about
SEO during the transition. This one causes real damage when it's handled poorly. URL structures change, redirect maps get incomplete, internal links point to 404s, structured data breaks. We've seen businesses lose 40% of their organic traffic in the month after a migration because nobody owned the SEO handover.
Content that was never actually managed properly. WordPress's flexibility means a lot of teams have content living in weird places—custom fields with no documentation, page builders with proprietary shortcodes that don't export cleanly, images embedded in post content with hardcoded URLs. None of this surfaces in a demo. It all surfaces when you start migrating.
The CMS learning curve. If your editors have been in WordPress for three years and you move them to Contentful, expect friction. Not because Contentful is hard, but because any change to a workflow people do fifty times a week takes adjustment. Factor in training time and a period where both systems run in parallel.
Performance assumptions. Just because you're on Next.js doesn't mean the site will be fast. We've audited Next.js sites scoring worse than the WordPress they replaced because nobody thought about image optimisation, JavaScript bundle size, or rendering strategy. The framework gives you the tools. Someone still has to use them correctly.
What a well-run migration looks like
Discovery comes first—not a proposal, not a quote, a proper look at what you have. How many pages, what functionality, what the content model looks like, where the third-party integrations are, what the CMS workflow needs to support. An agency that quotes a WordPress migration without doing this is guessing.
Then a redirect map before build starts, not after. Then design and build in parallel where possible. Then a staging environment where the client can review before anything goes live.
Working on Performance asked before the Project starts. Not "we'll aim for good scores"—actual numbers. For reference, the Oxbridge Summer Courses site we built hit mobile Core Web Vitals passed with LCP 1.8s and CLS 0.01. That was the target going in, not a happy accident at the end.
Headless WordPress vs full migration
Worth mentioning separately because a lot of businesses assume migration means abandoning WordPress entirely. You get the performance and flexibility gains without retraining your whole content team.
FAQs: WordPress to Next.js migration
How much period does a WordPress to Next.js migration take?
Its Range is: Almost 6 weeks for a small brochure site with clear content, up to 6 months for a large platform with e-commerce or complex integrations.
What Happened to my SEO ranking after migrating?
They can, if the migration is handled carelessly. A proper redirect map, pre-launch SEO audit, and monitoring setup in place before go-live will prevent most of the damage. Rankings sometimes dip slightly during the transition period regardless—Google needs time to recrawl. A well-executed migration recovers within weeks. A badly managed one can take months.
I have to leave WordPress completely?
No. Editors stay in the admin, visitors get the speed.
Can I migrate WooCommerce to Next.js?
Yes, but it will be a bigger Project. Payment flows, product data, inventory, orders—all of it needs careful rebuilding. Get a proper scoping session before anyone quotes you a number for this.
What's the difference in cost between UK and US agencies?
London and New York agencies tend to sit at the top of the ranges above. Regional studios in both markets come in lower. What matters more than location is what's actually in scope—two quotes at the same price can represent very different amounts of work.
Related resources
- Next.js and headless WordPress services
- React vs WordPress: full comparison
- How much does a Next.js website cost?
- Why hire a Next.js developer
- Oxbridge Summer Courses case study
Bottom line
A WordPress to Next.js migration done properly will improve your performance, your SEO control, and how much your team can do without filing a dev ticket. Done carelessly, it'll cost you rankings, editorial workflow, and more money to fix than the migration cost in the first place.
The difference is almost always in how much was scoped and agreed before the project started—not what framework ended up in the repo.
We run these migrations for UK and US businesses. Services · Free 15-min audit.
