WordPress migration service, delivered under your brand
Your client is stuck on a WordPress site that is slow, fragile and expensive to keep alive, and they will not fund a rebuild they do not understand. We move them onto Astro or Next.js without losing a single URL, working white-label so the migration stays yours.
The problem
Why WordPress becomes your problem, not the client's
The cost of an ageing WordPress build lands on the agency long before the client agrees to do anything about it.
The maintenance never ends
Plugin updates, PHP version bumps, a security patch every other week. None of it is billable, and all of it lands on you.
Performance work that will not hold
You buy a caching plugin, claw back a few points, and the next plugin update undoes it. The page-speed problem is structural, not a setting.
One bad plugin takes the site down
A dependency you did not choose breaks the front end on a Friday, and the client calls you rather than the plugin author.
You cannot quote the rebuild
The client will not pay for a rewrite they see no reason for, so the site stays as it is and the maintenance burden compounds.
Scope
What comes across in a WordPress migration
The parts that decide whether the client notices the move for the right reasons or the wrong ones.
Content and media
Posts, pages, taxonomies and the media library, moved into a headless CMS the client logs into as before.
Every URL
A mapped 301 for each existing path, verified against the live site before switchover rather than discovered afterwards in Search Console.
SEO signals
Titles, descriptions, canonicals, hreflang, structured data and the XML sitemap carried across rather than re-created from scratch.
Forms and integrations
Contact forms, analytics, tag manager and CRM hooks rebuilt on the new stack and tested against real submissions.
Process
How a migration runs
Four steps, and the first one can end with us telling you not to migrate.
Audit before anything is quoted
We crawl the existing site, inventory the plugins and list what actually has to survive the move. If a plugin is genuinely load-bearing and cannot be replaced, we tell you the site should stay put.
Redirect map first
The URL map is built and reviewed before the rebuild, because it is the part that decides whether the client keeps their traffic.
Rebuild on Astro or Next.js
Static where static is enough, dynamic where the project needs it. Same design, or a new one if that is in scope.
Switchover and verification
We stage the new site, check redirects and metadata against the old one, then cut over. Source code is delivered to you.
When we will tell you not to migrate
A WordPress site running a heavily customised WooCommerce setup, a membership system, or a plugin with no equivalent outside the ecosystem is usually better left where it is. We would rather lose the project at the audit stage than hand you a migration that costs your client their functionality. If that is the call, you get the reasoning in writing and no invoice.
Pricing
What a migration costs
Migrations are priced like builds, on the number of pages and the complexity of what has to be carried across. The audit tells us which tier applies before you quote your client.
Landing
One conversion page for your marketing campaigns.
- 1 responsive page
- Bespoke design
- Contact form
- Basic SEO optimisation
- Analytics integration
Showcase
3-5 pages for a complete professional presence.
- 3 to 5 responsive pages
- Advanced technical SEO
- Lighthouse performance 90+
- Source code delivered
Flagship
6-10 pages optimised for local search.
- 6 to 10 responsive pages
- Service + location pages
- Optimised SEO architecture
- Schema.org / rich snippets
- Source code delivered
Custom projects or specific needs? Contact us for a personalised quote.
FAQ
WordPress migration questions
What agencies ask before handing over a client's site.
No. We migrate away from WordPress, we do not develop on it. If your client wants to stay on WordPress, we are the wrong partner and will say so on the first call rather than waste your time.
Astro for content and brochure sites, Next.js where the project needs dynamic rendering, authentication or an application layer. We pick the one that fits the project rather than defaulting to the heavier option.
That is the main risk in any migration, and it is handled deliberately: every existing URL is mapped to its destination with a permanent 301, metadata and structured data are carried across, and the redirect map is verified against the live site before switchover rather than after.
Yes. Editing moves to a headless CMS the client logs into as before. What changes is that the public site is pre-rendered, so an editing mistake cannot take the front end down.
They are audited first. Most are replaced by something built in, a few map to a hosted service, and occasionally one is genuinely load-bearing and the honest answer is that the site should stay where it is. You get that assessment before any work is quoted.
Only if you want them to. The default is white-label: we work under your brand, in your project tooling, and the client deals with you throughout.
Send us a WordPress site to assess
We will crawl it, inventory the plugins and tell you whether it is worth migrating. No cost, and no obligation to proceed.
Response guaranteed within 24 working hours