Migrating Your Site to a New Host Without Downtime or Ranking Loss

Why move to a new host in the first place

Usually it's one of a few reasons: the current host has gotten slow or run out of resources (CPU, RAM), support isn't responsive, or your needs changed, say you grew from a simple company site into a store with more traffic. Whatever the reason, the goal of migration is the same: the same content, the same URLs, the same rankings, just running on better infrastructure.

Before doing anything, ask a simple question: is the problem really the host, or the site itself? If a WordPress site is loaded with unoptimized plugins, switching hosts alone won't fix the speed. The website speed guide helps you tell the two apart.

The pre-migration checklist

Most of the migration risk disappears with preparation. Before moving anything, have these ready:

• A full, fresh backup of the current site's files and database, plus a second copy stored somewhere outside the current host.
• A complete list of every domain and subdomain connected to this host, including organizational email if it lives on the same server.
• A note of the current SSL certificate — whether it's free or paid (paid certificates need to be reinstalled on the new host).
• Full access to the domain's DNS management panel, for when it's time to change the records.

If the new host is WordPress hosting, confirm the PHP version and any essential plugins (contact forms, payment gateways) are compatible with the new environment; older plugins sometimes break on a newer PHP version.

Lowering TTL: the step people forget

A domain's DNS record has a TTL (Time To Live) value that tells browsers and other DNS servers how often to re-check the site's IP address. If TTL is left at its default (often several hours to a day), some visitors keep reaching the old server for a while after the DNS switch.

The fix is simple: at least 24 to 48 hours before migrating, lower the domain's A record TTL to something small, like 300 seconds. This lets DNS refresh faster and shortens the window where old and new servers disagree. Once the migration is stable, you can set TTL back to normal.

Migration day: switching without downtime

The key idea is keeping the old and new hosts running at the same time, rather than shutting the old one down early.

1. Copy the files and restore the database on the new host, without pointing the main domain there yet.
2. Fully test the site on the new host through a temporary address (the server IP or a local hosts-file entry): main pages, the contact form, the payment gateway if it's a store.
3. Once you're confident the new copy is healthy, update the domain's DNS record to the new server's IP.
4. For the next while, keep both servers running (don't shut down the old host) so DNS can fully propagate across the internet.
5. After roughly 48 hours, once you're sure every visitor is reaching the new server, retire the old host.

Keeping Google rankings intact

If page URLs don't change and the content stays the same, Google typically doesn't even notice a host migration; server IP address isn't a ranking factor. The real risk shows up if you also change the URL structure at the same time (say, dropping www, or moving to https) — then 301 redirects between old and new URLs need to be set up correctly.

After the switch, watch the Coverage section in Google Search Console for a few days to catch any sudden indexing errors. If your site currently has professional SEO oversight, let that team know about the host migration too, so ranking is monitored alongside the technical change through our website SEO service.

What this doesn't fix

To be honest about the limits: if the site's code is weak or plugins are heavy, changing servers alone won't fix the root cause. We also don't claim migration is always zero-downtime; in the worst case, a few minutes of inconsistency can occur while DNS propagates, not more, provided TTL was lowered in advance.

Frequently asked questions

Does host migration break email?

If organizational email is hosted on the same server, it needs to be migrated separately and the domain's MX record updated. Check email separately before switching the main DNS record.

How long does DNS take to update everywhere?

If TTL was lowered in advance, most visitors usually reach the new server within a few hours; full global propagation can take up to 48 hours.

Do we need to take the site offline during migration?

No. If both hosts stay active at the same time and the pre-switch testing step is done properly, the site stays available to visitors without interruption.

Is faster speed guaranteed after migrating hosts?

A new host gives you a better resource ceiling, but real-world speed also depends on image optimization, caching, and site code; see the website speed page for the full picture.