If you need to migrate WordPress to a new host, the goal is simple: visitors should keep seeing a working site the whole time. That is achievable for most sites because DNS lets you choose the moment traffic moves. Until then, the old server carries on as normal while you set up and test the new one.

This guide follows that order: decide, prepare, copy, test, switch and check.

When Should You Migrate WordPress to a New Host?

Moving takes effort, so be clear about why. Common reasons include:

If the main problem is a single slow plugin or an oversized page, moving hosts will not fix it. Diagnose first.

Timing matters too. Avoid moving during your busiest season, a product launch or a big campaign. Pick a quieter window, give yourself time for testing, and make sure you will be around for a day or two after the switch to deal with anything unexpected. Check your current contract as well, so you are not paying for two hosts for longer than you need to, but do not cancel the old plan until the new site has been running smoothly.

What to Check on the New Host First

Settle these questions before you copy a single file. WordPress.org's hosting page and server requirements are a good starting point.

Checklist for a new WordPress host: PHP and database versions, HTTPS, backups, staging, SSH and WP-CLI, server caching, email and support
Settle these before you copy a single file.

Backups and a Pre-Migration Checklist

A migration is also a good moment to tidy up. Before you start:

  1. Take a full backup of files and database, and download a copy. My WordPress backup strategy explains what a reliable backup looks like.
  2. Delete unused plugins, themes and old backup archives sitting inside wp-content.
  3. List everything that relies on the server: forms, payment webhooks, cron jobs, API integrations and email sending.
  4. Note your current DNS records, including MX and TXT records for email.
  5. Lower the TTL on the records you will change, a day or more in advance. TTL controls how long resolvers cache a record, so a lower value means the switch reaches visitors faster.

Moving Files, the Database and Search-Replace

A WordPress site is two things: the files, mainly wp-content plus wp-config.php, and the database. Copy both.

Seven-step timeline to migrate WordPress to a new host: lower TTL, copy, replace URLs, test, final sync, switch DNS and wait
The old host keeps serving visitors until DNS has moved.
wp search-replace 'https://old.example' 'https://new.example' --dry-run

Never use a plain text find-and-replace on a WordPress database dump. Serialised data stores string lengths, and changing the text without updating the lengths can break settings and widgets. The WordPress migration guide also says not to change the guid column.

Test on the New Server Before Switching DNS

This step is what makes a zero-downtime move possible. You can view the new server with your real domain before anyone else does.

Server tower inside a glass test chamber being scanned by horizontal red laser lines, representing testing a new WordPress host before switching DNS
Test the copied site on the new server before any visitor reaches it.

Test as a logged-out visitor as well as an administrator, on a phone as well as a desktop. Make a short list of the journeys that earn you money or enquiries, and run through each one. It is much easier to fix a missing PHP extension or a broken form now, while nobody else can see the new server, than after the switch.

Remove the hosts file entry when you have finished, or you will keep seeing the new server after the switch and miss problems others see.

Switch DNS with Minimal Downtime

For busy sites, especially shops, freeze changes on the old site shortly before the switch. Pause new orders or comments if you can, or plan a final database sync immediately before DNS changes.

Stream of red light particles being diverted at a junction from a dim old server towards a bright new server, representing a DNS switch during a WordPress migration
Changing DNS decides the moment visitors start reaching the new host.
  1. Run the final sync of the database and any new uploads.
  2. Update the A (and AAAA, if used) records, or change nameservers if the new host manages DNS.
  3. Keep the old host running. Some visitors will reach it until cached DNS records expire.
  4. Watch both servers' logs until traffic has clearly moved.

If a redesign is happening at the same time, plan the two separately. My guide to a website redesign without losing SEO covers the URL side.

Email, SSL and Cron After the Move

Most post-migration problems turn up in the same places.

Checks after the DNS switch when moving WordPress to a new host: SSL, email, cron, caches and CDN, and old host
Most post-migration problems show up in these five places.

Frequently Asked Questions

How long does it take to migrate WordPress to a new host?

It depends on the size of the site and how much testing it needs. Copying a small brochure site can be quick, while a large shop needs more time for testing and a final data sync. Allow extra time for DNS changes to reach every visitor.

Will moving hosts hurt my SEO?

Moving to a new host on the same domain does not change your URLs, so rankings should not be affected as long as the site stays available and behaves the same. Keep downtime and errors to a minimum and check Search Console afterwards.

Do I need to change URLs in the database when I move hosts?

Only if the domain or path is changing, for example from a staging address or to a new domain. If the domain stays the same, the database can be moved as it is. When you do change URLs, use a tool that handles serialised data, and leave the guid column alone.

What happens to my email when I change hosts?

If your email is hosted with your old web host, it may stop working when you cancel. Check your MX records before the move and decide where email will live. If you use a separate email service, keep those records exactly as they are when you change DNS.

Can my new host migrate the site for me?

Many hosts offer migration help or tools. It is still worth following the testing and post-move checks in this guide, because you know which forms, payments and integrations matter most.

Final Thoughts

To migrate WordPress to a new host without downtime, keep the old server live while you copy and test on the new one, lower the TTL in advance and switch DNS only when the new site works. Then check SSL, email, cron and caches before you cancel the old plan.

If you would rather have the move handled for you, possibly alongside a refresh of the site, my website revamp service includes careful migrations.

Official References

Sources checked on 29 October 2026: