How to Migrate WordPress Without Downtime: A Practical Guide

Most guides on how to migrate WordPress tell you how to copy a site. They skip the part that actually matters to a business: doing it without your site going dark in the middle. We’ve run hundreds of WordPress migrations between hosts, and the difference between a clean move and a stressful one is almost never the file transfer. It’s the order of operations around DNS, testing, and the URL swap. Get that order right and visitors never see a hiccup. Get it wrong and you’ve got an hour of downtime and a search-replace mess.

This is the zero-downtime sequence we use on real client moves. It works whether you migrate by plugin or by hand.

Why “without downtime” is the part everyone skips

When you move a site to a new host, there’s a window where two things are true at once: your new server has the site, but your domain still points at the old one. If you change your domain’s DNS too early, visitors hit a half-finished site. If the old host is gone before DNS updates everywhere, visitors hit nothing.

The fix is simple once you see it: build and fully test the site on the new host first, keep the old site live the entire time, and only flip DNS once the new one is verified. Then leave the old host running for another day or two while DNS propagates. No visitor should ever land on a broken page.

Step 0: lower your DNS TTL a day ahead

This is the single move that separates people who’ve done this before from people who haven’t. DNS records have a TTL (time to live) that tells the internet how long to cache them, often 24 or 48 hours. The day before you migrate, log in to wherever your DNS lives and drop the TTL on your A record to 300 seconds.

Why bother? When you finally flip DNS to the new host, a low TTL means the change propagates in minutes instead of up to two days. That shrinks the risky window to almost nothing. Set the TTL low now, do the rest of the work, then flip with confidence tomorrow.

How to migrate WordPress, step by step

1. Set up the new host and a clean WordPress

Get hosting at the destination and install WordPress there, empty for now. If you need a refresher, our guide on how to install WordPress covers it. Don’t point your domain at this host yet. You’ll work on it behind the scenes using its temporary address or a staging URL.

2. Copy the files and the database

You’re moving two things: the files (themes, plugins, uploads) and the database (posts, settings, users). With a migration plugin this is one export and one import. By hand, you download the wp-content folder over FTP and export the database as a SQL file from phpMyAdmin, then upload both to the new host. Either way, the goal is an exact copy living on the new server.

3. Search-replace the URLs (the trap that breaks sites)

Here’s where manual migrations go wrong. Your database is full of your old URL, and some of it is stored in serialized PHP data where a naive find-and-replace corrupts the data and breaks widgets and settings. Never run a plain SQL REPLACE on a WordPress database.

Use a serialization-safe tool instead. The WP-CLI command wp search-replace handles serialized data correctly, and the free Better Search Replace plugin does the same through a UI. If you’re staying on the same domain and only changing hosts, you may not need this step at all, which is one reason a same-domain move is the easiest kind.

4. Test the new site before anyone sees it

Don’t trust a migration you haven’t tested. Preview the new server using its temporary URL, or edit the hosts file on your own computer to point the domain at the new server’s IP just for you. Click through pages, submit a form, check images load, log in to wp-admin, and view the site on your phone. The rest of the world still sees the old site while you do this. Only move on when the new copy is genuinely correct.

5. Flip DNS and keep the old host alive

Now update your domain’s A record to the new server’s IP. Thanks to the low TTL you set yesterday, this propagates fast. As people’s DNS refreshes, traffic shifts to the new host. Crucially, leave the old hosting running for at least 48 hours. Anyone still on the cached old DNS keeps seeing a working site until they catch up. Once analytics show all traffic on the new server, you can cancel the old plan.

Plugin or manual migration?

For most sites, a migration plugin is the right call. Tools like Duplicator, All-in-One WP Migration, or UpdraftPlus handle the copy and the URL swap in a few clicks, and they get the serialized-data part right automatically. We reach for them on the majority of straightforward moves. Several of these double as your scheduled backup, so it is worth picking one you trust; we rank them in our best WordPress backup plugin comparison.

We go manual when a site is too large for a plugin’s upload limit, when it has custom database tables, or when a host blocks the plugin’s import. Manual gives full control and no size ceiling, at the cost of more steps and more ways to slip. If your site is a standard blog or brochure site, start with a plugin. If it’s a big store or a heavily customized build, manual or professional help is safer. The same logic applies when moving off another platform entirely, which we covered in our walkthrough on migrating from Wix to WordPress.

The mistakes that actually cause downtime

• Changing DNS before the new site is tested. Now everyone sees a broken site instead of just you.
• Cancelling the old host the moment DNS is changed. Cached visitors lose the site for hours.
• Running a plain find-and-replace on the database and corrupting serialized data.
• Forgetting to copy the uploads folder, so every image 404s after the move.
• Skipping the TTL change, then waiting two anxious days for DNS to catch up.

Want it migrated without the risk?

A small site on the same domain is a reasonable weekend project. A revenue-generating site, a big store, or a host-to-host move with a domain change is where a missed step costs real money. That’s exactly the work we do every week. Our WordPress migration service moves your site with zero downtime, handles the DNS and search-replace properly, and keeps a rollback ready in case anything looks off. You stay live the whole time.

Frequently asked questions

Can I migrate WordPress without any downtime?

Yes. Build and test the site on the new host first, lower your DNS TTL a day ahead, flip DNS only after testing, and keep the old host running for 48 hours afterward. Done in that order, visitors never see an interruption.

What is the easiest way to migrate a WordPress site?

A migration plugin like Duplicator or All-in-One WP Migration. It exports your whole site from the old host and imports it to the new one, handling the URL changes safely. Manual migration is for large or customized sites that outgrow a plugin.

Why is my site broken after migrating?

The usual suspects are a plain find-and-replace that corrupted serialized data, a missing uploads folder, or DNS that hasn’t propagated yet. Restore from your backup, then redo the URL swap with a serialization-safe tool like WP-CLI or Better Search Replace.

How long does a WordPress migration take?

The copy itself takes 15 to 60 minutes for an average site. The full zero-downtime process spans a day or two because you lower the TTL ahead of time and leave the old host running after the switch. The active work is short; the safety margin is the wait.