Migration
How to move web hosting without downtime
You can move a website to a new host with no downtime at all. The sequence is what makes it safe: build and test the new copy while your current site keeps running, shorten the wait time on your address records ahead of the switch, change only the records the website needs, and keep the old site available until the new one is proven. Your visitors never see a broken site, and if anything is not right, the old site is still there to switch back to.
1. Copy before changing DNS
Build the new hosting account first. Copy website files, databases, cron jobs, redirects, and application settings while the old host is still serving traffic.
2. Test the new copy
Test the site against the new server before changing public DNS. Check forms, logins, uploads, scheduled tasks, database writes, SSL, and any application-generated outbound mail.
3. Reduce DNS TTL
Lower the TTL ahead of the move when possible. TTL is the wait time attached to an address record: it tells the rest of the internet how long to remember the answer. Lowering it a day or two early means the final change is noticed within minutes.
4. Sync changing data again
Sites that receive orders, comments, uploads, or other writes need a final database and file sync immediately before cutover.
5. Change only the DNS records the website move requires
Point the website records to the new host only after the new copy is working. A website-hosting move does not require changing MX records when email is staying with the existing mail provider. Keep the old web service online while DNS caches expire.
6. Watch both web servers
Check traffic, error logs, forms, background jobs, database activity, and application-generated messages during the transition.
7. Cancel last
Do not cancel the old hosting account until the new service has been stable and you have a separate backup of the final site. Keeping the old account live is also your way back: if the new site misbehaves after the switch, the address records can point back at the old site while the problem is fixed.
What visitors notice during the move
Nothing, when the move runs in this order. For a short period some visitors reach the old copy and some reach the new one while address changes spread, which is why changing data is synced again at the switch and why the old copy stays up until every visitor is landing on the new one.
Changing the email provider too? Moving mailboxes is a separate cutover with its own steps for changing email hosting without downtime. Follow the email hosting migration guide before changing mail routing. Email that already runs on Microsoft 365 or Google Workspace does not need to move at all.
