You can move a WordPress site to new hosting with no downtime by building a full copy on the new host first, testing that copy on a temporary address, and only pointing your domain at it once the copy is proven. Your live site keeps serving visitors the entire time, and the switch itself is near-instant — so there is no “site down for maintenance” window at all.
The fear that stops most people from moving hosts is the maintenance window: the hours when the site is offline mid-move and customers hit an error. That window is avoidable. The trick is to run both hosts side by side during the transition, so the old site never stops working until the new one has taken over cleanly. Here is how the no-downtime approach works, step by step.
The parallel-migration approach
1. Build a complete copy on the new host
First, create a full working copy of your site on the new hosting while the original keeps running untouched. This is a staging copy — the whole site, files and database, rebuilt on the new server but not yet connected to your public web address (Pantheon). Because it is separate, nothing you do to it can affect the site your visitors are using.
2. Test the copy on a temporary address
Before anything switches, open the copy on a temporary link and check it end to end — pages, images, forms, checkout, logins (WP Swift). This is the step that removes the risk. You are proving the new site works in full before a single visitor is sent to it, so there are no surprises after the switch.
3. Prepare the switch in advance
A domain change takes a little while to spread across the internet, and you can shorten that wait by lowering your domain’s “refresh interval” a day or two ahead of the move. With it lowered, most visitors reach the new host within roughly half an hour to an hour of the switch rather than waiting much longer (Hosting’s House). It is a quiet preparation step that makes the eventual cutover feel instant.
4. Run final checks, then cut over
Right before switching, confirm the essentials on the new copy: the security certificate is active, contact and checkout emails send, redirects work, and scheduled tasks run. With those green, you point the domain at the new host. Visitors move across smoothly because the destination is already tested and ready.
5. Keep the old host running for a day or two
Do not cancel the old hosting the moment you switch. Keep both live for about 48 hours while the change finishes spreading everywhere, so any visitor still reaching the old host sees a fully working site, not an error (WP Swift). Once everything resolves to the new host, you can retire the old one.
Why this beats a “quick” copy-and-switch
The tempting shortcut is to copy the site and flip the domain in one go. It usually causes exactly the downtime you were trying to avoid, because any problem — a broken link, a missing certificate, a form that no longer sends — is now live, on your real address, in front of real customers. The parallel approach front-loads all the checking onto a copy nobody can see, so by the time the public switch happens, the outcome is already known.
This is the approach a good managed provider takes on your behalf. At Groundcraft, migration is free and done in parallel: your live site keeps running while we rebuild and test the copy, and we only cut over when you say it is ready. You approve the switch; you are never surprised by it.
Frequently asked questions
Will my site really stay online during the move?
Yes. Your existing site keeps serving visitors from the old host the whole time the new copy is being built and tested. The only change your visitors experience is the near-instant switch at the end, once the new site is proven to work.
How long does a no-downtime migration take?
The build and testing can take anywhere from an hour to a day depending on the site’s size, and then the domain change spreads over the following hours. None of that is downtime — it all happens while the current site stays live and the new one waits in the wings.
What is the temporary address for?
It lets you open and test the migrated copy without touching your real web address. You can click through every page, submit forms, and check checkout on the new host, confirming everything works before any visitor is sent there.
Do I need to tell customers the site will be down?
No, because it will not be. That is the point of the parallel approach — there is no maintenance window to warn anyone about. The switch is designed to be invisible to the people using your site.
What if something is wrong after the switch?
Because the old host stays live for a day or two, you have a safety net: if an issue appears, you can point the domain back while it is fixed. In a well-tested parallel migration this is rarely needed, since the copy was proven before the switch.
If you would like your site moved with no downtime and nothing to do on your end, see how free migration works.