Zero-downtime website migration: moving hosts without breaking your business

At some point almost every growing business outgrows its first hosting provider — or simply wants better speed, support, or pricing. The common fear is that migrating means downtime, broken emails, and lost data. Done correctly, none of that needs to happen. This guide explains what a migration actually involves and how to execute one without your site going dark for a single minute.

What a website migration actually moves

A complete site migration is not just copying files. There are four distinct components, and each one needs to be handled in the right order:

• Website files: All your theme files, plugins, uploaded images, and any custom code. For WordPress sites this is primarily the wp-content folder.
• Database: All your pages, posts, settings, user accounts, orders, and form submissions live in a MySQL database — not in the files. Migrating without the database gives you a shell with no content.
• Email accounts: If your email runs on the same hosting account (e.g. info@yourbusiness.com), the mailboxes, folders, and contacts need to be migrated or pointed to a new mail server. This is the component most often broken during rushed migrations.
• SSL certificate: Your HTTPS padlock must be active on the new host before you cut over DNS. Visitors hitting the site on an insecure connection will see browser warnings and leave immediately.

The DNS cutover: where downtime actually happens (and how to avoid it)

When you move hosts, you update your domain’s DNS records to point to the new server’s IP address. DNS changes propagate across the internet gradually — this is called TTL (Time to Live), and by default it can take up to 48 hours for every visitor worldwide to see the new server. During that window, some visitors hit the old server and some hit the new one.

The professional approach is to lower your TTL to 300 seconds (5 minutes) at least 24 hours before you plan to cut over. Once propagation of that TTL change completes, you make the DNS switch. Within 5 minutes, virtually all traffic is on the new server. The old server stays live and untouched until you are certain everything is working — acting as a safety net. Only then do you decommission it.

Pre-launch checklist

Before you change a single DNS record, confirm every item on this list:

1. Full backup of files and database taken from the old host and stored off-server (not just on the new host).
2. Files and database successfully imported and verified on the new host using a temporary staging URL or hosts file override.
3. All internal links and media URLs resolve correctly on the new host — especially important if you are changing your domain at the same time.
4. SSL certificate issued and active on the new host for your domain.
5. Contact forms, payment gateways, and any third-party integrations tested and working.
6. Email accounts created on the new mail server and IMAP/SMTP settings documented.
7. TTL already lowered on your current DNS for at least 24 hours.
8. A monitoring alert set up so you know immediately if the site returns an error after cutover.

What to ask any migration provider

Not all “free migration” offers are equal. Before you hand over access credentials, ask these questions:

• Do you migrate the database, or just the files? Files-only migrations leave your site broken.
• Do you handle email migration, or is that separate? Many providers migrate the site but leave email for you to sort out — often without telling you upfront.
• What is your rollback procedure if something goes wrong? A serious provider has a documented rollback plan, not just a vague “we’ll fix it.”
• Will there be any downtime? Zero-downtime migration is achievable — if a provider cannot explain how they achieve it, that is a red flag.
• Who do I contact during the cutover window? The DNS cutover is the highest-risk moment. You want a named person available, not a ticket queue.

After the cutover

Once DNS has propagated and the new server is live, spend 30 minutes walking through your site as a real user would: test the checkout if you have e-commerce, submit a contact form, check that emails arrive, verify the SSL padlock on every major page. Do not cancel the old hosting account for at least 7 days — you want a clean fallback if an edge case surfaces in the first week.

If you would rather hand this off entirely, the WebHostLB migration service covers the full stack — files, database, email, SSL, and DNS — with a documented zero-downtime cutover process and post-migration support included.