What comes out of WordPress
The WordPress Export screen produces an XML file of posts, pages and other content.
Moving from WordPress to Next.js
The WordPress Export screen produces an XML file of posts, pages and other content. On Next.js, old addresses are mapped to the new pages with permanent redirects.
How we run the move
List every page, product, form and integration on the old site, including the ones nobody has opened in a while.
Map each old address to its new page before anything is switched over.
Build and check the new Next.js site on a private link, then switch over with redirects in place.
Check Search Console and the busiest pages in the weeks after the switch.
Running the site on Next.js
Deploys to a Node.js server, a Docker container, static hosting or a supported platform adapter.
Features come from libraries and services chosen for the project, such as authentication libraries.
Migration plan
Moving from WordPress to Next.js
What moves across, and how
| Item | Approach |
|---|---|
| Pages and blog posts | The WordPress Export screen produces an XML file of posts, pages and other content. Content moves into the content source chosen for the build, then pages are generated from it. |
| Images and files | Downloaded from the old site, uploaded again and relinked in the content. |
| Page addresses | Old addresses are mapped to the new pages with permanent redirects. |
| Page titles and descriptions | Carried across page by page so search results keep showing accurate titles and summaries. |
| Forms and integrations | Rebuilt on the new platform and tested end to end, including where each submission is delivered. |
Risks we plan for
| Risk | How we handle it |
|---|---|
| Search rankings move after the switch. | Map every old address to its new page with permanent redirects, as Google's site move guidance describes. |
| Editors move away from a visual page builder. | Choose the content editing tool with the team before the build starts. |
FAQ
Frequently asked questions
Will we lose our Google rankings moving from WordPress to Next.js?
Some movement is normal after any site move. Google's site move guidance centres on mapping every old address to its new page with permanent redirects, which is the main safeguard.[1]
What can we take out of WordPress?
The WordPress Export screen produces an XML file of posts, pages and other content.[2]
Do you handle WordPress to Next.js moves?
Yes. Next.js is one of the platforms we build on, and we recommend it when it suits the jobs your site has to do. If another platform fits better, we say so. We plan the move from WordPress and say plainly if anything cannot be carried across.
How we work together
Two ways to get started
Website Subscription
Your website, fully managed — no big upfront cost.
We design, build, host, maintain and keep improving your site for one simple monthly fee.
- Custom-designed & built for your brand
- Hosting, security & maintenance included
- Ongoing edits & content updates
- Continuous SEO & performance improvements
- Scale up or down as you grow
Fixed Project
A one-off custom build you own outright.
A defined scope and a single fixed quote — delivered once, and yours to keep.
- Bespoke design & development
- Defined scope & timeline
- You own the website & code
- Optional care plan after launch
- Custom-quoted to your needs
Sources
- [1] Site Moves and Migrations (Google Search Central). Checked 9 October 2026.
- [2] Tools Export screen (WordPress documentation). Checked 9 October 2026.
- [3] Next.js Docs. Checked 9 October 2026.
- [4] Deploying Next.js (Next.js docs). Checked 10 October 2026.
- [5] How to implement authentication in Next.js (Next.js docs). Checked 10 October 2026.
Ready to get started?
Get a free, no-obligation quote for your project. We respond within 24 hours.