WordPress Migration
Move WordPress between hosts, domains or platforms without losing the map.
Controlled migrations for hosting, domain or CMS changes, with redirects, database and content parity, QA and SEO continuity treated as the project, not a leftover.
A move with a checklist
Migrations break when URLs and tracking are treated as afterthoughts.
Moving a WordPress site between hosts, domains or platforms is a continuity project. The work is an inventory of URLs, content, the database, integrations and measurement, then a destination that can hold them. Redirects are mapped before DNS changes. QA covers journeys, forms and tracking, not only whether the homepage loads. Rankings cannot be promised. Losing the map is optional, and we treat it as a failure of planning.
Typical constraints
The risk is rarely the copy-paste of files.
- 01A host or domain change is planned without a redirect map for URLs that still earn demand.
- 02Content and media look complete until editors find missing fields, broken embeds or orphaned files.
- 03The database moved, but cron, search, cache and environment URLs still point at the old stack.
- 04Forms, payments or CRM connections fail because they were never on the cutover checklist.
- 05Tracking and Search Console were verified after the weekend, not before.
- 06A platform move to WordPress imported pages without a content model the editor can keep.
What you receive
A destination that can be checked against the source.
The artefacts are a map and a rehearsal, not a surprise weekend. Rollback conditions are written before anyone touches DNS.
01
Source inventory
URLs, content types, media, users, integrations and third-party tags listed from the live site, not from memory.
02
Destination model
Hosting, domain, theme and content shape the move is going to, including what cannot be copied one-to-one.
03
Redirect and canonical map
Old paths, files and known parameter cases mapped to destinations, ready to test before go-live.
04
Database and content move
A rehearsed transfer of content, media and required data, with environment-specific values corrected.
05
Cutover QA and rollback path
Journeys, forms, tracking and SEO checks on the destination, plus written conditions for rolling back.
How a move is run
Inventory, map, rehearse, then cut over.
We do not discover missing redirects on Monday morning. The destination is proven against the source before traffic is pointed at it.
01
Source inventory
What exists, what earns demand, and which integrations will break if they are forgotten.
02
Destination model
Host, domain, platform and content model are confirmed so the move has a real landing place.
03
Redirect map
URLs are mapped and tested on the destination, including files, feeds and known campaign paths.
04
Content and database move
A staged transfer is rehearsed. Search, cache, cron and secret values are corrected for the new environment.
05
Tracking and SEO check
Analytics, pixels, Search Console and robots behaviour are verified before the public cutover.
06
Cutover and rollback
DNS or go-live happens against a checklist. Rollback conditions are already written if the destination fails.
When this is the right entry
Migration is the entry when the destination is the point.
- A host change forced by performance, support or a contract ending.
- A domain change that still has to honour years of indexed URLs.
- A move onto WordPress from another CMS, with content that must remain findable.
- A redesign that cannot launch on the current stack and needs a controlled cutover.
- A staging-to-production move that is more than a file copy because integrations are involved.
What we judge
A migration works if visitors, editors and measurement still have a path.
A mapped URL set
Important paths have destinations that were tested, not guessed after the weekend.
Content and data parity you can check
Editors can find the pages, media and fields they expect, with gaps listed instead of discovered in public.
Measurement still attached
Analytics, ads pixels and Search Console are verified on the destination as part of go-live.
A rollback that is a procedure
If the cutover fails, the team knows what happens next instead of improvising.
Related work
Migrations are evidenced by checklists and live URLs, not by slogans.
We will not invent a zero-loss story. When a move is cleared to discuss, it appears in Work with the type of move and the constraints that mattered.
Published case studies will appear here when they are cleared.
Related services
Work that usually sits beside this.
- WordPress RedesignA structured rebuild of an existing WordPress site without losing equity or content.
- Technical SEOCrawlability, indexation, architecture and performance work that search engines can trust.
- WordPress SecurityHardening, access control and recovery planning for WordPress properties that matter.
- Shopify MigrationA planned move to Shopify that treats catalogue, redirects and integrations as project work, not a file export.
Questions
Buying questions, answered directly.
We plan redirects, canonicals, content parity and Search Console so continuity is possible. Rankings cannot be guaranteed. A move that ignores the URL map is how equity is wasted.
Next move
Move the site with a map, not a hope.
Tell us what is moving, why, and which URLs still matter. We will outline the inventory, the redirect work and the smallest safe cutover.