WordPress to Next.js Migration Service
We move B2B and SaaS marketing sites from WordPress to Next.js and protect what the old site earned: URLs, rankings, forms and leads.
By Tal Gerafi, Founder & Website Engineer · · Updated
We migrate B2B and SaaS marketing sites from WordPress to Next.js and protect the URLs, rankings and leads the old site earned. Every project runs in the same order: list every live URL, map each one to its new route with a 301, carry over titles, canonicals and schema, switch DNS with a lowered TTL, check everything on launch day, then watch Search Console and your forms for 14 days. AI speeds up the build and the content move. We handle the parts that decide whether your rankings survive.
Who this is for
- B2B and SaaS teams on WordPress whose site brings in leads they can't afford to lose.
- Marketing teams who wait on a developer, a plugin update or a theme fix for every page change.
- Companies whose product team already works in React and wants the website on the same stack.
- Teams on HubSpot or another CRM who need every form and tracking field to keep working.
Not a fit: a small site that ranks well and isn't blocking anyone. Stay on WordPress. A migration is a real project with real risk, so do it for a reason. Our guide to migrating WordPress to Next.js without losing SEO has a move-now-or-wait table if you're unsure.
One thing we won't promise: that Next.js alone makes your site faster. Speed comes from how a site is built (images, fonts, scripts, third-party tags), on any platform. We measure Core Web Vitals on your key pages before we start and measure the new build on the same pages before launch, so you see the difference in numbers.
How the migration works
1. Inventory every live URL
We pull every URL that Google or a visitor can reach: the XML sitemap, Search Console's indexed pages, a full crawl and your analytics. Each URL gets its traffic, rankings and (from Search Console's Links report) backlinks next to it, so we know which ones carry value. We also list every template, plugin, form, embed and tracking script, because each one needs a home on the new site.
2. Build and test the redirect map
One row per old URL, pointing to its new Next.js route with a permanent redirect (a 301, or the 308 Next.js sends by default; Google treats them the same). No redirect chains, and no dumping old posts on the homepage. WordPress leftovers (attachment pages, thin tag archives, old feeds) get redirected to something useful or a clean 410. We run the whole map against the preview site before launch. Here is the format in detail: the WordPress to Next.js redirect map.
3. Keep metadata, canonicals and schema at parity
Each page keeps its title, meta description, headings and a self-referencing canonical on the new host. The schema your SEO plugin used to add (Article, FAQ, Organization, breadcrumbs) is rebuilt in code. One trailing-slash rule, one host, a sitemap and robots.txt that match the new routes, and nothing set to noindex by accident. Publish dates stay as they were.
4. Rebuild the site and move the content
We rebuild your templates in Next.js, keeping your design or refining it, and move every post and page with its full text, images, alt text and internal links. AI does much of the conversion work. We compare old and new pages (word count, headings, links) so nothing gets thinner on the way. Shortcodes and plugin features become components or direct integrations.
5. Switch DNS with a plan
A few days before launch we lower the DNS TTL so the switch spreads in minutes, not hours. The new site has to pass on its own URL first. We switch during low traffic and keep the old WordPress server answering until old DNS caches expire. Where your host allows, it stays up after that as a rollback. More on how this works: what is a DNS cutover?
6. Launch-day checks
On launch day we:
- Run the full redirect map against the live domain and confirm every old URL returns a single permanent redirect (301 or 308) to a live page.
- Check that http and https, www and non-www all resolve to one host in one hop.
- Open the top-traffic pages and check titles, canonicals and schema in the live HTML.
- Send a test lead through every form and confirm it lands in HubSpot or your CRM.
- Confirm analytics and the consent banner fire as before.
- Submit the new sitemap in Search Console and request indexing for key pages.
7. Watch for 14 days
For 14 days after launch we check Search Console's Pages report for new 404s and redirect errors, impressions and positions on your top pages, and form submissions against your normal volume. Fixes go in order of risk to traffic and leads. Some ranking movement in the first weeks is normal while Google recrawls. A climbing 404 count is not, and that's what the watch catches.
What you get
| Deliverable | What it protects |
|---|---|
| URL inventory with traffic, links and rankings per URL | Pages nobody remembered |
| Redirect map, tested on the preview and on the live domain | Rankings and backlinks |
| Metadata, canonical and schema parity check | How Google and AI search read each page |
| Next.js site in your design, kept or refined | Brand and conversion paths |
| DNS switch and rollback plan | Uptime on launch day |
| 14 days of monitoring and fixes | Problems caught while they're small |
What changes for your content team
The biggest change is where you edit. We pick one of two setups with you before the build:
- Keep WordPress as the editor (headless). Your team writes in the same WordPress admin, and Next.js renders the public site. Least retraining, but you still run and update WordPress.
- Content in the codebase (Markdown or MDX). Pages live as files in Git, edited directly or with AI tools. Fewer moving parts, and a good fit for teams comfortable with that workflow.
A few other things change:
- Plugins become code. The SEO plugin's titles and schema, the redirect plugin and the form plugin move into the site's code or a direct integration. Fewer plugin updates to manage.
- Previews before publishing. With content in Git on a host like Vercel, every change gets its own preview link before it goes live.
- A handoff guide. Your team gets a short written guide to editing pages, adding posts and swapping images on the new site.
Coming from Webflow, Framer or an AI builder
The process above works for any source. What differs is how the content comes out.
- Webflow. Webflow's code export leaves out CMS content, so Collection pages export empty (Webflow Help Center, checked 2026-10-01). We export your Collections as CSV, move them into the new content setup and map every Collection URL in the redirect map. Running HubSpot forms on Webflow today? See our HubSpot forms on Webflow playbook.
- Framer. Framer doesn't offer HTML export for self-hosting (Framer Help, checked 2026-10-01). We rebuild the pages to match the live site and move your CMS content across.
- Lovable, v0 and Bolt. These tools give you real code: Lovable syncs to a GitHub repository you own, v0 connects projects to GitHub, and Bolt exports a ZIP (all checked 2026-10-01). So we start from your code, not from scratch. AI builds it fast. We make it great: we check rendering, metadata, redirects, forms, accessibility and Core Web Vitals, and fix what a production marketing site needs.
Proof: our own migration and what clients say
In June 2026 we moved our own site from greeto.me to greeto.studio and published the Search Console data, including what dipped: our domain migration log. That was a domain move, not a WordPress migration, so it's the easier kind. Old greeto.me URLs redirect path by path to the new domain, none to the homepage, and Google has indexed 76 of the 77 URLs in our sitemap (Search Console, checked 2026-10-01). The log also lists what lagged and what we'd do differently.
Here is what clients say, quoted from their public LinkedIn recommendations. They cover rebuilds, design and performance work, not a WordPress migration specifically. (Tal Gerafi is our founder.)
"From complete website redesigns to optimizing our Core Web Vitals, Tal tackled it all. He's not just a great web dev — he's an expert consultant on making your website the best it can be. If you want perfection, you want Tal."
Zev Schonberg, Head of Product Marketing, Coralogix
"I handled the design and Tal brought it to life beautifully and precisely. He's that rare kind of developer who genuinely cares about design."
Sivan Lahav, Senior Creative Designer, Coralogix
"We've worked with Greeto for over three years. He has perfected the performance of our website and consistently delivers way beyond our expectations."
Hagai Shaham, Director of Digital Marketing, TechSee
Comparing providers? We wrote an honest comparison of WordPress to Next.js migration services, with our own entry clearly marked.
FAQ
How much does a WordPress to Next.js migration cost?
We quote each site after we've seen it, and we don't publish prices. What drives the cost: the number of page templates (more than the number of pages), how much content moves and whether it needs cleaning up, plugins that must be rebuilt as code (search, multilingual, gated content), integrations like HubSpot, analytics and consent, whether the design stays as is or gets refined, and the size of the redirect map. Tell us about your site and you'll get a scoped quote.
How long does a WordPress to Next.js migration take?
It depends on templates and content volume more than page count. Every project has the same phases: URL inventory and redirect map, rebuild and content move, pre-launch checks, the DNS switch, and the 14-day watch. The watch is always 14 days. How long the other phases take depends on your site, so we estimate them after we've crawled it. AI shortens the build and content move. The checks don't get skipped to save time.
Will we lose SEO rankings when we move off WordPress?
Usually not, if continuity holds. Google ranks URLs and content, not the CMS behind them. Rankings drop when old URLs return 404s, when content gets thinner, or when canonicals and schema go missing. With a complete 301 redirect map and content parity, expect some movement in the first weeks while Google recrawls and processes the redirects. If 404s or redirect errors climb in Search Console, the map has a gap, and the 14-day watch is there to catch it.
Can we keep our current design?
Yes. We can rebuild your current design as it is, so visitors see the same site on a new foundation. Or we refine it during the move. Changing URLs, content and design at the same time adds risk, so if you want a full redesign we'll tell you whether doing both at once makes sense for your site.
Will our HubSpot forms keep working?
Yes. HubSpot forms aren't tied to WordPress. We place the same forms on the new pages, so submissions, workflows and lead routing in HubSpot don't change. Two things need checking on the new site: the HubSpot tracking code on every page (if you used the HubSpot WordPress plugin, it added this for you), and your domain listed in HubSpot's tracking settings, because HubSpot marks submissions from unlisted domains as spam (HubSpot Knowledge Base). We test every form before the switch and again on launch day.
Can we migrate in stages instead of one big launch?
Yes. For larger sites, moving one section at a time (often the blog first) can be safer. Next.js can proxy the paths it doesn't serve yet to the old WordPress server, so both run under one domain until the last section moves.
Ready for a safer migration?
Related reading:
