Skip to main content
Grab a .com from $2.99, with WHOIS privacy included on every name

Blog · Migration

Moving between web hosts without one second of downtime

By the HostingFast team Published 27 July 2026 7 min read

Fear of the move keeps more people on poor hosting than any renewal discount ever has. That fear is misplaced. Done in the right order, a migration costs you no downtime whatsoever, not a little, none, because the old site answers every visitor right up until the new copy has been proven and swapped in. Outages only appear in this story once 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

Three separate jobs make up a migration: copying the site, verifying the copy, redirecting the traffic. Your old host has no notion that a copy exists and carries on serving the domain as usual. Every scrap of risk sits in job three, the DNS change, and that is exactly why it goes last, after the copy has proved itself.

In practice that means keeping the old account paid through the changeover. An overlap costs you a few dollars. An outage costs a good deal more. Copy the lot across, test it hard on the new server, and repoint the domain only after that. Cancel the old plan a week or two later, when nothing relies on it any more.

The sequence, step by step

1. Inventory the lot: site files, databases, mailboxes and everything inside them, the DNS records nobody thinks about such as SPF, DKIM and subdomains, SSL requirements, cron jobs. Migration pain nearly always traces back to whatever got left off that list, and it is usually mail or 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 shifts an inch. Point your hosts file at the new server, or use the host's preview URL, and browse the site as though it were already live. Push through forms, checkout, 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 land on the new server, confirm SSL has issued, then send yourself a test message. Stragglers running on cached DNS keep hitting the old server for a few hours, and since both copies serve identical content, nobody spots the seam.

7. Once a week has passed quietly, pull a final backup off the old account and shut it.

The two errors every outage story shares

Error one: repointing DNS before anyone has verified the copy. Visitors flood into a half-built site and you find yourself debugging in production while customers watch. Every migration-downtime story we hear begins at that precise moment, and the copy-first rule exists so it cannot begin at all.

Error two: shutting the old account too soon. At plenty of hosts, cancellation triggers deletion, so if the new copy conceals a fault, the working original has vanished. Your old account is the rollback. Keep it until the new one has carried genuine traffic for several days running.

Lock-in deserves a paragraph. Look at how hard a provider makes leaving: no backup exports, an obstacle course of retention offers at cancellation, fees charged for moving a domain away. That is a retention strategy on display. Test portability before the day you need it. We hand migrations over free, verified and with nothing offline, because arriving should be simple and nothing technical should stand between you and the door.

Quick answers

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

Measured on the calendar, a few days, and most of that is deliberate waiting through the TTL drop and the watch after cutover. Measured in working hours, a few for an ordinary site, or near enough zero where 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 if the mailboxes already exist on the new host before DNS changes and their contents have been copied across over IMAP. Mail is the part migrations forget most often, so put it at the top of the inventory and plan its cutover as carefully as the website's.

When should I cancel the old hosting, before the move or afterwards?

Afterwards, without exception. Leave it running through the switch and for a week at minimum beyond that. It is your live rollback should the new server misbehave, and the overlap costs a few dollars measured against what an outage genuinely costs.

Up next

More from the blog

The hosting platform behind these posts

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

Browse Hosting Plans