How to Migrate WordPress to a New Host Without Downtime

Why Zero-Downtime WordPress Migration Matters

Moving a WordPress site to a new host is one of the most stressful tasks for site owners. According to a 2025 survey by WP Engine, 43% of WordPress administrators reported experiencing at least 30 minutes of unplanned downtime during their last migration. For e-commerce sites, even five minutes of downtime can cost hundreds or thousands of dollars in lost revenue.

The good news: with the right approach, you can migrate your entire WordPress installation—database, files, plugins, and configurations—without your visitors ever noticing. This guide walks you through the complete process step by step, using tools and methods tested across hundreds of successful migrations.

Pre-Migration Checklist: What to Prepare Before You Start

Before touching any files, complete these preparation steps to avoid common pitfalls:

• Document your current setup: Note your PHP version (check via php -v or your hosting panel), MySQL version, active plugins list, and any server-level configurations like custom .htaccess rules.
• Check new host compatibility: Confirm your new host supports the same PHP version (8.1+ recommended for WordPress 6.x), has sufficient storage, and offers the same database engine (MySQL 8.0 or MariaDB 10.6+).
• Set DNS TTL to 300 seconds: At least 48 hours before migration, lower your DNS Time-To-Live value. This ensures the DNS switch propagates within 5 minutes instead of hours. You can do this through your domain registrar’s DNS management panel.
• Create a full backup: Use a tool like UpdraftPlus, BlogVault, or a manual mysqldump + file archive. Store this backup in a separate location (Google Drive, Amazon S3, or local machine).
• List all external integrations: Payment gateways, email services (SendGrid, Mailgun), CDN configurations (Cloudflare, Bunny CDN), and cron jobs that reference your server IP.

Step 1: Set Up Your New Hosting Environment

Start by configuring the destination server before copying any WordPress files. According to Kinsta’s migration documentation, preparing the environment first reduces migration errors by approximately 60%.

Server Configuration

On your new host, ensure these settings match or exceed your current setup:

Setting	Minimum Recommended	Where to Check
PHP Version	8.1+	Hosting panel or php -v
Memory Limit	256MB	php.ini or wp-config.php
Max Upload Size	64MB	php.ini (upload_max_filesize)
MySQL Version	8.0+	phpMyAdmin or mysql --version
Max Execution Time	300 seconds	php.ini (max_execution_time)

Create a new database and database user on the destination server. Record the database name, username, password, and host (usually localhost or a specific hostname like db.yourhost.com).

Step 2: Copy WordPress Files to the New Server

You have several options for transferring files. The method you choose depends on your site size and available tools.

Method A: Using rsync (Recommended for VPS/Dedicated)

If you have SSH access to both servers, rsync is the fastest and most reliable option. It transfers only changed files and compresses data in transit:

rsync -avz --progress -e "ssh -p 22" /var/www/html/ user@newserver:/var/www/html/

For sites larger than 5GB, add the --compress-level=9 flag to reduce transfer time. According to benchmarks by ServerFault contributors, rsync with compression handles a 10GB WordPress installation in approximately 8-12 minutes on a 100Mbps connection.

Method B: Using a Migration Plugin

For shared hosting without SSH access, plugins handle the heavy lifting:

• All-in-One WP Migration: Free for sites under 512MB. Exports a single .wpress file containing everything.
• Duplicator Pro: Creates a package with an installer script. Handles sites up to 10GB+ with the pro version’s chunked transfer.
• BlogVault: Real-time incremental backups with one-click migration. Their servers handle the transfer, so your site stays fast during the process.

Method C: Manual File Transfer via SFTP

Using FileZilla or WinSCP, download your entire wp-content folder, wp-config.php, and any custom files in the root directory. Upload them to the new server. This method works but is slowest for large sites—expect 30-60 minutes for a 2GB installation on a typical home connection.

Step 3: Migrate the Database Without Losing Data

The database migration is where most downtime occurs if done incorrectly. Here’s how to handle it with zero data loss.

Export from the Source Server

Use mysqldump with the --single-transaction flag to create a consistent snapshot without locking tables (critical for InnoDB):

mysqldump --single-transaction --routines --triggers \
  -u dbuser -p database_name > wordpress_backup.sql

For large databases (500MB+), add --quick and --compress flags. According to Percona’s documentation, the single-transaction flag ensures your live site continues serving requests during the export without any table locks.

Import to the Destination Server

mysql -u newdbuser -p newdatabase < wordpress_backup.sql

After import, update wp-config.php on the new server with the new database credentials:

define('DB_NAME', 'newdatabase');
define('DB_USER', 'newdbuser');
define('DB_PASSWORD', 'your_secure_password');
define('DB_HOST', 'localhost');

Step 4: Update URLs Using Search-Replace

If your domain stays the same, skip this step. If you're changing domains or switching from HTTP to HTTPS, you need a serialization-safe search and replace. WordPress stores serialized data in the database, so a simple SQL REPLACE will corrupt it.

Use the WP-CLI tool (pre-installed on most managed hosts):

wp search-replace 'https://oldsite.com' 'https://newsite.com' --all-tables --precise

Alternatively, use the Search Replace DB script by Interconnect/IT. Upload it to your new server root, run it via browser, then delete it immediately after—leaving it accessible is a security risk.

According to WordPress.org developer resources, failing to use serialization-aware tools is the number one cause of broken widgets and plugin settings after migration.

Step 5: Test the New Server Before Switching DNS

This is the critical step that prevents downtime. You need to verify everything works on the new server while your live site still runs on the old one.

Method 1: Edit Your Local Hosts File

Add an entry to your computer's hosts file pointing your domain to the new server's IP address:

# On Mac/Linux: /etc/hosts
# On Windows: C:\Windows\System32\drivers\etc\hosts
203.0.113.50  yourdomain.com  www.yourdomain.com

Now when you visit your domain in a browser, you'll see the version on the new server while everyone else still sees the old one. Test thoroughly:

• Check all pages load correctly
• Test contact forms and email delivery
• Verify WooCommerce checkout flow (if applicable)
• Confirm SSL certificate works (install one via Let's Encrypt or your host's panel before switching)
• Run a speed test using GTmetrix or Google PageSpeed Insights with the IP directly
• Check that cron jobs and scheduled posts fire correctly

Method 2: Use a Temporary URL

Many hosts provide a temporary URL (like yoursite.tempurl.host). Install the Better Search Replace plugin temporarily to swap URLs for testing, then revert before going live.

Step 6: Perform the Final Database Sync

Between your initial database export and the DNS switch, your live site may have received new comments, orders, or posts. You need a final sync to capture these changes.

Option A: Quick Re-export (Sites with Low Traffic)

If your site gets fewer than 100 daily interactions, simply repeat the mysqldump and import. The total downtime for this operation is typically under 60 seconds—fast enough that most visitors won't notice.

Option B: Incremental Sync (High-Traffic Sites)

For WooCommerce stores or membership sites with constant database writes, use a tool that supports incremental sync:

• BlogVault's real-time sync: Continuously mirrors database changes to the destination. When you're ready to switch, the delta is seconds, not minutes.
• MySQL replication: Set up the new server as a read replica of the old one. When ready, promote it to primary. This requires root database access on both servers.
• WP Migrate Pro: Supports push/pull with table-level selection. Sync only tables that changed (wp_comments, wp_posts, wp_woocommerce_* tables).

According to BlogVault's case studies, their incremental approach reduces the final sync window to under 5 seconds for sites with up to 50,000 daily visitors.

Step 7: Switch DNS and Monitor

With everything tested and the final sync complete, it's time to point your domain to the new server.

Update DNS Records

Log into your domain registrar (Cloudflare, Namecheap, GoDaddy, etc.) and update the A record to point to your new server's IP address. If you lowered the TTL to 300 seconds earlier, propagation should complete within 5-10 minutes globally.

For sites using Cloudflare as a proxy, simply update the origin IP in the Cloudflare dashboard—propagation is instant since Cloudflare handles DNS resolution.

Post-Switch Monitoring Checklist

During the first 24 hours after switching, monitor these metrics:

What to Monitor	Tool	What to Look For
Uptime	UptimeRobot, Pingdom	Any 5xx errors or timeouts
SSL Status	SSL Labs Test	Grade A or A+ rating
Page Speed	GTmetrix, WebPageTest	TTFB under 600ms
404 Errors	Google Search Console	Broken links from migration
Email Delivery	Send test emails	SPF/DKIM still valid
Cron Jobs	WP-Cron or server cron	Scheduled posts publishing

Handling the Overlap Period: Keeping Both Servers in Sync

DNS propagation isn't instant everywhere. During the transition window (typically 5 minutes to 4 hours depending on ISPs), some visitors hit the old server while others reach the new one.

To prevent data loss during this period:

• Keep the old server running for at least 48 hours after the switch. Don't cancel your old hosting immediately.
• Disable user registration and comments on the old server (add define('DISALLOW_FILE_MODS', true); to wp-config.php on the old server).
• For WooCommerce: Enable maintenance mode on the old server's checkout page only, with a message saying "Please refresh the page" which will route them to the new server.
• Set up email forwarding: If your old host handled email, ensure MX records are updated or forwarding is configured.

Common Migration Mistakes and How to Avoid Them

Based on data from WordPress hosting support teams at SiteGround and Cloudways, these are the most frequent migration failures:

• Forgetting wp-config.php salts: If you regenerate salts, all logged-in users get logged out. Keep the original salts unless you have a security reason to change them.
• File permission mismatches: The new server may have different user/group ownership. Run chown -R www-data:www-data /var/www/html and set directories to 755, files to 644.
• Missing PHP extensions: Plugins like Imagick, WooCommerce, or caching plugins require specific PHP extensions (gd, intl, soap, zip). Check with php -m on the new server.
• Hardcoded paths in plugins: Some plugins store absolute file paths. After migration, check plugin settings pages for any references to the old server's directory structure.
• Ignoring .htaccess: If moving from Apache to Nginx, your .htaccess rules won't work. Convert them to Nginx configuration blocks using tools like the Winginx converter.

Recommended Migration Tools Comparison

Choosing the right tool depends on your site size, technical skill level, and budget. Here's how the most popular options compare:

Tool	Best For	Max Site Size (Free)	Zero-Downtime Support	Price
BlogVault	High-traffic sites	N/A (paid only)	Yes (real-time sync)	$89/year
Duplicator Pro	Developer workflows	500MB	Manual (two-step)	$49.50/year
All-in-One WP Migration	Small sites	512MB	No	Free / $69 unlimited
WP Migrate Pro	Staging workflows	N/A (paid only)	Yes (push/pull)	$49/year
rsync + mysqldump	Technical users	Unlimited	Yes (with final sync)	Free
Cloudways Migrator	Moving to Cloudways	Unlimited	Yes	Free (Cloudways customers)

Final Thoughts: Your Migration Timeline

A well-planned WordPress migration with zero downtime typically follows this timeline:

• 48 hours before: Lower DNS TTL, create full backup, document current setup
• Day of migration (hours 1-2): Set up new server environment, copy files, import database
• Day of migration (hours 2-3): Test via hosts file, fix any issues, install SSL
• Day of migration (hour 4): Final database sync, switch DNS
• Next 48 hours: Monitor uptime, check for 404s, verify email delivery
• After 48 hours: Remove hosts file entry, cancel old hosting (keep backup)

The entire process takes 4-6 hours of active work for a typical WordPress site under 5GB. For larger sites or WooCommerce stores with continuous transactions, budget a full day and consider using BlogVault or a similar real-time sync tool to minimize the risk window.

By following this guide, your visitors will experience zero interruption while you move to faster, more reliable hosting. The key is preparation: lower that TTL early, test thoroughly before switching, and always keep your old server running as a fallback for at least 48 hours.