Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Blog · Migration

Changing web hosts without a second of downtime

By the HostingFast team Published 27 July 2026 7 min read

More people stay on poor hosting out of fear of the move than any renewal discount ever kept. The fear is misplaced. Run in the right order, a migration produces no downtime at all, not a little but zero, because the old site keeps answering every visitor until the new copy is proven and switched in. Outages only enter the story when the order gets scrambled.

Here is that order, why each step sits where it does, and the two classic blunders behind the horror stories. Move to us and our team handles the entire process at no charge, but knowing what a clean move looks like is worth having anyway, if only to audit our work.

The one rule: copy first, cut over last

A migration is three distinct jobs: copying the site, verifying the copy, and redirecting traffic. The old host has no idea a copy exists and keeps serving your domain as normal. All of the risk is concentrated in job three, the DNS change, which is exactly why it goes last, once the copy has proven itself.

Practically, that means keeping the old account paid through the transition. The overlap costs a few dollars; an outage costs a great deal more. Copy everything over, test it hard on the new server, and only then repoint the domain. Cancel the old plan a week or two later, once nothing depends on it.

The sequence, step by step

1. Inventory everything: site files, databases, mailboxes and their contents, the non-obvious DNS records such as SPF, DKIM and subdomains, SSL needs, and cron jobs. Migration pain almost always comes from the forgotten items on that list, usually mail and the DNS extras.

2. Move files and database onto the new host. WordPress has a well-trodden path, and anything on cPanel restores in one piece from a full account backup.

3. Verify the copy before DNS moves an inch. Use your hosts file or the host's preview URL and browse the new site as if it were live. Work through forms, checkout and login. That unglamorous QA pass is what makes the cutover safe.

4. Lower the DNS TTL to 300 seconds a day before the switch, so the change spreads in minutes instead of days. (What TTL means.)

5. Create the mailboxes on the new host and schedule the mail cutover deliberately. Email is what everyone remembers only once it bounces. The email migration guide covers copying contents across via IMAP.

6. Flip DNS, watch requests arrive at the new server, confirm SSL has issued, and send yourself a test message. Stragglers on cached DNS hit the old server for a few hours, and because both copies serve identical content, nobody sees a seam.

7. After a quiet week, take one last backup of the old account and close it down.

The two errors every outage story shares

Error one: repointing DNS before the copy is verified. Visitors pour into a half-built site and you end up debugging in production with customers watching. Every migration-downtime story we are told starts at exactly that moment, and the copy-first rule exists so it cannot happen.

Error two: closing the old account too early. Cancellation triggers deletion at plenty of hosts, so if the new copy hides a fault, your working original is gone. The old account is your rollback. Hold it until the new one has carried genuine traffic for several days.

A note on lock-in. A host that makes leaving awkward, with no backup exports, a retention obstacle course at cancellation, or transfer-out fees on domains, is showing you its retention strategy. Check portability before you need it. It is also why our migrations run as a free, verified, zero-downtime service: simple to arrive, and nothing technical blocking the exit.

Quick answers

How long does a host-to-host move take?

On the calendar, a few days, mostly deliberate waiting through the TTL drop and the post-cutover watch. In working hours, a few for a typical site, or close to none if the new host runs the move for you. Copy first, switch last, and the site never goes dark.

Does email break when you switch hosts?

Not when the mailboxes already exist on the new host before DNS changes and their contents are copied over IMAP. Mail is the piece migrations forget most often, so put it in the inventory first and plan its cutover as carefully as the website's.

Should the old hosting be cancelled before or after the move?

After, always. Keep it running through the switch and for at least a week beyond. It is your live rollback if the new server misbehaves, and the overlap costs a few dollars set against what an outage really costs.

Up next

More from the blog

The platform these posts come from

Flat renewals, limits stated up front, free migration and support that actually writes back — all of it bundled into a plan.

Browse Hosting Plans