On this page
Most WordPress migrations do not fail on moving day. They fail a week later, when someone notices that contact form emails stopped, half the images point to the old server, or Google is indexing a staging URL.
This field guide walks through a migration in the order that keeps a site online the whole time. It works for moving to a new host, a new domain, or both.
Quick answer: To migrate WordPress without downtime, copy the site to the new host while the old one stays live, test it privately using your computer’s hosts file, lower your DNS TTL a day ahead, then switch DNS. Keep the old host running for at least 48 hours, and freeze content or orders during the final sync.
What “zero downtime” really means
Downtime happens when visitors reach a server that is not ready. If both the old and new servers can serve the site correctly during the switch, visitors never notice which one they hit.
So the whole plan comes down to one rule. Never switch traffic until the new copy is complete and tested, and never shut down the old copy until traffic has fully moved.
Before you start: a short inventory
Write these down first. Most migration surprises come from something nobody listed.
- WordPress, PHP and database versions on the old host.
- Total size of files and database.
- Where email is handled (your host, Google Workspace, Zoho or another service).
- DNS records: A, CNAME, MX, TXT (including SPF and DKIM).
- Scheduled tasks, server-level caching, CDN and firewall settings.
- Custom code outside the theme and plugins, such as rules in
.htaccessorwp-config.php.
Step 1: Take a full backup
Back up both files and database, and store the copy somewhere other than the old server. Test that the backup opens. A backup you cannot restore does not count.
Step 2: Lower your DNS TTL a day ahead
TTL (time to live) tells networks how long to cache your DNS records. If it is set to a day, some visitors could keep reaching the old server for up to a day after you switch.
At least 24 hours before moving, lower the TTL on your A record (and any record you will change) to around 300 seconds. When you switch later, the change spreads in minutes rather than hours.
Step 3: Set up the new host
Create the site on the new host with the same PHP version as the old one, or a newer one your plugins support. Install an SSL certificate if the host lets you issue one before DNS points there. Some hosts can only issue it after the switch, so check this now.

Step 4: Copy the site
Pick the method that matches the site’s size and your comfort level.
| Method | Good for | Watch out for |
|---|---|---|
| Your new host’s migration tool or service | Most small and medium sites | Check what it skips, such as email or custom server rules |
| A migration plugin | Sites up to a few gigabytes | Upload limits and timeouts on large sites |
| Manual copy (SFTP files, database export and import) | Large or complex sites | Needs a careful search and replace on URLs |
If you are also changing the domain, replace the old URL in the database with a tool that understands serialised data. On the command line, WP-CLI does this safely. Run it with --dry-run first:
wp search-replace 'https://old-domain.com' 'https://new-domain.com' --all-tables --dry-run
Step 5: Test privately with your hosts file
Your computer’s hosts file lets you point your own domain at the new server, while everyone else still sees the old one. Add a line with the new server’s IP and your domain:
203.0.113.10 example.com www.example.com
On Windows, the file is at C:\Windows\System32\drivers\etc\hosts. On macOS and Linux, it is /etc/hosts. Replace the example IP with your new server’s address, and remove the line when testing is done.
Pro tip: On macOS, if the change does not show up, flush the DNS cache with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Windows, run ipconfig /flushdns.
Now browse the site as a visitor would. You should see the new server’s copy at your real domain.
Step 6: Run a test checklist
- Home page, key landing pages and a few old blog posts load correctly.
- Images and downloads load from the new server, not the old one.
- Contact forms submit and the emails arrive.
- Logins, the admin area and the editor work.
- Checkout and payment work, in test mode if your gateway allows it.
- Permalinks work. If posts show 404 errors, open Settings, then Permalinks, and click
Save Changesonce to refresh the rules. - Caching and security plugins are configured for the new server.
Step 7: Freeze changes and do a final sync
Anything that changes on the old site after you copied it will be lost unless you sync it again. That includes new posts, comments, form entries and, most importantly, WooCommerce orders.
For a blog, pause publishing for a few hours. For a store, pick a quiet hour, put the store into maintenance mode briefly, copy the latest database, then switch DNS straight away. The pause is usually short, and it is the only reliable way to avoid losing orders.
Step 8: Switch DNS
Update your A record (or nameservers) to the new host. With a low TTL, most visitors move within minutes. Some networks ignore TTL, so a few visitors may reach the old server for longer, which is why the old host must stay live.
Check MX and email-related TXT records carefully. Moving a website should never break email, but it often does when records are copied by hand.
Step 9: Keep the old host for at least 48 hours
Leave the old server running and unchanged for two days or more. Then confirm nothing new arrived there (orders, form entries, comments) before cancelling the old plan.
Step 10: Post-migration checks
- Issue or confirm the SSL certificate, and check that every page loads over HTTPS.
- If the domain changed, add 301 redirects from every old URL to its new one, and update the address in Google Search Console.
- Submit your sitemap again in Search Console and watch the coverage report for a couple of weeks.
- Confirm scheduled tasks run, such as scheduled posts, backups and subscription renewals.
- Set the DNS TTL back to a normal value, such as an hour.
- Run Tools, then Site Health, on the new host. My quick WordPress tips post covers what to look for.
Common mistakes
- Switching DNS before testing, then fixing problems live.
- Forgetting email DNS records, so mail stops quietly.
- Losing WooCommerce orders placed between the copy and the switch.
- Leaving staging sites indexable, so Google finds a duplicate copy.
- Cancelling the old host the same day.
A careful migration is very doable on your own for a small site. For a busy store, a site with years of SEO history, or a move that also changes theme or domain, the cost of a mistake is higher.
That is the work I handle through HelloSatya’s WordPress Migration service, with a staging build, a URL map and a rollback plan ready before anything goes live.
Frequently asked questions
Can I migrate WordPress without any downtime?
Yes. Copy the site to the new host while the old one stays live, test it using your hosts file, then switch DNS with a low TTL. Because both servers can serve the site during the switch, visitors see no gap in service.
How long does DNS propagation take?
If you lower your TTL to around 300 seconds a day ahead, most visitors reach the new server within minutes of the switch. With a long TTL, it can take up to a day or more, because networks keep the old record cached until the TTL expires.
Will migrating WordPress hurt my SEO?
Not if URLs stay the same and the site stays online. When the domain or URL structure changes, add a 301 redirect from every old URL, update Google Search Console and resubmit your sitemap to protect rankings.
How do I avoid losing WooCommerce orders during a migration?
Do the final database copy during a quiet hour with the store briefly in maintenance mode, then switch DNS immediately. Afterwards, check the old site for any orders placed during the switch before you cancel the old host.
Should I use a plugin or migrate manually?
A migration plugin or your new host’s migration service suits most small and medium sites. Large sites, or moves with custom server rules, are safer done manually with file transfer, a database export and WP-CLI.
Planning a move soon? Start with the inventory list above. It is the step most people skip, and the one that prevents most surprises.
WooCommerceWordPressWordPress migration

Written by
Satyam Vishwakarma founded HelloSatya and does the client work himself. He is a WordPress 6.5 core contributor, a WordPress Photo Directory moderator, the developer of two plugins on WordPress.org and a co-organiser of WordCamp Kolhapur 2026.

Leave a comment