Blog · Migration

How to switch web hosts without downtime

By the HostingAlly team Published 27 July 2026 7 min read

More people stay on bad hosting out of fear of moving than were ever kept there by a renewal discount. That fear is misplaced. Run a website migration in the correct order and downtime is zero, not 'minimal', actually zero, because the old site carries on serving every visitor until the new one is proven and live. Scramble the order and downtime walks in.

Below you'll find the order, why each step sits where it does, and the two classic blunders that produce the outages everyone dreads. (Move to us and our team does all of this for you, free. You should still know what 'done right' looks like, if only so you can check our work.)

The golden rule: copy first, switch last

Think of a migration as three separable acts: copy the site, verify the copy, redirect the traffic. Your old host neither knows nor cares that a duplicate exists, and it goes on serving your domain exactly as it did yesterday. Every ounce of risk sits in act three, the DNS switch. Which is why act three happens last, once the copy has been proven working.

In practice: keep paying for the old hosting right through the move, since overlap costs a few dollars and an outage costs a lot more. Copy everything across to the new host. Test it there properly. Only then point the domain. Cancel the old plan a week or two after the switch, once nothing has come back to bite you.

The order of operations

1. Inventory. Site files, databases, email accounts along with everything inside them, DNS records past the obvious ones (SPF, DKIM, subdomains), whatever SSL you need, and any cron jobs. Whatever gets forgotten off that list, and it is usually email plus the DNS extras, is where migration pain originates.

2. Copy the files and the database over to the new host. WordPress has a well-trodden path for this. On cPanel, a full account backup restores the lot in one go.

3. Verify on the new server while DNS still points elsewhere. Edit your hosts file, or use the provider's preview URL, and browse the copy as though it were already live. Click through the forms, the checkout, the login. That dull QA pass is exactly what makes act three safe.

4. Drop the DNS TTL down to 300 seconds a day ahead of the switch, so when the change lands it propagates in minutes rather than days. (TTL, explained.)

5. Recreate the mailboxes on the new host and plan the mail cutover with care. Email is what everybody forgets, right up until it bounces. Our email migration guide covers shifting the contents across via IMAP.

6. Switch DNS. Watch the traffic land on the new server, confirm SSL has issued, fire off a test mail. Stragglers on cached DNS carry on hitting the old server for a few hours, and since both copies serve identical content, nobody notices a thing.

7. Once a quiet week has passed, take a final backup of the old account, then cancel.

Two mistakes sit behind every migration horror story

First mistake: flipping DNS before the copy has been verified. Traffic hits a half-working site, and suddenly you are debugging in production with customers watching. Every 'migration downtime' story that reaches us begins right there. The golden rule exists to make that impossible.

Second mistake: cancelling the old host too soon. At plenty of hosts, cancellation triggers deletion, and if something on the new copy turns out broken, the working original has already gone. Treat the old account as your rollback. Keep it alive until the new one has served real traffic for days.

A structural note about lock-in. When a host makes leaving hard, no backup exports, a retention gauntlet at cancellation, transfer-out fees slapped on domains, it is telling you exactly how it keeps customers. Portability is a feature worth checking long before you need it. That is also why we run migration as a free, verified, zero-downtime service that cuts both ways: easy to join us, and nothing technical standing between you and the exit.

Quick answers

How long does switching web hosts take?

Elapsed time runs to a few days, most of it deliberate waiting: the TTL reduction, then watching after the switch. Active work comes to a few hours on a typical site, or close to nothing where the new host handles the migration for you. Follow the copy-first, switch-last order and the site never goes down at all.

Will my email go down when I change hosts?

No, provided you create the mailboxes on the new host before DNS switches and shift the contents across via IMAP. Email is the piece people forget more often than any other part of a migration. Inventory it first, and plan its cutover as carefully as you plan the website's.

Do I cancel the old hosting before migrating, or after?

After, every time. Leave the old account running through the switch and for a week beyond it at minimum. It stands as your working rollback should anything on the new server misbehave, and the overlap costs a few dollars set against what an outage really costs.