WordPress to Next.js migration

Your site runs on WordPress, with a theme, a page builder and a stack of plugins that all have to stay compatible and up to date. Every change waits on whoever knows how it all fits together, and the updates never stop. In July 2026 a flaw in WordPress itself let anyone run code on sites that hadn't been updated, and attackers were already using it.

Source Coalition, WP2Shell vulnerabilities exploited in the wild, 20 July 2026

• Your site rebuilt in Next.js, in code you own in your own GitHub repo, matched to your live pages.
• Every post, page, image and category carried across, editable like any other page.
• Every page that ranks keeping its address, or sent on to its new one, tested before your domain moves.
• What your plugins did, such as forms, the titles search engines show and site search, built into the site itself, with no plugins left to update.
• Claude Code set up to know your site and your rules, so editing a post or adding a page is a sentence to it.
• A preview link for every change, so nothing reaches the live site before someone looks at it.
• A recorded walkthrough for whoever on your team makes the changes.

1. You send me your WordPress site, and I list every page your rankings rest on and every plugin the site depends on.
2. I rebuild it in Next.js, with your posts, pages and images carried across and each plugin's job built in.
3. Claude Code is set up on it, and you make your first change by asking.
4. Your domain moves to the new site, and every old address is checked on the day.

WordPress exports your posts, pages, comments, categories and tags, with links to your images rather than the images themselves, so the old site stays up until every file has been copied across. On WordPress.com the export leaves out your theme design, your customizations and your plugins.

Source WordPress.com, Export your content to another blog or platform

Everything a plugin keeps for itself misses the export, and that's where a move breaks.

• Form entries, the titles and descriptions search engines show, and the redirects you set in a plugin.
• Pages built in Elementor, Divi or another page builder, whose layout sits inside each post in the builder's own markup, so it's rebuilt rather than copied.
• Shortcodes, the bracketed tags plugins leave in your posts.
• Shop, membership and booking data, which each need their own way across.

Some sites keep WordPress behind the scenes as the place posts are written, with Next.js serving the pages. That suits a team that writes in WordPress every day and wants to keep doing it. When the point is to stop updating WordPress at all, the content moves into the code and Claude Code edits it from there.