Switching web hosts is one of those jobs that sounds risky and usually is not, as long as you do it in the right order. The fear is always the same: visitors hit a blank page, email stops arriving, and Google notices the outage. Almost every horror story comes from one mistake, moving the domain before the new server is truly ready. Done properly, a migration happens with visitors never seeing a single error, because the old site keeps serving traffic right up until the new one is proven and live. This guide walks through the exact sequence that keeps your site online the entire time.
Why sites go down during a move
Downtime during a host change is almost never caused by the file transfer itself. It comes from pointing your domain at a new server that has not finished copying, or that is missing a database, an SSL certificate, or an email record. The internet then sends real visitors to a half built site. The fix is a principle rather than a trick: never change where the domain points until the new host is a complete, tested copy of the old one. Keep both environments running in parallel and you always have a working site to fall back to.
Prepare before you touch anything
Preparation is where a clean migration is won. Rushing this stage is what forces emergency rollbacks later. Work through this list before you move a single byte of live traffic.
- Take a full backup. Copy every file, the database, email, and your current DNS records. This is your safety net if anything goes wrong.
- Document the current setup. Note the PHP version, database credentials, cron jobs, and every DNS record including the MX, SPF and DKIM records for email. Missing an email record is the most common way people break their inbox during a move.
- Provision the new host fully. Match the PHP version, install the database, add required extensions, set up caching, and recreate cron jobs before cutover, not after.
- Get the SSL certificate ready. Issue or install the certificate on the new server in advance so the site is secure from the first second it goes live.
Lower your DNS TTL first
This single step is what separates a smooth move from hours of stragglers hitting the old server. TTL, or time to live, tells the world how long to cache your DNS records. Most domains ship with a TTL of 3600 seconds (one hour) or 86400 seconds (a full day). At 24 hours, some visitors could keep landing on your old host for a day after you switch.
Twenty four to forty eight hours before the migration, log into your DNS panel and drop the TTL on your A record to 300 seconds (five minutes). Crucially, you have to wait out the old TTL before the short one is trusted everywhere. If your TTL was one hour, lower it at least a day ahead so every resolver has picked up the new value. When you finally switch, most visitors will see the new server within five to ten minutes instead of hours.
Copy, test, then cut over
With the new host prepared and the TTL lowered, transfer your files using SFTP or rsync for speed and encryption, then import the database. Now comes the step most people skip: test the new site before any real visitor touches it. You can preview it through a temporary staging URL, or edit the hosts file on your own computer to point the domain at the new server IP address. This shows you the new environment in a real browser while the public still sees the old one. Click through every key page, submit a form, and confirm that email sends.
Only once the copy is proven do you update the A record to the new IP address. Because the TTL is low, propagation is fast. How long the whole project takes depends on the site.
| Site type | Typical migration time | Realistic visible downtime |
|---|---|---|
| Small brochure site | 30 minutes to a few hours | None to a few minutes |
| Business site with a CMS | Half a day to 2 days | None when TTL is lowered first |
| Busy store or database app | 2 days to 2 weeks with testing | None with parallel hosting |
Note that visible downtime and total project time are different things. A large store can take weeks to plan and test yet still switch over with zero downtime, because the old site stays live the entire time.
After the switch, do not cancel too soon
The move is not finished the moment DNS updates. Full DNS propagation takes 4 to 8 hours for most people and up to 48 hours worldwide, with a few slow networks lingering as long as 72 hours. During this window a small share of visitors may still reach the old server, so keep your old hosting active for at least 48 to 72 hours after cutover. Once traffic has fully shifted and everything looks stable, restore your TTL to its normal value of 3600 or higher, since a permanently low TTL adds needless DNS lookups and can slow the first page load for new visitors.
When to call professionals
You can move a simple site yourself with this checklist and a calm afternoon. Bring in specialists when the stakes rise: a busy online store where every minute of downtime is lost revenue, a site running custom server software, complex email routing, or a database large enough that a bad import corrupts orders. The cost of a professional migration is almost always smaller than the cost of a store that goes dark during a sale, or an inbox that silently drops customer enquiries for two days.
If you would rather hand this off, our managed web hosting team runs migrations as a fixed scope project with backups, a tested staging copy, and a monitored cutover, so your site never blinks. Request a free migration plan and we will map out exactly how your move will happen before we touch a thing. You can also see the full range of growth services Auronix Solutions offers once your site is on faster, safer infrastructure.
Related reading
Frequently asked questions
Will my website go offline when I switch hosts?
It does not have to. If you keep your old host running, copy and test the site on the new server first, and lower your DNS TTL before switching, visitors keep seeing a working site the entire time. Downtime only happens when the domain is pointed at a server that is not fully ready.
How long does DNS take to update after a host migration?
Most visitors see the new server within 4 to 8 hours, and you should plan for up to 48 hours for a full global update. A few slow networks can take as long as 72 hours. Lowering your TTL to 300 seconds a day before the move shortens the wait to minutes for most people.
When can I safely cancel my old hosting plan?
Wait at least 48 to 72 hours after you change the DNS records, and confirm that traffic, forms and email are all flowing to the new server. Cancelling too early is a common cause of self inflicted downtime, so give propagation time to finish before you close the old account.
