Switching Web Hosts With Zero Downtime, Step by Step
Your hosting renewal email arrives with a price that has quietly doubled, from 3 euro a month to 11, and suddenly switching providers looks worth the effort.

Your hosting renewal email arrives with a price that has quietly doubled, from 3 euro a month to 11, and suddenly switching providers looks worth the effort. Then the fear sets in: what if the site goes offline for two days, or the contact form stops working, or email vanishes? The good news is that you can move a website to a new host without downtime if you do things in the right order, and most of the work happens before anyone visiting your site notices a thing.
I have moved dozens of small business and personal sites between hosts. Nearly every horror story I hear comes from doing the steps out of order, usually cancelling the old plan too soon or changing DNS before the new copy was tested. Here is the sequence that avoids that.
Why Moving Hosts Causes Downtime in the First Place
Your domain name points to a server through DNS records. When you move, you copy your site to a new server and then update those records to point at it. Downtime happens in the gap: when the records point somewhere that is not ready, or when the old server is switched off while some visitors are still being sent there.
DNS changes do not take effect everywhere at once. Each record has a TTL, a time to live, which tells networks around the world how long they may remember the old answer. If you want the background, I explain it in why your new domain is not loading yet. The short version is that old and new servers both need to work for a while, so visitors land on a working site whichever one they reach.
Before You Start, Take Stock
Write a list of everything the old host does for you. People remember the website and forget the rest.
- Website files and, for most sites, a database.
- Email accounts on your domain, if the host provides them.
- DNS records, including any for email, verification or third party services.
- SSL certificate, which you will need again on the new server.
- Scheduled tasks such as backups or cron jobs.
- Software versions, especially the PHP version if you run a CMS.
Take a screenshot of every DNS record in the old control panel. This one step has saved me more times than any other.
The Steps to Move a Website to a New Host Without Downtime
- Lower the TTL. Two days before the move, set the TTL on your main records to 300 seconds, or five minutes. Changes will then spread quickly on moving day.
- Buy the new plan, but keep the old one. Do not cancel anything yet.
- Take a full backup of files and database from the old host, and download it to your own computer.
- Upload to the new host and import the database. Update the configuration file with the new database name, user and password.
- Test before switching. Use the new host's temporary address, or edit the hosts file on your computer so only you see the new server.
- Set up SSL on the new server. Many hosts issue a free certificate automatically once the domain points there, so check how yours handles it.
- Freeze changes on the old site, such as new posts, orders or comments, for the switch window.
- Update DNS to point to the new server.
- Wait at least 48 hours with both servers running, then check for any late traffic on the old server.
- Cancel the old plan only after that, and after downloading one final backup.
Testing the New Copy Properly
Step five is where downtime is really prevented, and it is the one most people rush. Editing your computer's hosts file lets you load your real domain from the new server while the rest of the world still sees the old one. Your host's help pages will show you the IP address to use.
Then click through the site as a visitor would. Check the home page, a few deep pages, images, the contact form, any login areas and the checkout if you sell anything. Submit the contact form and confirm the email arrives. A site that loads but cannot send mail is the most common failure I see after a move, usually because the new server handles outgoing mail differently.
Why the Free Migration Service Is Not Always the Easy Option
Most hosts now offer a free migration, and the usual advice is to accept it and let them handle everything. Sometimes that is right. For a standard WordPress site with no unusual setup, a host's migration tool works well.
But I would not hand it over blindly. Free migrations often copy the files and database and stop there. They may not move email, may skip DNS records for services like your newsletter tool, and may switch DNS for you before you have tested anything. Some also take three to five working days to schedule, during which you are paying for two plans. If your site is small and simple, doing it yourself in an evening can be faster and leaves you in control. If you do use the service, ask in writing exactly what it includes, and keep your own backup regardless.
Handling Email During the Move
If your email is hosted with your old provider, plan this part separately. Create the same mailbox names on the new host before switching DNS. After the switch, new messages start arriving at the new server once the MX records update, while older messages stay on the old one. Download or move those before you cancel the old plan.
For many small sites, the move is a good moment to separate email from hosting entirely, using a dedicated mail provider. That way, the next time you switch hosts, email is not affected at all. If you are moving because you have outgrown cheap hosting, my comparison of shared hosting and a VPS may help you pick the right plan.
A Realistic Timeline
| When | Task |
|---|---|
| Day 1 | Take stock, screenshot DNS, lower TTL |
| Day 2 | Buy new plan, back up, upload files and database |
| Day 3 | Test via hosts file, set up email accounts |
| Day 3 evening | Freeze changes, switch DNS |
| Days 4 to 5 | Run both servers, check logs and forms |
| Day 6 or later | Final backup, cancel the old plan |
Choose a quiet time for the switch. For most small sites that is a weekday evening or a Sunday morning, not a Monday when enquiries peak.
Frequently Asked Questions
Will moving hosts affect my search rankings?
Not if the URLs stay the same and the site stays online. Search engines care about the address and content, not which server it sits on. A faster host can even help slightly.
Do I need to move my domain registration too?
No. Your domain can stay with its current registrar. You only need to change the DNS records or nameservers to point to the new host.
How long does DNS take to update?
With a TTL lowered to five minutes in advance, most visitors reach the new server within an hour. A few networks may take up to 48 hours, which is why both servers should run in parallel.
The Order That Keeps You Online
Lower the TTL, copy the site, test it privately, then switch DNS, and only cancel the old plan once traffic has fully moved. Follow that order and a host move becomes an evening's work rather than a weekend of panic.
More in Hosting and Domains
Hosting and Domains
Inode and Entry Process Limits on Shared Hosting
A reader wrote to me last March after his host suspended his site at nine on a Friday evening.
Hosting and Domains
How to Set Up a Staging Site on Cheap Shared Hosting
A plugin update at nine in the evening is how most small sites go down.
Hosting and Domains
What Is Managed WordPress Hosting and Is It Worth Paying For
Your WordPress site is slow, an update broke something last month, and a hosting company is offering to "take care of...