Topic hub

Hosting Migration

A hosting migration moves a website to different infrastructure while ideally keeping the public domain and URLs unchanged. The technical copy is only one part of the task. Databases, email, DNS, certificates, scheduled…

1 published guides0 subtopicsUpdated 21 July 2026

Start here

The main guide for this topic

Step-by-step

How to Move a Website to Another Host

A safe hosting move copies and tests the website before public traffic is switched. The exact commands depend on the platform, but the control sequence is consistent: inventory, backup, compatibility,…

Open the complete guide →

Published guides

Articles in this section

Step-by-step21 July 2026

How to Move a Website to Another Host

A safe hosting move copies and tests the website before public traffic is switched. The exact commands depend on the platform, but…

Read guide →

About this section

This section helps small businesses decide when to move, prepare a controlled migration and verify the result without unnecessary downtime.

Choose the guide that matches the decision

Hosting migration guides
Situation	Guide	Outcome
You are deciding whether a move is justified	When to Change Web Hosting	An evidence-based decision rather than a reaction to one incident
You need the full process	How to Move a Website to Another Host	A staged copy, test, DNS switch and verification plan
You are preparing launch	Hosting Migration Checklist	A repeatable control list with rollback
The migration is failing	Common Hosting Migration Problems	Diagnosis of DNS, database, certificate, email and configuration issues

Distinguish hosting changes from URL changes

If the domain and page URLs remain the same, the move is mainly an infrastructure migration. If the domain, protocol, subdomain or paths change, it is also a URL migration and needs a complete redirect and search-preservation plan.

Avoid combining a hosting move, domain change, redesign and content rewrite unless there is a strong operational reason. Separating changes makes faults easier to diagnose.

Inventory the current environment

website files and databases;
runtime and software versions;
DNS records and nameservers;
mailboxes and email routing;
TLS certificates;
cron or scheduled jobs;
caches, queues and background workers;
uploads, private files and permissions;
CDN, firewall and proxy configuration;
forms, APIs, payment webhooks and external integrations;
backups and restoration procedures.

Plan around changing data

A brochure site may be copied and switched with a short content freeze. An online shop or membership site can receive orders, accounts and updates during migration. Decide how the final database delta will be synchronised and how duplicate or missing transactions will be avoided.

Test before changing DNS

Where possible, run the site on the new host using a temporary address or local hosts-file override. Test representative pages, login, forms, uploads, search, scheduled tasks, payment callbacks and email sending. Compare software versions and error logs.

Protect email separately

Moving web hosting does not always require moving email. Preserve MX, SPF, DKIM, DMARC and verification records unless the email plan explicitly changes them. Record the complete DNS zone before editing it.

Use a rollback point

Keep the old hosting active for an agreed period, prevent conflicting updates and document how DNS or deployment can be reversed. A rollback is useful only if the old data remains consistent enough to restore service safely.

What to monitor after the switch

DNS resolution from different networks;
HTTPS and certificate coverage;
server and application errors;
forms, payments and webhooks;
email delivery;
scheduled jobs;
performance under real traffic;
crawl errors and Search Console verification.

Official search reference

Google Search Central: changing hosting without URL changes

The next practical step is to export the current DNS zone and create an environment inventory before buying or configuring the replacement host.