A new server or host
Files, database, email and DNS reviewed; staging and rollback planned.

A WordPress migration is not just a database import. DNS, email, hard-coded URLs, redirects, forms and commerce all need a plan. We prepare the new environment, test the cutover and keep a rollback path.
No obligation. A fixed scope follows the audit and a review of DNS, email and the current stack.
The URL, database and DNS risks are not the same for each job.
Files, database, email and DNS reviewed; staging and rollback planned.
Redirects, canonical URLs, search console and internal links updated.
Tested content and templates pushed live without losing orders or form entries.
A content model and commerce plan, not a database copy.
Network, subsite and user mapping with a clear URL plan.
Content and URLs preserved while the theme/plugin debt is retired.
The live site stays intact until the new one is tested.
Inventory the site, take a full backup and record DNS/email details.
Build and test the new environment away from production.
Update domains, links, redirects and search settings before launch.
Forms, checkout, users, email and mobile are tested; a rollback is ready.
Switch over, watch the first checks and document what changed.
Most migration surprises are avoidable with a checklist.
MX, SPF, DKIM and DMARC must survive the change.
Serialized data and theme settings can hide the old domain.
Important paths need mapping and a canonical check.
Orders, customers and payment callbacks need post-move tests.
CRM, analytics and marketing tools must be rechecked.
A tested backup and a documented DNS rollback are non-negotiable.
“They actually explained what they were doing instead of just billing us for it. Our booking site has paid for itself twice over.”
What to expect from the move.
Host moves, domain changes, staging-to-live releases, multisite consolidations and rebuilds. Each has a different risk profile for URLs, email and search.
We plan a cutover and a rollback. A short maintenance window may be agreed for DNS or email changes; the aim is to avoid an unplanned outage.
If email is hosted with the website, DNS changes need extra care. We document the current records before changing nameservers.
Yes. Products, customers and orders need a commerce-specific check, and checkout/payment tests happen after the move.
A simple host move can be a short planned job. A domain change with email, redirects and commerce needs longer. The audit and a short review set the scope.
The next useful question, based on what you are dealing with.
Send the current host, target host or domain, and whether email is involved. We will scope the migration and rollback plan before touching DNS.