How to Migrate a WordPress Website Without Downtime
Moving a WordPress site to a new host should be invisible to your customers. No error pages, no lost form submissions, no orders stuck between two servers. To migrate WordPress
7 minute read
Moving a WordPress site to a new host should be invisible to your customers. No error pages, no lost form submissions, no orders stuck between two servers. To migrate WordPress without downtime, you need more than a migration plugin: you need a sequence that keeps the old site serving visitors while the new one is built, tested and switched on in a controlled moment.
We handle hosting moves as part of our web design and maintenance work, and the method below is the one we use for inquiry-led sites, WooCommerce stores and membership platforms. It focuses on the technical cutover: where downtime actually comes from and how to remove each cause.
Where downtime really comes from
Most migrations that “go down” are not caused by the copy itself. They come from a handful of predictable gaps:
- DNS caching: some visitors reach the new server while others still reach the old one, sometimes for hours.
- Content drift: orders, form entries, comments or new members arrive on the old site after the copy was taken, and are lost.
- SSL gaps: the new server has no valid certificate at the moment traffic arrives, so browsers show a security warning.
- Configuration differences: a different PHP version, missing extension or memory limit breaks a plugin on the new host.
- Hard-coded references: old server paths or URLs inside the database or theme files.
- Email and integrations: SMTP settings, webhooks, payment callbacks or API allowlists still pointing at the old server’s IP address.
To migrate WordPress without downtime, your plan must answer each of these before the switch happens.
Prepare both environments
Match the new server to the old
Record the current PHP version, database version, PHP extensions, memory limit, upload limit and any server rules for redirects or security headers. Set up the new environment to match, or deliberately test any upgrade in advance. A migration is not the moment to discover that a plugin fails on a newer PHP version.
Lower the DNS TTL early
The time to live on your DNS records controls how long resolvers cache them. At least a day before the move, reduce the TTL on the main A record and the www record to a few minutes. When you later change the IP address, most visitors will follow within minutes instead of hours.
Take stock of everything connected to the site
List payment gateways, CRM connections, form integrations, WhatsApp or chat tools, SMTP services, cron jobs, CDN settings and any third-party service that allowlists your server IP. Each one needs checking after the move, and some need updating before it.
Copy the site and test it privately
Copy the files and database to the new server using your preferred method: a migration plugin for smaller sites, or a direct file sync and database export for larger ones. Keep the domain name the same so no search and replace is needed on URLs.
Then test the new copy while the public still uses the old server. The simplest way is to edit the hosts file on your own computer so that your domain points to the new server’s IP address. Your browser will load the new site under the real domain while everyone else sees the old one. Check:
- Every key template: home, services, product, blog, contact and landing pages.
- Forms, including the email notification and CRM entry they should create.
- Search, filters, logins and member areas.
- Cart and checkout in the payment gateway’s test mode, where possible.
- The Arabic version and right-to-left layouts on bilingual sites.
- Server error logs for warnings the front end does not show.
Handle new data during the move
This is the step that separates a smooth move from a painful one. How you handle it depends on how often your site writes data.
| Type of site | Data risk | Approach |
|---|---|---|
| Brochure or corporate site | Low: occasional form entries | Freeze content edits, route form entries to email or CRM as well as the database, then cut over at any quiet hour |
| Blog or content site | Low to medium: comments and editorial changes | Pause publishing and comments for the cutover window, then resync the database immediately before the switch |
| WooCommerce store | High: orders, stock and customer accounts | Run a final database sync at a low-traffic hour and place the store in a short read-only state, or migrate new orders across after the switch |
| Membership or LMS site | High: sign-ups, renewals and progress | Pause sign-ups briefly, run a final sync and confirm payment webhooks point to the new server |
For busy stores, a few minutes of “checkout temporarily paused” during the final sync is far better than lost orders. Pick the quietest hour from your analytics. For many UAE audiences, that is very early morning, though Ramadan shifts browsing patterns later into the night.
Secure SSL before traffic arrives
Certificates issued through HTTP validation need traffic to reach the new server first, which creates a short window with a certificate warning. Avoid it by using one of these approaches:
- Issue the certificate on the new server using DNS validation before the switch.
- Install a copy of your existing certificate on the new server.
- Use a CDN or proxy that terminates SSL at the edge, so the switch happens behind it.
If your site already sits behind a CDN, the whole move can be as simple as changing the origin address in the CDN settings, which takes effect almost immediately.
The cutover: how to migrate WordPress without downtime
With preparation done, the switch itself is short. A reliable order that we follow on every move:
- Announce the freeze internally: no content edits, no plugin changes.
- Pause writes where needed: comments, checkout or sign-ups.
- Run the final database sync, and files sync if uploads changed.
- Confirm the new site one last time through the hosts file.
- Update DNS records, or the origin in your CDN.
- Monitor traffic arriving on the new server and watch error logs.
- Reopen writes and send a test order, form and sign-up.
- Keep the old server running and untouched for at least several days.
Keep a rollback plan ready
Zero downtime also means being able to reverse quickly. Before the switch, agree what would trigger a rollback, such as payment failures or a critical plugin error, and who makes the call. Because the old server stays live and the DNS TTL is short, rolling back is a single DNS change. Any orders or entries created on the new server during that window must then be copied back, so note the exact switch time.
After the move settles, restore the DNS TTL to a normal value, update integrations that referenced the old IP, confirm backups are running on the new host and cancel the old hosting only when you have a full backup stored safely elsewhere.
Frequently asked questions
Is it really possible to migrate WordPress without downtime?
For most sites, yes. The old server keeps serving visitors while the new one is built and tested privately, and a short DNS TTL makes the switch quick. Sites that take orders or sign-ups may need a brief pause on checkout or registration during the final sync, but visitors can still browse, and nothing is lost.
How long does DNS propagation take after a move?
It depends on the TTL that was set before the change. If you lowered it to a few minutes a day or two in advance, most visitors reach the new server within minutes. A small number of networks ignore short TTLs, which is why the old server should stay live and unchanged for several days after the switch.
Will moving hosts affect my search rankings?
A like-for-like move on the same domain, with the same URLs and content, should not harm rankings by itself. Problems appear when pages break, the site slows down or long outages occur. Keep URLs identical, check that the robots settings on the new server allow indexing and watch Search Console for crawl errors in the weeks after the move.
Should I use a migration plugin or move the site manually?
Plugins work well for small and medium sites with standard hosting. Large sites, stores with big databases or hosts that limit upload sizes are often better moved with direct file sync and database tools, which are faster and easier to repeat for the final sync. Either way, the testing and cutover steps matter more than the copy method.
A move your customers never notice
A calm migration is mostly preparation: matched environments, a low TTL, private testing, a clear plan for new data, SSL ready in advance and a rollback you hope not to use. Done in that order, the switch becomes a quiet few minutes rather than a risky evening. If you are planning a hosting move and want it handled without disruption to inquiries or sales, we would be happy to talk it through.