Platform strategy

Why We Choose Next.js for Some WordPress Migrations

PandaCodeGen builds Next.js websites and migrates existing sites onto them. We choose Next.js when a client needs a deliberately engineered presentation layer and can own its operating model. We do not treat WordPress as automatically slow, insecure or wrong.

Reviewed against current primary documentation on July 24, 2026.

Hassan Jamal·Mar 4, 2026·9 min read

The honest reason

We moved for engineering control over how pages are rendered and delivered, not because WordPress is bad at what it does. That distinction matters, because the second framing would make this a recommendation and the first makes it a fit decision. Four things followed from it, and each one cost us something in exchange. A build here starts at $1,500 at a fixed price, has no minimum project size, and the code is yours at the end.

✓
Next.js gives our engineering team explicit rendering, caching, component and integration choices.
✓
WordPress gives a team a familiar editor and a broad managed ecosystem, which is a real advantage when nobody wants to learn a new publishing workflow.
✓
Neither platform guarantees performance, security, SEO, low cost or ownership by itself.
✓
We recommend migration only when measured requirements remain blocked after realistic WordPress repairs.

Delivery

Rendering and caching chosen per route and data need.

Editing

A governed CMS selected for the content workflow.

Security

A smaller intentional surface, still requiring updates.

Ownership

Repository, accounts, data and licenses defined in writing.

What changed our platform decision

Our choice came from recurring requirements: tighter control over rendered output, reusable design systems, route-specific data loading, integration work and a cleaner handoff for revenue-generating sites. That is our delivery preference, not proof that every WordPress property should migrate. We do not attribute any single client's ranking movement or hosting bill to the platform on its own, because a rebuild usually changes content, structure and hosting at the same time and no one of those can be isolated after the fact. The feature-by-feature comparison behind that preference is in WordPress compared with Next.js.

Speed depends on the build, not the platform name

Next.js supports server and client components plus multiple caching and revalidation patterns. Those tools can help an experienced team send less work and control data freshness. They can also be implemented poorly. WordPress speed comes down to the hosting, the caching, the theme, the plugins, content, media, database work and third parties. Measure representative routes with field data where available and repeated lab tests before naming the cause. Our method for the WordPress side is in diagnosing a slow WordPress site, and the metrics themselves are explained in Core Web Vitals explained.

Why there are no platform score ranges here

We do not publish a Lighthouse score range for either platform. A score belongs to a specific page, build, hosting setup and test condition rather than to the platform name, so a range quoted without that context tells you nothing about what your own site would score. Test your representative routes yourself and compare them against themselves over time. Every page named in your quote scores 90 or better on Google PageSpeed on phone and desktop, tested three times before we hand it over.

"We choose Next.js when a client needs a deliberately engineered presentation layer, and can own what that requires afterward.

Hosting and lifecycle cost

Build the comparison from current invoices and equivalent requirements. WordPress cost can include hosting, backups, security, premium extensions, maintenance and support. A Next.js system can include build, runtime, bandwidth, image processing, database, CMS, email, monitoring and engineering. Vercel's Hobby plan is intended for personal, non-commercial use under its current terms, so it is not a universal free-business-hosting promise. We set out a full input-by-input model in the three-year platform cost comparison, and our own tiers sit on the pricing page.

Plugins, packages and security

Moving off WordPress relocated our dependency risk rather than removing it. Our review of WordPress AI plugin security works through the runtime side of that, and it applies the same standard to the stack we run now: a custom build still carries packages, a build pipeline and service providers, and somebody still has to own patching.

WordPress advises keeping software current, limiting access, using trusted sources, backups and defense in depth. Plugin risk depends on the installed software, versions, configuration and maintenance. A Next.js application still uses framework and package dependencies, provider services, secrets and custom code. Our goal is a smaller, intentional dependency and privilege surface, not a vulnerability-free or maintenance-free system. The same inventory has a performance dimension, which we cover in how plugins affect front-end performance.

One argument gets made in our favour that we will not use, because on our own stack it is not true. You will read that a Next.js site has no exposed database and no admin URL to attack — no /wp-admin to brute-force. The first half is fair: there is no PHP plugin runtime and no database sitting behind the web tier where a plugin can reach it.

The second half is wrong for any site with a CMS, which is most of them. We run Sanity, so there is an admin: it is Sanity Studio, reached with real credentials, and it holds the content for the site. There are also API tokens, a Git repository, a deploy pipeline that can push code to production, and a hosting account. The attack surface moved. It did not disappear, and in some ways it got more interesting, because a leaked deploy token is a worse afternoon than a leaked editor password. If someone selling you a rebuild tells you the new site cannot be attacked, they are describing a diagram rather than a system, and the honest question to ask them is where the admin went, not whether it exists.

Will editors miss WordPress?

Some will, especially when their workflow depends on WordPress themes, blocks and plugins. Others prefer a structured CMS with constrained fields and preview. Sanity's current Visual Editing documentation supports live preview and direct editing from the rendered page. The correct choice depends on roles, approvals, localization, media, publishing volume, preview, portability and training.

Ownership is a contract question

A framework does not decide who owns deliverables. Our standard position is that client content remains client property; custom deliverables transfer after full payment under the signed agreement; PandaCodeGen retains reusable tools and pre-existing code; and third-party components keep their original licenses. Client-controlled domains, repositories, hosting and business accounts can be established when agreed. We walk through what to check in your own arrangement in do you own your website.

What we can say about MyCustomPatches

MyCustomPatches is an independent client, not a PandaCodeGen property, and its figures are owner-confirmed and published with permission. The client's owner reports a delivery of about 22 days. We do not hold a dated record of that confirmation, so treat it as an owner statement rather than an audited figure. That is a first-party timeline for one scope, not a market benchmark or promise. We do not attach performance, ranking, conversion, hosting or revenue figures to it. Numbers like those mean something only with the measurement period, method and comparable baseline stated beside them, and one site's results would not predict yours in any case. The scope of that project is written up on the MyCustomPatches project page.

When WordPress is still the right choice

Five conditions, and any one of them is usually enough to stay. The strongest is the third: an organization with reliable WordPress operations and someone who owns updates already has the thing most migrations are really bought to fix. Adding engineering responsibility without enough business value in return is not an upgrade.

✓
The team relies on mature WordPress editing, theme or extension workflows.
✓
Once repaired, the site you have is fast enough, secure enough, and connects to what it needs to.
✓
The organization has reliable WordPress operations and update ownership.
✓
A custom application would add engineering responsibility without enough business value.
✓
The budget or deadline supports a focused improvement but not a controlled migration.

When we consider Next.js

Consider, not recommend. These five conditions describe requirements that survived realistic repair, not preferences about tooling. The last one is the gate that decides most engagements: the client has to be able to own the target providers, the maintenance, the security and the release process afterwards.

✓
The design system and rendered output need deliberate engineering control.
✓
Integrations or application behavior exceed the current theme and extension model.
✓
A separate structured content workflow fits the editors and governance.
✓
The site is still slow or still breaking after you have genuinely tried to fix it.
✓
The client can own the target providers, maintenance, security and release process.

Requirements in the second line usually become custom engineering rather than another extension. For the broader replacement question, see what actually replaces WordPress.

What happens to SEO during migration?

A platform move can create search risk when URLs, rendered content, status codes, internal links, canonicals, metadata or crawl controls change. Google recommends careful planning, relevant redirects, updated links and canonicals, sitemaps and monitoring. Keep valuable URLs stable where practical and preserve a rollback path. No agency controls crawling, indexing, rankings, traffic or recovery timing. We answer the question people usually ask next in will migrating hurt my SEO.

Our migration process

Six steps, and the first two happen before anyone writes code. Inventory everything the current site contains, then define the target architecture, the content workflow, the ownership and the acceptance evidence. Building while the current site stays live is what makes the rollback in step five real rather than theoretical.

✓
List every URL, template, piece of content, data set, form, account and integration.
✓
Define target architecture, content workflow, ownership and acceptance evidence.
✓
Build and validate the replacement while the current site remains available.
✓
Test redirects, rendered output, analytics, consent, accessibility, security and performance.
✓
Launch with monitoring, rollback conditions and named owners.
✓
Complete handoff and contract-defined launch defect support.

That sequence is what our WordPress migration service is built around, and the step-by-step technical version is in how to migrate WordPress to Next.js.

PandaCodeGen offer and terms

We start with a free fit audit and prepare an SEO-safe migration plan when migration is justified. PandaCodeGen planning tiers start at $1,500 Starter, $3,500 Growth and $5,000 to $10,000 Scale. A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed. Refund is tied to failure to deliver the signed scope. Starter includes 15 business days of launch defect support; Growth and Scale include 30. The inputs behind a migration figure are broken down in WordPress migration cost.

Frequently asked questions

Frequently Asked Questions

Why does PandaCodeGen choose Next.js for some migrations?

It can provide deliberate rendering, routing, data and deployment control when those capabilities match the brief. The decision follows measurable requirements and operating ownership. It is not based on a claim that every Next.js site is fast or every WordPress site is slow.

When is WordPress the better choice?

WordPress can be the better fit when its editing workflow, ecosystem and maintained extensions serve the required capabilities and the team can operate updates, security and performance. Repairing a suitable implementation may be lower risk than migrating.

Can non-developers edit a Next.js website?

Yes when the build includes an appropriate CMS and tested preview, publishing and rollback workflows. The client can edit the scoped content fields, while structural changes and new integrations may require engineering.

Does switching from WordPress to Next.js hurt SEO rankings?

We kept our permalink structure through the move, which is the single biggest thing you can do to make this boring. Where addresses did change we mapped each one to its closest equivalent. What we watched afterwards was the shape of the curve in Search Console by page rather than the sitewide total, because a brief dip and a slow decline look identical for the first fortnight.

How long does it take to migrate from WordPress to Next.js?

Ours took weeks, not months, and the slow part was not the code. It was deciding what to keep. Rebuilding is an opportunity to drop pages that were never earning anything, and that is an editorial decision with opinions attached, so it takes longer than the engineering. Budget for the argument, not just the build.

Primary sources

Decide from your requirements, not platform slogans

We will compare WordPress repair and Next.js migration against the same routes, workflows, costs, risks and acceptance evidence.

Next.js16 min