WordPress migration to new hosting or a new domain: the step-by-step plan without downtime

Moving a WordPress site to new hosting or a new domain can be done without your site being unreachable for even a minute. The trick is in the sequence: you first build the complete site on the new environment, test it on a hidden address, and only once everything works do you switch the DNS. That way the old address stays live until the new one is ready, and not a single visitor notices anything. In this guide we walk through the technical plan step by step, from backup and database to media and DNS, specifically for WordPress.

This article is about the technical move itself. If what you mainly want to know is how to protect your Google rankings during a move, read website migration without losing rankings. The two belong together: a migration can go technically perfectly and still cause SEO damage if you forget the redirects. Here we focus on the part that keeps your site online. For the broader context of building and maintaining, take a look at our guide to B2B website development.

What does a WordPress migration involve technically?

A WordPress migration means you move three things: your files, your database and your domain pointing. The files are your themes, plugins and uploaded media. The database contains all your content, settings and users. The domain, managed through DNS, decides which server visitors are sent to. A move is only successful once all three are correctly in their new place and pointing at each other.

The type of move determines how much work you face. If you only move to a faster host while your domain stays the same, not a single URL changes and the risk is low. If you also switch domain, all your addresses change and an SEO layer is added on top of the technical work. So treat a migration as a genuine project with a backup, a testing round and a fallback plan, not as a half-hour job. It is also worth digging into the broader approach to migrating a domain or hosting without downtime, which is not tied to WordPress.

How do you move WordPress without downtime?

You avoid downtime by switching the DNS only at the very end, once the new site is fully tested and ready. The mistake people make is redirecting the DNS immediately and only then setting up the new environment. Your site is then offline for as long as the build takes. Do the opposite: build first, test on a hidden address, then switch over.

Two technical preparations make all the difference. First, lower your DNS TTL (Time To Live, the length of time servers remember your address) to 300 seconds, roughly 24 to 48 hours before the move. That way your later DNS change propagates in minutes rather than hours. On top of that, test the new site before the DNS switch, either through a change to your local hosts file or through a temporary test domain from your hosting provider. You then see the new environment exactly as visitors will get it, while the old site simply stays live.

The technical plan step by step

Work with a checklist and tick off every step. Improvising a migration almost always leads to a forgotten component.

The six steps below deliberately follow one thread: every preparation happens while the old site simply stays live, and only the final step touches what visitors see.

1. Full backup and baseline measurement

Make a complete backup of your files and your database before you touch anything. This is your safety net. Also jot down a baseline: loading speed, a few important pages and your forms, so that after the switch you can check whether everything still works as it did before.

2. Lower the DNS TTL

Set your domain’s TTL to 300 seconds 24 to 48 hours in advance. If you do not, the final switchover can take hours for some visitors because their provider still remembers the old address. A low TTL turns that waiting time into a matter of minutes.

3. Transfer files and database

Copy your WordPress files to the new host and import your database. Then adjust wp-config.php with the correct database name, user and password for the new environment. Do not forget your media: the wp-content/uploads folder holds all your images and documents and is often the heaviest part. After copying, check that the file permissions are correct, otherwise you will get error messages or missing images.

4. Replace URLs safely in the database

If you change domain, your old URLs are still everywhere in the database. The problem: WordPress stores many settings as serialised data, in which the length of a piece of text is stored alongside it. A raw search-and-replace through SQL breaks that structure and can wreck widgets, page builders or settings. So use a serialisation-safe method, such as the search-replace command in WP-CLI or a reliable migration or search-and-replace plugin. Always make a backup first and preferably run a test round.

5. Testing on a hidden address

View the new site through your hosts file or a test domain, while the old site stays live. Walk through your important pages, test your contact forms, check your menus, internal links and mobile display. Click around until you are sure nothing is broken. This is the moment to find problems, not when visitors are already on the site.

6. Switch the DNS and keep the old host

Only now do you point the DNS to the new server. Thanks to the low TTL, the transition is fast. Keep your old host active for another 7 to 14 days as a safety net, so you can switch back if something unexpectedly goes wrong and so visitors with an outdated DNS cache still see a working site. After a few days you can set the TTL back to normal.

Database and media: where things often go wrong

Most failed WordPress migrations come unstuck on the database and the media, not on the files. Serialised data is the biggest pitfall: always replace URLs with a safe tool. A second classic is an incomplete media transfer, where large uploads folders break off halfway and your site ends up full of broken images. After the migration, spot-check that your images load.

Also watch out for references to external services. Tracking scripts, email connections, payment or CRM integrations and API keys can be tied to a domain or server. Go through them so your forms and measurements keep working. And after the switch, keep an eye on your Core Web Vitals: a new host is often exactly the opportunity to gain loading speed, provided the configuration is right.

Migration plugin or manual move?

For most standard sites a migration plugin is the fastest and safest route, because such a plugin carries serialised data across automatically and correctly. Tools like All-in-One WP Migration, Duplicator and WP Migrate package files and database into a single bundle and set the URLs right on import. Do bear in mind that the free versions often have a practical upper limit on file size, which partly depends on your host’s PHP settings. For large sites you sometimes need a paid extension or a manual approach.

Moving manually, with WP-CLI and a direct database export, gives you more control and suits heavy or complex sites with a lot of custom work. It does require technical knowledge and leaves less room for mistakes. The right choice depends on the size of your site, your technical comfort level and how much custom work is in it. If you are in doubt, a test migration on a staging environment is the safest way to see which route fits your site. For a bigger rebuild it is also worth considering pairing the migration with a website redesign.

The short summary

Migrating WordPress without downtime is above all a matter of sequence and preparation. Build the new environment completely first, lower your DNS TTL in advance, replace URLs with a serialisation-safe tool, test everything on a hidden address and only then switch the DNS. Keep your old host running a while longer as a safety net. If you are also switching domain, do not forget that the technical move is only half the job: you also need a redirect plan to protect your rankings.

We are a small, senior B2B team that builds and moves sites with a focus on what counts: a site that keeps running and keeps bringing in leads. If your WordPress migration spans multiple domains, integrations or a redesign at the same time, we will look at the safest path together. Take a look at our approach as a web design agency or schedule a conversation right away.

Get in touch with us

Frequently asked questions about WordPress migration

How long does a WordPress migration take?

The technical transfer of a standard site is often done in a few hours. The preparation, the testing and the DNS propagation together take more time, typically one to several days. Plan generously, because rushing is exactly where mistakes come from.

Will I lose my data during a WordPress migration?

Not if you make a full backup of files and database beforehand and keep your old host running for a few more days. With that safety net you can always switch back. Data loss occurs almost exclusively in moves made without a backup.

Will I have downtime when switching hosting?

No, provided you build and test the new site fully before you switch the DNS. Because the old address stays live until the new one is ready, visitors experience no interruption. Downtime only occurs if you redirect the DNS too early.

Should I use a plugin or migrate manually?

For most sites a migration plugin is faster and safer, because it carries serialised data across correctly. Large or complex sites with a lot of custom work are sometimes better off with a manual approach via WP-CLI. A test migration will show what suits your site.