Hosting migration sounds terrifying until you do it once with a solid plan — then it turns out to be a handful of concrete steps, not a gamble. Here’s the process that minimizes the risk of downtime or losing anything.
Why do this at all
The most common reasons for migration: current hosting is slow (see the previous post on causes of slow sites), it’s more expensive than a market alternative with the same specs, or the panel/support is so inconvenient that every small change takes hours. All three are perfectly valid reasons to switch providers — as long as you do it safely.
Step 1: Full backup before touching anything
Before you move anything, back up:
- Files — everything in the site’s directory (code, images, uploads)
- Database — a full SQL dump export, not just the “important” tables
- Domain configuration (DNS) — a screenshot or export of the current records, so you know what they looked like before the change, in case you need to roll anything back
The rule I follow: if you don’t have a backup in two different places (e.g., local drive + cloud), you don’t have a backup.
Step 2: Set up the new hosting in parallel, without shutting down the old one
This is the most important rule of the entire migration: the old site keeps running the whole time, until the new one is 100% ready and tested. New hosting gives you a temporary address (or you can use your computer’s hosts file) to see the new version of the site under the target domain before anyone else sees it.
Upload the files, import the database, and check that the site actually works — login, forms, payments (if any), every subpage.
Step 3: Test everything thoroughly on the new environment
This is the step people skip most often when in a hurry. Check:
- Whether the contact form actually sends emails (the new server may have different mail configuration)
- Whether all images load (file paths sometimes differ between servers)
- Whether the login panel works correctly
- Whether the
SSLcertificate is active and the site runs onHTTPS
Step 4: Switching DNS — the moment people stress about most (unnecessarily)
Once the new site is tested and ready, you change the domain’s DNS records to point to the new server. This is the only “risky” moment, but in practice it’s safe if you did steps 1-3 correctly — because even if something goes wrong, the old site still exists and you can revert the DNS change.
Worth knowing: DNS propagation (the time it takes for the whole internet to “see” the change) can take anywhere from a few minutes to 24-48 hours, depending on TTL settings. During that time, different visitors might briefly see the old or new version of the site — that’s normal and settles on its own.
Step 5: Monitoring for the first few days
For the first 48-72 hours after migration, check daily that the site works correctly, that forms are actually being delivered, and that no errors are showing up in the new server’s logs. Only after that is it safe to remove the old site and close down the previous hosting.
The most common mistake I’ve seen
Shutting down the old hosting the same day the DNS is changed. Because of DNS propagation, some visitors will still hit the old server for a while — if it’s already gone at that point, they get an error instead of your site. Always keep the old hosting active for at least a week after migration.
Migration sounds like something you’d rather not spend time on? I can do it for you — tell me what hosting you’re on now and where you want to move, and I’ll put together a quote.