Migration
How to move web hosting without downtime
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. That reduces how long old website DNS answers remain cached after the final change.
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.
Changing the email provider too? Moving mailboxes is a separate cutover with its own MX, synchronization, alias, authentication, and client-setting steps. Follow the email hosting migration guide before changing mail routing.