Skip to content
HyperDAF editorialMigration Guides

Migrate WordPress to a New Host With Zero Downtime

Learn how to migrate WordPress to new host servers with zero downtime. A proven step-by-step checklist covering backups, DNS, testing, and rollback plans.

Migration GuidesEditor-curated guide
13 min8 sectionsIntermediate
Before you beginWhat this guide gives you
8Focused sections13Minutes to finishIntermediateExperience level91Article views
Start reading
Table of contents8

The client’s online store went dark on a Friday afternoon. Not because of hackers, not because of traffic — because his previous developer had “migrated” the site to a cheaper host that morning by simply changing the DNS and hoping for the best. For six hours, half the world saw a broken site and the other half saw nothing at all. By the time I got the call, he had lost a full day of sales and most of his patience.

I am Ryan Clarke, and I have migrated well over a hundred WordPress sites between hosts. Big stores, tiny blogs, membership sites with thousands of users. The Friday-afternoon disaster taught me the lesson that shapes every migration I do now: moving a WordPress site is not a single action. It is a sequence — and the order of that sequence is what keeps your site online the whole time.

If you are thinking about switching hosts, you probably feel the fear. What if the site goes down? What if I lose orders, or emails, or Google rankings? In this guide, I will walk you through the exact four-phase process I use on every migration — the same process that has moved sites with zero minutes of downtime, every single time.

Whether you are moving your first blog or your fiftieth client store, this is the method I wish someone had handed me before that Friday afternoon.

Illustration of a website moving between two servers with a safety check

Here is what this guide covers:

  • Why WordPress Migrations Go Wrong
  • Phase 1: Prepare Before You Touch Anything
  • Phase 2: Move the Site to the New Host
  • Phase 3: Test Everything Before Anyone Notices
  • Phase 4: Switch the DNS and Monitor
  • Your Rollback Plan (Hope for the Best, Prepare for the Worst)
  • Frequently Asked Questions
  • Final Thoughts

Ready? Let us move your site without anyone noticing it moved.

Why WordPress Migrations Go Wrong

Almost every failed migration I have seen failed for the same reason: the person treated DNS like a light switch. They pointed the domain at the new server and assumed the site would simply appear there. But DNS is not instant — it spreads across the internet over hours — and a WordPress site is not a single file. It is thousands of files plus a database plus email plus cached everything, all of which must arrive intact and in the right order.

The classic mistakes are painfully consistent. No complete backup before starting, so there is nothing to restore when things break. Migrating on a Friday (never migrate on a Friday — you want support teams awake and alert if you need them). Changing DNS before testing the site on the new host. Forgetting about email — the site moves but the client’s inbox stays pointed at the old server and vanishes. And the silent killer: hardcoded URLs in the database that still point to the old setup.

Here is the good news: every one of these is preventable with a process. Migration is not luck. It is preparation plus testing plus patience, in that order. The four phases below are the entire system. Follow them exactly and your visitors will never know anything happened.

Phase 1: Prepare Before You Touch Anything

I spend more time preparing than migrating, and that ratio is the whole secret. A rushed migration is a broken migration. Before anything moves, get these five things in order.

First, take a complete backup of everything — files plus database — and store it somewhere that is NOT either host. Your laptop, cloud storage, anywhere independent. This backup is your time machine. If every phase below goes wrong simultaneously, this file is what saves you. Verify the backup actually contains the database, not just the files; a file-only backup of WordPress is a beautiful, useless zip.

Second, set up the new hosting account completely before the site arrives. That means PHP version matched to what the site needs, SSL certificate ready, and a temporary URL or hosts-file trick so you can preview the site on the new server before DNS changes. Most good hosts give you a temporary preview address — if yours does not, you can edit your computer’s hosts file to point the domain at the new server IP just for your machine.

Third, gather every login: old hosting, new hosting, domain registrar, WordPress admin, email accounts, CDN, and anything else the site touches. Write them in one access sheet. I have watched migrations stall for two days because nobody knew who controlled the domain registrar.

Illustration of a migration preparation checklist beside a database

Fourth, audit the site you are about to move. Update WordPress core, themes, and plugins on the OLD host first, and clean out what you do not need — unused themes, dead plugins, spam comments, bloated media. Migrating clutter is like paying movers to transport garbage. A lean site moves faster and breaks less.

Fifth, pick your migration day: Tuesday, Wednesday, or Thursday morning, when traffic is lowest and every support team is fully staffed. Warn the client (or yourself) that no content changes should happen during the migration window — no new posts, no new orders processed on the old site after the copy is taken, or those changes get left behind.

Phase 2: Move the Site to the New Host

Now the actual move. You have two reliable methods, and I want you to understand both so you can choose with confidence.

The manual method gives you full control: export the database from the old host, download all files, upload them to the new host, create a fresh database there, import the data, and update the configuration file with the new database credentials. It sounds technical, but it is just six careful steps, and it teaches you exactly how WordPress fits together. I still do manual migrations for complex sites because nothing hides from you — you see every piece.

The guided method uses your new host’s migration service. Many quality hosts will move your site for free when you sign up — you give them the old logins and they handle the transfer. This is genuinely excellent for standard sites, and I recommend it to anyone who finds the manual method intimidating. The catch: you must still do Phase 1 (backup) and Phase 3 (testing) yourself. A host’s migration team moves files; they do not verify your business works.

Whichever method you choose, one rule is absolute: do NOT touch the DNS yet. The site now lives in two places — old host serving visitors, new host waiting for your inspection. That overlap is your safety net, and it is what makes zero downtime possible. If anything looks wrong on the new copy, visitors are still happily using the old one.

A note on quality while you are here: a migration is the perfect moment to leave bloat behind. Bloated themes and sloppy plugins are the number one reason sites crawl after a move. This obsession with clean code is something I care about deeply — it is why at HyperDAF, our own development team builds every WordPress theme, plugin, and tool from scratch, with no outsourced code and no bloat. Our marketplace of our team’s own WordPress products launches very soon at hyperdaf.com, and clean performance is the standard everything is held to.

Phase 3: Test Everything Before Anyone Notices

This is the phase most people skip, and skipping it is how Friday-afternoon disasters happen. You now have a full copy of the site on the new host, invisible to the world. Test it like a suspicious detective before a single visitor arrives.

Start with the preview method: use the host’s temporary URL or your edited hosts file to browse the new copy as if you were a visitor. Click through the homepage, the key pages, the checkout or contact flow — whatever the site exists to do. Submit a test form. Complete a test order if it is a store. Log into the admin and publish a test post, then delete it.

Then check the invisible stuff. Are images loading from the right place? Do internal links work? Is the SSL certificate valid with no mixed-content warnings (that little padlock must be clean)? Is email sending — order confirmations, contact form notifications, password resets? Email breaks silently in migrations more than anything else, so send test messages to yourself and confirm they arrive.

Illustration of DNS switching with a globe and network arrows

Check speed too. Run the new copy through PageSpeed Insights — Google’s free speed testing tool — and compare against the old host’s numbers. A migration should never make a site slower; if it did, something is misconfigured on the new server (usually PHP version or caching), and now is the time to fix it, not after launch.

Only when every test passes do you move to Phase 4. If anything fails, fix it on the new copy while the old site keeps serving visitors. There is no pressure, no downtime, no panic — that is the entire point of this sequence.

Phase 4: Switch the DNS and Monitor

Now — and only now — you change the DNS. Log into the domain registrar and point the domain’s A record (and www) at the new host’s IP address. Lower the TTL (time-to-live) on the DNS records 24 hours BEFORE you make the change — this tells the internet to check for updates frequently, so the switch spreads in minutes instead of hours. If you forgot to lower it, the change still works; it just takes longer to reach everyone.

Here is what zero downtime actually looks like: during DNS propagation, some visitors reach the old server and some reach the new one. Both serve the identical, tested site. Nobody sees an error. Nobody notices anything. Within a few hours (usually much less with a lowered TTL), the whole world is on the new host.

Monitor for 48 hours. Watch the new host’s traffic logs to confirm visitors are arriving. Check that forms, orders, and emails work in the live environment. Keep the old hosting account active for at least a week — do not cancel it the same day. I keep old accounts for 30 days on client projects; the cost is trivial compared to the insurance.

After a week of clean operation, cancel the old host and celebrate. Update your records: the access sheet now lists the new host as primary. And take a fresh backup on the new home — your migration is only truly finished when the new site has its own verified backup. If you want a refresher on keeping those backups safe, read our guide on why you should stop storing WordPress backups on your own server.

Your Rollback Plan (Hope for the Best, Prepare for the Worst)

A rollback plan is not pessimism. It is professionalism. Write it before Phase 4, in one paragraph: “If the new site fails after DNS switch, revert the A record to the old IP (old IP: X), which restores the old site within the TTL window. Old hosting remains active until [date].”

Because you lowered the TTL and kept the old host alive, rollback is a two-minute DNS change, not a rebuild. In over a hundred migrations, I have needed rollback twice — both times for DNS issues at the registrar level, both fixed in under ten minutes, both invisible to visitors because the old site was still there.

The rule: never delete, cancel, or overwrite the old anything until the new everything has run cleanly for a week. Backups, old hosting, old DNS values written down — these cost almost nothing and buy total safety.

Illustration of a rollback safety plan protecting a website

Frequently Asked Questions

How long does a WordPress migration take? Preparation takes a few hours spread over a day or two. The actual file and database move takes 30 minutes to a few hours depending on site size. DNS propagation takes minutes to a few hours with a lowered TTL. Plan a calm morning, not a rushed evening.

Will my Google rankings drop after migration? Not if the URLs stay identical — and they should. Google does not care which server hosts your content as long as every URL works and the site stays fast. Keep the domain, keep the URL structure, keep the speed, and rankings continue undisturbed. For domain changes (a different kind of migration), extra SEO steps apply — and if you are weighing backup strategies for the move, see our comparison of manual backups vs backup plugins.

What about emails during the migration? Email is the most commonly broken piece. Decide BEFORE migrating where email lives: with the old host, the new host, or a dedicated email service. Update MX records deliberately as part of Phase 4, and test sending and receiving on the new setup. Never assume email “just moves” with the site.

Can I migrate a WooCommerce store with zero downtime? Yes, with one extra rule: freeze orders during the final copy. Put the store in maintenance mode for the 15–30 minutes it takes to take the final database copy and move it, so no order lands on the old database after you have copied it. Schedule this in the lowest-traffic hour and announce it in advance.

Should I migrate on the weekend when traffic is low? Traffic timing matters less than support availability. Migrate on a weekday morning when every support team — old host, new host, registrar — is fully staffed. A Tuesday with slightly more traffic beats a Sunday with nobody answering tickets.

Final Thoughts

That Friday-afternoon disaster never fully leaves me. Not because of the lost sales — the client recovered — but because it was so preventable. Nobody needed to suffer. The site could have been copied, tested, and switched over a calm Tuesday morning with nobody noticing a thing. Every migration since has been my apology for that Friday, systematized into four phases.

Here is what I want you to carry forward: migration is not a leap of faith. It is prepare, move, test, switch — in that order, with a backup and a rollback plan underneath it all. Follow the sequence and your visitors will never know anything happened. That is what zero downtime really means: not heroics, just process.

Have a migration story — smooth or terrifying? Share it in the comments below. The best lessons in this work come from each other’s war stories. Related guides: The Safe WordPress Update Checklist, Backuply Vulnerability (CVE-2026-93953), How to Speed Up WordPress in 2026, How to Install WordPress Plugins Safely, 10 Checks to Run Before Activating Any Plugin.

P.S. — If you like the idea of WordPress products built clean from the ground up by a real expert team, keep an eye on hyperdaf.com. Our marketplace of our own team’s themes, plugins, and tools is launching very soon.

Written by

Ryan Clarke

Ryan runs WordPress infrastructure for high-traffic stores. His 9 years in hosting and DevOps shape his guides on servers, staging workflows, backups, and deployment.

7 published articles
View all articles

Related articles

View all articles

3 comments

Join the discussion

Your email address will not be published. Required fields are marked *

Keep comments relevant and respectful.