Switching Hosts Without Downtime: The Migration Guide

Audit the current setup before moving

Changing hosts starts with a complete inventory, not a move. List what you own: the site (files and database), email accounts and their content, domain names and their DNS records, SSL certificates, and any auxiliary services (subdomains, redirects, cron jobs). Also note access credentials and the contacts who own the domain.

This audit often reveals forgotten elements: an old follow-up email address, a test subdomain, a redirect, or a certificate to renew. It is better to discover them before the switch than after, when the old host has already cut everything off. Dedicate the necessary time to this inventory: it is what prevents most losses.

Choose the right time

A migration is never neutral for a live site. Choose a period of low traffic, ideally a weekend or off-peak hours, and never during a commercial campaign. Keep access to the old host at hand: you will need it until the end.

The goal is not to go fast, but not to lose anything. A prepared migration takes a few hours; a rushed one is paid for in days of troubleshooting. If possible, also plan a rollback procedure: knowing how to go back in case of a problem is just as important as moving forward. Notify stakeholders (internal teams, partners) in advance who might be surprised by a potential disruption. Clear communication avoids unnecessary alerts on D-Day.

DNS, emails, databases: what must follow

Three elements must be transferred in a coordinated manner: the site, emails, and DNS. DNS is the directory that indicates where to find your domain; it is what directs visitors to the correct server and messages to the correct mailbox. If you forget emails, your site will work but your mailboxes will remain empty. If you forget the database, your site will display an empty shell.

DNS records are cached, and the duration of this cache corresponds to the TTL (Time to Live). A long TTL means that a change takes longer to propagate everywhere. This is why best practice is to lower the TTL of your records in advance, so that the switch propagates quickly when the time comes. Consult our guide to change your domain's DNS.

The seamless switch

The switch is prepared in several stages. First, copy your files and database to the new host while the old one continues to provide the service. Then test the new site by previewing it locally or via a temporary URL, without changing the public DNS. Once the new site is validated and the TTL has been lowered in advance, switch the DNS to the new host.

During propagation, some visitors will still see the old server and others the new one. To avoid any discrepancy, keep the old site online for a few days, until propagation is complete, then shut it down properly. This overlap is what makes the transition transparent for the end user.

Verify after migration

After the switch, check methodically: the site responds on the new server, the SSL certificate is valid, forms and payment work, emails are sent and received, and old addresses remain accessible. Test from multiple networks and on mobile.

A systematic verification turns a successful migration into a confirmed migration. This is also the time to make a full backup of the new environment, to start from a healthy base. Note what has been checked: in case of future doubt, you will know what has already been controlled. Keep this checklist: it will also serve for the next migration.

Changing hosts: pitfalls to avoid

The most common pitfalls: forgetting emails in the migration plan, switching without having lowered the TTL in advance, shutting down the old hosting too early, neglecting to test the database restoration, and not checking the SSL certificate afterwards. Another classic pitfall is losing access to the old account before recovering everything.

Before starting, make a backup copy of everything you are moving: it is your safety net if the switch encounters an issue. If you are also transferring your domain name, consult our guide on domain transfer.

A well-run migration is unnoticed: your visitors notice nothing and your data arrives intact. To choose the right destination, read our guide choosing web hosting, our article on domain transfer and that on SLAs.

Atlas Hoster supports the migration of files, databases, and emails from an existing cPanel or any other hosting: request a quote.

The countdown of a migration

To summarize, a seamless migration always follows the same order:

1. Inventory and back up.
2. Lower the DNS record TTL in advance.
3. Copy files and the database to the new host, then test.
4. Switch DNS, then email MX records.
5. Verify functionality, then cancel the old service.

Keep this list at hand: it reassures stakeholders and serves as a framework for the migration. If the switch reveals a problem, a rollback plan allows you to go back in a few minutes rather than several days.

FAQ

How long does DNS propagation take? It depends on the TTL of your records and the resolvers' cache. By lowering the TTL in advance, the switch propagates in a few minutes to a few hours.

Is there a risk of losing emails during the migration? Not if you create the mailboxes on the new host before switching the MX records, and if you keep the old service active during the transition.

Can I migrate without any downtime? Yes, by preparing the new environment in parallel and only switching the DNS once everything has been tested. A short propagation window remains inevitable, but it does not interrupt the service.