The key points
- Map every existing URL before building anything.
- Decide the editing workflow before you leave WordPress.
- Redirect every address that changes.
- Test on a separate address, then switch the domain.
Why would anyone migrate?
Usually because the site is slow or fragile from layers of themes and plugins, because they need custom behavior a plugin cannot supply, or because they want a codebase they control. Migration is not always the answer; a well-maintained WordPress site that meets the need can stay, as the Next.js vs WordPress comparison explains.
What are the main risks?
Search visibility and editing. Addresses that change without redirects lose the rankings attached to them, so map them all first, as in any redesign that keeps its SEO. And a team used to the WordPress editor needs an equally workable way to update content, or the new site goes stale. Plan both before the build, not after.
- URLs changing without redirects
- No clear way for staff to edit content
- Plugin features that need to be rebuilt
- Forms and integrations not tested end to end
How long does it take?
It depends on the size of the site and how much is rebuilt. In our Next.js development process, discovery takes about a week, design one to two, build two to six and launch about three days, with larger sites at the longer end. The migration plan is agreed in the proposal.
A WordPress to Next.js migration
Inventory
List every URL, template, plugin and integration, and note which pages bring traffic or enquiries.
Plan editing
Choose how your team will update content after the move, so editing does not become a developer ticket.
Rebuild and migrate
Rebuild templates in Next.js and move content, exported from WordPress or read through its REST API, cleaning duplicates and outdated pages as you go.
Redirect and test
Map redirects for changed addresses and test the new site on a separate address.
Switch and monitor
Point the domain at the new site, then check redirects, metadata and indexing against a website launch checklist.
Before you migrate
- Do you have a list of every live URL?
- Which pages currently bring traffic or enquiries?
- How will your team edit content afterwards?
- Which plugins provide features you need to keep?
- Who tests forms, integrations and redirects?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.