Blog · Migration
Moving to a new web host with zero downtime
By the Hosting Seller team Published 27 July 2026 7 min read
Fear of the move keeps more people on poor hosting than any renewal discount ever managed. It shouldn't. Done in the right order, a migration involves no downtime at all, not minimal but none, 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 shuffled.
So here is the order, the reason behind each step, and the two classic errors that produce the outages people are afraid of. If you move to us, our team runs the whole thing for you at no charge, but knowing what a proper move looks like is worth having anyway, if only to check our work.
The rule: copy first, switch last
A migration is three separate acts: copying the site, proving the copy, and redirecting traffic. The old host neither knows nor cares that a copy exists, and carries on serving your domain exactly as before. Every scrap of risk lives in act three, the DNS switch, which is why it goes last, after the copy has been shown to work.
In practice that means keeping the old hosting paid up through the move, since an overlap costs a few dollars and an outage costs a great deal more. Copy everything across, test it properly on the new server, and only then point the domain. Cancel the old plan a week or two later, once nothing is looking back.
The order of operations
1. Take stock: site files, databases, email accounts and their contents, any DNS records beyond the obvious such as SPF, DKIM and subdomains, SSL requirements, and cron jobs. The forgotten entries on that list, usually mail and the DNS extras, are where migration pain actually comes from.
2. Copy files and database to the new host. WordPress has a well-worn route, and anything on cPanel restores wholesale from a full account backup.
3. Prove the copy before touching DNS. Use your hosts file or the host's preview URL to browse the new site as though it were live. Click through forms, checkout and login. That dull QA pass is what makes act three safe.
4. Drop the DNS TTL to 300 seconds a day ahead of the switch, so the change spreads in minutes rather than days. (TTL, explained.)
5. Recreate mailboxes on the new host and plan the mail cutover deliberately. Email is the thing everyone forgets until it bounces. The email migration guide covers moving the contents over IMAP.
6. Switch DNS, watch traffic land on the new server, confirm SSL has issued, send a test message. The old server keeps answering stragglers on cached DNS for a few hours, and since both copies serve the same content nobody notices a thing.
7. After a quiet week, take a final backup of the old account and close it.
The two mistakes behind every horror story
First mistake: switching DNS before proving the copy. Traffic arrives at a half-finished site and you are debugging in production with customers watching. Every migration-downtime story we hear begins right there, and the copy-first rule exists to make it impossible.
Second mistake: cancelling the old host too soon. At many hosts cancellation triggers deletion, so if something on the new copy turns out to be broken, the working original has gone. The old account is your rollback. Keep it until the new one has carried real traffic for several days.
A word on lock-in. Hosts that make leaving awkward, with no backup exports, a retention gauntlet on cancellation, or transfer-out fees on domains, are telling you how they keep customers. Portability is worth checking before you need it. It is also why we run migration as a free, verified, zero-downtime service: easy to join, and nothing technical in the way if you ever want to go.
Short answers
How long does switching web hosts take?
On the calendar, a few days, most of it deliberate waiting for the TTL drop and post-switch observation. In actual work, a few hours for a typical site, or close to none if the new host runs the move for you. Follow copy-first and switch-last and the site stays up the whole way.
Will my email go down when I change hosts?
Not if the mailboxes exist on the new host before DNS moves and the contents are copied over IMAP. Mail is the most commonly forgotten part of a migration, so inventory it first and plan its cutover as carefully as the website's.
Should I cancel my old hosting before or after migrating?
After, every time. Keep the old account running through the switch and for at least a week afterwards. It is your working rollback if the new server misbehaves, and the overlap costs a few dollars against what an outage really costs.
Also on the blog
Web hosting costs in 2026: the whole bill
The tag on the shelf is advertising. The renewal is the product. Here is the three-year arithmetic, worked out in the open.
“Unlimited” web hosting: where the limits really sit
Disks have sizes. 'Unlimited' translates to 'limited by units you haven't met yet': inodes, CPU seconds and a fair-use paragraph.
Free domain with hosting: four things to check before you claim one
The free year is genuine. Year two is where the questions live: renewal rate, whose name is on the record, and what leaving costs.
The product behind the posts
Flat renewals, limits printed on the tin, free migration and a help desk that replies — everything above, in plan form.
Browse Hosting Plans