Web Development
Company websites, online shops and web applications, built in Next.js. TechPlay’s database of more than 200,000 games runs on the same stack.
WordPress to Next.js migration that keeps your content, URLs and rankings, and ends the plugin updates.
We move WordPress sites to Next.js for companies tired of slow pages, plugin conflicts and security updates. Content, images and URLs come across, every address that earns traffic is redirected to its new equivalent, and rankings are monitored after the switch.
- How long does a WordPress to Next.js migration take?
- A typical business site takes 4–8 weeks, depending on the number of pages, content types and integrations.
- How much does a migration cost?
- A WordPress to Next.js migration starts from €1,500.
- Who owns the new site?
- You do.
What this service includes
There are two ways to do it. A full rebuild replaces WordPress with a new CMS. A headless setup keeps WordPress as the editor your team knows and puts a Next.js front end in front of it. We recommend one in writing after looking at your site.
A crawl of the current site: every URL with its traffic and links, the plugins in use, the content types and what each one does. You get a written plan before any work starts.
Posts, pages, custom fields, images and authors moved to the new CMS by script and then checked, not copied by hand.
Every old URL matched to its new equivalent with a 301 redirect, never to the homepage, and tested one by one before and after launch.
WordPress stays as the editor your team knows; Next.js renders the public site. The plugins that slowed the front end no longer affect it.
Next.js DevelopmentTitles, descriptions, canonical tags, structured data and internal links carried over; sitemaps resubmitted; Search Console watched daily after launch.
Core Web Vitals measured before and after on a mid-range phone, so the difference is a number rather than an impression.
Why sites leave WordPress
- The site needs a dozen plugins to do what it does, and each update risks breaking something. Nobody remembers what half of them are for.
- Mobile speed stays poor despite caching plugins, and Core Web Vitals remain red in Search Console.
- The site has been hacked or flagged before, or the theme is no longer maintained and cannot be updated safely.
A clear process, from scope to delivery
Audit and fixed quote
What you receiveA URL inventory, a migration plan and a fixed price.
Content model and prototype
What you receiveAn agreed content model and approved templates.
Build and content transfer
What you receiveA staging site with your real content, ready to review.
Switchover
What you receiveThe new site live, with every old URL answering correctly.
Thirty days of monitoring
What you receiveA before-and-after report on indexing, rankings and speed.
Chosen for the work, not for the trend
We choose tools based on the requirements of the project, your existing systems and what will be practical to maintain after delivery. Below are the technologies we typically use for this type of work, and why.
Next.js + React
The new front end: server-rendered pages that load fast and arrive complete for search engines.
WordPress
Kept as a headless CMS when your team prefers it, with its API feeding Next.js.
TypeScript
The migration scripts and the new site share types, so content arrives in the shape the templates expect.
Screaming Frog
The crawl behind the URL inventory, and the check that every redirect answers correctly.
Google Search Console
Indexing, coverage and rankings watched before and after the switch.
Cloudflare
DNS, redirects at the edge and caching during and after the move.
The work stays with you
Content intact
Every post, page and image moved and checked, with the old URLs answering through redirects.
Rankings protected
A redirect map, a before-and-after crawl and a month of Search Console monitoring.
Fewer moving parts
No plugin updates on the public site; security patches come down to a small set of dependencies.
Code you own
Repository, hosting and domain registered to your business from day one.
Related pages
- News Portal DevelopmentNews portals and media websites with a newsroom CMS, an app and ad positions
- Website RedesignA new design and a faster site, with content, addresses and rankings carried over
- Restaurant & Café WebsitesWebsites, QR menus and table ordering for restaurants and cafés
- Salon Websites with Online BookingWebsites for beauty salons that take bookings by themselves, day and night
- Event Venue & Wedding WebsitesWebsites for event venues and wedding studios that sell every offer and collect complete enquiries
- Accessibility Audit & FixesWCAG 2.2 AA audits and fixes in code, for the European Accessibility Act
Questions about this service?
If you cannot find the answer below, send us your question. A member of our team will reply within one business day.
Ask a question01How long does a WordPress to Next.js migration take?
A typical business site takes 4–8 weeks, depending on the number of pages, content types and integrations. Large content sites are moved in stages. The timeline is in the written plan before work starts.
02How much does a migration cost?
A WordPress to Next.js migration starts from €1,500. The final price depends on the number of URLs, content types and integrations; it is fixed in writing after the audit and does not change.
03Who owns the new site?
You do. The repository, hosting, domain and analytics are registered to your business from day one, and full ownership transfers on final payment.
04Will we lose Google rankings?
Rankings can move for a few weeks after any migration. They do not drop long term when every URL that earns traffic is redirected to its equivalent, content and metadata are kept, and indexing is monitored. That is what the redirect map and the month of monitoring are for.
05Can we keep WordPress for editing?
Yes. In a headless setup your team keeps writing in WordPress, and Next.js renders the public site from it. Whether that or a new CMS is the better choice depends on your content and team, and we recommend one in the audit.
06What happens to our plugins?
Each plugin is listed in the audit with what it does. Most front-end plugins — sliders, caching, SEO, forms — are replaced by code in the new site. Functions you still need, such as booking or a newsletter, are rebuilt or connected through their own service.
Often combined with
SEO
Technical fixes first, then pages written for the searches your customers make. You get a report every month.
Hosting & Care
Managed hosting and care for the sites we build, and for sites we take over from someone else.