Blog · Migration

How to switch web hosts without downtime

By the HostingAlly team Published 27 July 2026 7 min read

Fear of the move keeps more people on bad hosting than any renewal discount ever has. It shouldn't: a website migration done in the right order involves zero downtime — not 'minimal', zero — because the old site keeps serving every visitor until the new one is proven and live. Downtime only enters the story when the order gets scrambled.

Here is the order, the reasoning behind each step, and the two classic mistakes that cause the outages people fear. (If you move to us, our team does all of this for you, free — but you should still know what 'done right' looks like, if only to check our work.)

The golden rule: copy first, switch last

A migration is three separable acts: copying the site, verifying the copy, and redirecting traffic. The old host doesn't know or care that a copy exists — it keeps serving your domain exactly as before. All risk lives in act three, the DNS switch, so it happens last, after the copy has been proven working.

Concretely: keep the old hosting paid up through the move (overlap costs a few dollars; an outage costs more), copy everything to the new host, test it there thoroughly, and only then point the domain. Cancel the old plan a week or two after the switch, once nothing looks back.

The order of operations

1. Inventory: site files, databases, email accounts and their contents, DNS records beyond the basics (SPF, DKIM, subdomains), SSL needs, and cron jobs. The forgotten items on that list — usually email and DNS extras — are where migration pain actually comes from.

2. Copy files and database to the new host. For WordPress this is a well-trodden path; for anything on cPanel, a full account backup restores wholesale.

3. Verify on the new server before DNS changes, using your hosts file or the host's preview URL to browse the copy as if it were live. Click through forms, checkout, login — the boring QA pass that makes act three safe.

4. Drop the DNS TTL to 300 seconds a day before switching, so the eventual change propagates in minutes instead of days. (TTL, explained.)

5. Recreate mailboxes on the new host and plan mail cutover deliberately — email is the thing people forget until it bounces. The email migration guide covers moving contents via IMAP.

6. Switch DNS, watch traffic arrive at the new server, confirm SSL issued, send test mail. The old server keeps answering stragglers on cached DNS for a few hours — both copies serve identical content, so nobody sees anything.

7. After a quiet week: final backup of the old account, then cancel it.

The two mistakes that cause every horror story

Mistake one: switching DNS before verifying the copy. Traffic arrives at a half-working site, and now you're debugging in production while customers watch. Every 'migration downtime' story we hear starts here, and the golden rule exists to make it impossible.

Mistake two: cancelling the old host too early. Cancel triggers deletion at many hosts — and if anything on the new copy proves broken, your working original is gone. The old account is your rollback; keep it until the new one has served real traffic for days.

A structural note on lock-in: hosts that make leaving hard — no backup exports, retention-gauntlet cancellations, transfer-out fees on domains — are telling you something about how they retain customers. Portability is a feature to check before you need it. It's also why we run migration as a free, verified, zero-downtime service in both directions of confidence: easy to join, and nothing technical stopping you from leaving.

Quick answers

How long does switching web hosts take?

Elapsed time: a few days, dominated by deliberate waiting (TTL reduction, post-switch observation). Active work: a few hours for a typical site, or near zero if the new host runs the migration for you. The site itself stays up throughout when the copy-first, switch-last order is followed.

Will my email go down when I change hosts?

Not if mailboxes are created on the new host before DNS switches and the contents are moved via IMAP. Email is the most commonly forgotten part of migrations — inventory it first, and plan its cutover as deliberately as the website's.

Should I cancel my old hosting before or after migrating?

After — always. Keep the old account running through the switch and for at least a week beyond it. It's your working rollback if anything on the new server misbehaves, and the overlap costs a few dollars against an outage's real price.