Quick answer: Copy the WordPress files and database to the new server while the old site keeps running, test the copy with a hosts-file override, lower DNS TTL in advance, then do a final content sync and switch DNS during a quiet window. Visitors keep hitting the old server until DNS moves, so the site never appears offline.
Overview
Zero-downtime WordPress migration relies on one idea: the old site stays live and untouched while you build and verify its twin on the new server. Only the last few minutes — the final delta sync and DNS switch — need care. For the full WordPress-specific transfer steps see migrating WordPress to Cloud2Y VPS; this article focuses on doing it without visible interruption.
Before you start
- The new server fully prepared and the site copy already working on it.
- DNS TTL lowered to 300 seconds at least a day ahead.
- A quiet traffic window identified (check your analytics for the daily low point).
Step-by-step guide
- Initial copy: transfer wp-content, core files and a database dump to the new server; get the site rendering there.
- Verify via hosts file: point your machine at the new IP and click through pages, forms, admin and checkout if any (how to test).
- Freeze content briefly: pause publishing and plugin updates for the cutover window; for comment-heavy sites enable a short read-only notice.
- Final delta: rsync changed uploads and re-import the database (or just the changed tables) — minutes, not hours.
- Switch DNS and immediately test the live domain from a network that resolves the new IP.
- Watch both servers' logs: traffic drains from old to new as DNS propagates; keep the old server running for at least a few days.
Common issues
- Content written after the copy: anything posted between the last sync and the switch is lost unless the final delta catches it — freeze writes or sync again.
- Mixed caches: flush WordPress and server caches on the new host after cutover; stale URLs cause odd redirects.
- SSL not ready: issue the certificate on the new server before the switch so HTTPS never breaks.
When to contact support
High-traffic or e-commerce site where minutes matter? Request an assisted migration — we schedule the cutover with you and keep engineers on hand during the window.
Frequently asked questions
How can the site stay online while it moves?
Because two copies run in parallel: visitors keep using the old server while you build and test the new one, and DNS only moves traffic once the copy is proven to work.
What is the content freeze and how long does it last?
A short window, usually minutes, where you pause publishing and updates so the final file and database sync captures a stable state before the DNS switch.
When can I turn off the old WordPress server?
After several days of clean operation on the new server. Cached DNS keeps sending some visitors to the old IP for a while, and the old copy is your instant rollback.
Related articles
- How to migrate WooCommerce without losing orders
- How to avoid downtime during migration
- How to migrate WordPress to Cloud2Y VPS
- How to test a website before the DNS switch
Ready to move? Order a VPS at Cloud2Y →
