Service
WordPress to Next.js Migration
Leave the plugin pile behind without leaving your rankings behind with it.
Keep everything Google likes about your site. Lose everything you don't.
The reasons people give for leaving WordPress are rarely about WordPress itself. "Every update breaks something." "We pay for six plugin licenses and use two." "The site is slow, and the person who built it stopped answering." "The host updated PHP and the homepage went white." That last one has its own Playbook post, because it happens so often.
WordPress is a serious platform. W3Techs counts it on 39.5% of all websites, more than any other content management system. The trouble is usually what gets bolted on. In Patchstack's report on 2022, about 93% of the WordPress security bugs it tracked were in plugins, and well under 1% were in WordPress core.
A migration to Next.js removes the bolted-on layer completely. The fear that stops most owners is the right fear: losing the rankings the old site earned. This page is mostly about how we don't.
Why Next.js, and when to stay put
Next.js is an open-source framework for building websites with React. A site built on it can send finished pages to the browser, with no plugin stack assembling them on every request and no plugin layer to patch. In practice, in our experience, that means fast pages, fewer moving parts, and far fewer emergency calls. Speed is measurable: Google's Core Web Vitals set the targets, and we build to them.
We aren't neutral out of politeness. We also do custom WordPress development and WordPress repair, so we have no reason to talk you out of a platform that's working. If your team publishes every day and loves its editor, or your business runs on a plugin with no good replacement, staying may be right. For the full comparison, read AI vs. WordPress for trade sites and WordPress vs. a custom website.
The migration, step by step
1. Inventory everything. We crawl the old site for every URL, including blog posts, images, PDFs, and the odd page nobody remembers, and pull your Search Console data to see which pages actually earn search traffic.
2. Map every old URL to a new one. Where a URL can stay the same, it stays the same. Where it can't, it gets a permanent redirect. Google recommends server-side permanent redirects from the old URLs to the new ones, notes that 301s don't lose PageRank, and says to keep them in place for at least a year. We keep them indefinitely.
3. Carry the metadata forward. Title tags, meta descriptions, headings, image alt text, canonical tags, and structured data come across deliberately, not by accident.
4. Move the content by hand. Page-builder content is usually buried in shortcodes and nested layout boxes, so we move it by hand and clean it up as we go. Forms are rebuilt and tested until every one reaches the right inbox.
5. Launch, then watch. We submit the new sitemap, watch Search Console for errors and missed redirects, and fix what turns up. Google is candid that you should expect temporary fluctuation in rankings while it recrawls a moved site. We plan for it and won't promise you zero movement. Nobody honest can.
6. Compare against real numbers. Before launch we record the old site's speed scores and which pages earn search traffic. Afterward you can compare the new site against those records instead of against memory, which tends to flatter whichever site you liked better.
What changes for you, and what doesn't
Your domain and email stay put. The domain doesn't move anywhere. At launch we change only the DNS records the website needs and leave the mail records alone, so email keeps flowing the whole time.
Hosting changes. The site moves to hosting built for this kind of site. We set it up, and you'll know what it costs to run before launch, not after the first invoice.
Your team can still edit. Every package includes content management. Editors get clean fields for headlines, text, photos, and posts, and the design applies itself. What goes away is the ability to accidentally rearrange the homepage at 5 p.m. on a Friday.
The plugins become code, or disappear. The SEO plugin's job, titles, descriptions, sitemaps, and structured data, is built into the site itself. The form plugin becomes a form we wrote, with bot protection and delivery we can test. The caching plugin has nothing left to do, because the pages are already prebuilt. The page builder becomes a small set of components designed for your site. Fewer licenses to renew, fewer updates to fear.
What we need from you. Access to the old site, through a WordPress user account created for us rather than your own login, plus Search Console and analytics access, and a list of anything the site does that isn't obvious from the outside: a members area, a calculator, an integration with your CRM.
What it costs
A migration is a rebuild, so it's priced like one, by page count: up to 10 pages for $1,500, 11 to 20 for $2,250, 21 to 50 for $3,750, and 51 to 70 for $5,750. Larger sites are quoted. Every package includes SEO, design, content writing, content management so your team can still edit, lead forms, online booking, one custom third-party API integration, and a year of support. If the site is a store, online stores start from $2,500.
Most builds go live in 7 to 10 days, and work starts within 24 hours of the go-ahead. You can pay online on the pricing page, with a 25% deposit or in full, and 0% financing with 25% down is available for up to 12 months on any project.
Who it's not for
If your WordPress site is fast, secure, and liked by the people who use it, keep it. A slow site can often be fixed in place with a speed tune.
If you want to redesign pages yourself by dragging boxes around a visual builder, a structured Next.js site will feel strict, because it's built to keep the design consistent no matter who edits it.
And if a store or membership system with deep plugin dependencies is the heart of the business, that's a bigger conversation. We'd start it under eCommerce development.
Timing matters too. A migration two days before your busiest week is a gamble you don't need to take. For most trades, the quiet months are the right window, which is the argument of the slow season is when smart contractors fix the website.
Sites we've moved
Bleuwave HVAC, Bleuwave Plumbing, Bleuwave Electrical, Bleuwave Handyman, and Precision Leak Detection were all WordPress sites rebuilt on Next.js. Between them they carry deep service catalogs, estimate tools, and custom lead tracking. American Roofing went from WordPress to hand-coded PHP, a reminder that the destination should fit the business, not the trend.
For a broader rethink, see website redesign. For the search side in detail, read what happens to your SEO in a WordPress to Next.js migration.
How it works
Four steps. No mystery.
We listen first
You tell us about your shop, your best jobs, and your busy seasons. We learn your trade before we write a word or run a dollar.
We build the plan
A straight, honest plan with real timelines and real numbers. No jargon fog, no mystery line items.
We do the work
The person who built the plan does the work and answers your call. We ship, we measure, we show you what is moving the phone.
We tune and grow
Marketing is not set-and-forget. We cut what wastes money and pour more into what books jobs.
The part we didn’t write
Clients say it better than we do.
Real reviews, verbatim — the same people whose sites are in the portfolio. Hover to pause and read at your own speed.
What clients say — in their words
“Casey, the owner and developer, took the project and ran with it 100%. I gave him specific direction and he went well above the call of duty. Five star service all the way!”
“Wow! Casey rocked! The process was so easy, I told Casey what I wanted and he built it. My go-to with my online business, which has grown exponentially since working together.”
“First class all the way! From the prompt communication, being available seven days a week, to the nuts and bolts of getting our project completed on time and on budget — I highly recommend!”
“Simply amazing! They took our outdated website and transformed it into a modern, user-friendly platform that truly represents our brand.”
“They get it done. We had no idea where to start; they explained the build process and were patient with our many questions. All expectations and timelines were met. Double thumbs up!”
“Instrumental in driving our company growth through expert management of our Google and Microsoft Ads.”
“They helped us turn a loose idea into a working digital product — asked sharp questions, found the hidden workflow problems, and built a system our staff could use without a long training curve.”
“What stood out was the balance of design and operations. The site looked polished, but the real win was behind the scenes: better forms, cleaner handoffs, stronger tracking, fewer manual steps.”
“They made the technical side feel clear. We talked about goals first — then platforms, content, search, and automation.”
Pair it with the rest.
Website Maintenance & Support
Updates, backups, fixes, and a developer who answers the phone. The dull work that keeps a site earning.
Web Design & Development
Fast, hand-built sites that load in a blink and turn visitors into calls.
Custom Web Applications
When off-the-shelf runs out of shelf. Real software, built for how your business actually works.
Price it in a minute
WordPress to Next.js Migration: see where yours starts.
A few taps and the number appears on screen: fixed prices where the work is fixed, honest starting prices where it isn’t. The developer follows up personally — by phone, text or email, whichever you pick.
- Every price published on the pricing page
- 0% financing with 25% down on any project
- One developer from first call to launch
How many pages should the new site have?
We recommend 51 to 70 pages for the best initial organic SEO rankings: it gives the site proper page depth.
Also need? (pick any, quoted on top)
Rather talk? (480) 525-7582. 0% financing on any project, 25% down. See all pricing
WordPress to Next.js Migration: questions we hear a lot.
Will I lose my Google rankings if I leave WordPress?
Not if the migration is done carefully. We keep URLs where possible, permanently redirect the rest, carry over titles, descriptions, and structured data, and watch Search Console after launch. Google itself says to expect temporary fluctuation during a move, so we plan for it rather than promise zero movement.
How much does a WordPress to Next.js migration cost?
A migration is a rebuild, priced by page count: $1,500 for up to 10 pages, $2,250 for 11 to 20, $3,750 for 21 to 50, and $5,750 for 51 to 70. Larger sites are quoted. Every package includes SEO, design, content writing, content management, lead forms, online booking, one API integration, and a year of support.
Can my team still edit the site after the move?
Yes. Content management is included, and editors get clean fields for text, photos, and posts while the design applies itself. What goes away is the page builder's ability to accidentally rearrange layouts. Most teams find structured editing faster once they've used it for a week.
What happens to my plugins?
Their jobs are rebuilt as part of the site or simply disappear. SEO settings become built-in metadata, forms become custom forms with bot protection, and caching isn't needed because pages are prebuilt. If a plugin does something essential with no good replacement, we'll tell you before you commit.
How long does a migration take?
Most builds go live in 7 to 10 days, and work starts within 24 hours of the go-ahead. Large sites with hundreds of URLs or custom features take longer, and you'll get a realistic timeline after we crawl the current site. We recommend launching outside your busiest season.
Move the site. Keep the rankings.
Send us your current URL. We'll crawl it, count the pages, and tell you which package fits and what the redirect map looks like.