How to move a WordPress site to a new host without downtime

You move a WordPress site without downtime by copying it in full to the new server, testing it on a temporary link and switching DNS only once everything works. The old site stays online until the end, so visitors never land on a blank page. Below is what gets moved, how to test, and how to make the switch, so you can stop putting off a move away from slow or expensive hosting for fear that a zero-downtime WordPress migration won't work.

Why downtime can be avoided

Many people think moving hosts means shutting down the old site, moving it and hoping it starts on the new one. In a proper migration, the old site stays online and working until the new copy is made, tested and confirmed. Only then do you move the traffic. For a few hours you have two identical copies running side by side, and the switch from one to the other isn't visible from outside.

The one delicate moment is DNS propagation, the period when the internet learns the server's new address. That can be handled too: if both copies are identical, it doesn't matter which server a visitor reaches during propagation, because they see the same content. There's no window where the site is missing.

What gets moved, exactly

A WordPress site has four parts, and you need to move all of them. Miss one and you get problems that are hard to track down: forms that don't send, email that stops working, missing images. The migration covers:

• The site files: everything in the WordPress directory, meaning the theme, plugins, the files in wp-content/uploads (images, PDFs, other uploads) and the wp-config.php configuration file.
• The MySQL database: this holds your posts, pages, settings, comments and user accounts. Without it you have an empty WordPress install.
• Email accounts: if you use addresses like name@your-domain.ro hosted on the old server, the mailboxes and messages have to be copied separately, because they aren't part of WordPress.
• The DNS zone and the domain: the records that say where the site and email live. The domain itself doesn't move; you just point it at the new server.

Files and database are the site itself; email and DNS cover the rest. Skip the last two and the migration looks successful until someone tries to send a message through the contact form.

The steps of a zero-downtime WordPress migration

The order is simple: build the new copy in full, check it, and move the traffic last.

1. Make a full backup

Before anything else, save all files and the database from the old server. Even if the migration goes perfectly, the backup is your safety net. While the move is under way, don't change the site (don't publish posts, avoid important orders), so you don't lose data created between the copy and the switch.

2. Copy the files and database to the new server

Move all the files and import the database on the new hosting. On NVMe this step takes much less time than on old HDD hardware. At the end, update wp-config.php with the new database connection details.

3. Test on a temporary link, without touching DNS

This is the step that keeps the site online. You can open the site on the new server before your real domain points to it, either through a temporary link or by editing the hosts file on your computer. You see the new site exactly as it will look, while visitors are still on the old server.

4. Check everything end to end

Go through the main pages, test the forms, check the WooCommerce store if you have one, log into the admin panel, and confirm images load and plugins work. Whatever problem you find, you fix it now, on the test copy, without rushing and without anyone noticing.

5. Switch DNS only when you're 100% sure

When everything checks out, change the DNS records to point to the new server. To make the switch quick, lower the TTL (how long the records are cached) a day in advance. Since both copies are identical, visitors see the same site during propagation too. That's where "without downtime" comes from.

How to test on a temporary link before changing DNS

Many people skip this step, yet it's what separates a calm migration from a stressful one. There are two safe methods:

• Temporary link (preview): an address from the new host that shows the site on the new server without affecting the public domain. Good for a quick check of the pages.
• The hosts file: on your own computer, you point your real domain at the new server's IP. That way you test with the correct domain (which matters for WooCommerce, logins and payments tied to the domain), while everyone else still sees the old server.

If the site has features that depend on the domain, test with the hosts file. When you're done, delete the line you added and everything goes back to normal. Only once you're happy do you make the real DNS change.

Why it's worth handing the migration to a technical team

Anyone with patience can follow the steps above. In practice, each stage has traps: different table prefixes, old URLs left in the database, wrong file permissions, SSL certificates that need reissuing or incomplete DNS zones. One small mistake can turn "zero downtime" into a few hours of panic.

That's why BTU offers free migration done by our team: we copy the files and database, set up email, reissue the SSL certificate, test everything on a temporary link and switch DNS together with you, so visitors don't feel the move. You confirm the new site looks right; we handle the technical side.

Moving to hosting built for WordPress usually brings a speed boost too. Our NVMe servers with LiteSpeed and caching load your site faster from the first day after the migration, and technical support answers in Romanian.

In short

A zero-downtime WordPress migration comes down to order: make the new copy, test it on a temporary link and switch DNS only once everything is confirmed. If you'd rather skip the technical part, take a look at BTU's NVMe WordPress hosting and let us do the move, for free and planned so your customers aren't left without a site.