How to Migrate WordPress to a New Host Without Downtime

Switching hosting providers can feel like moving apartments while the building is on fire. There is a lot happening at once, the stakes feel high, and one wrong step can take your site offline. But it does not have to be that stressful.

Whether you are leaving a sluggish shared host or upgrading to managed WordPress hosting, the migration process follows a predictable pattern. This guide walks through three approaches: manual migration, plugin-assisted migration, and managed transfers offered by premium hosts.

Before You Start: The Pre-Migration Checklist

Rushing into a migration without preparation is how sites end up broken. Before touching anything, handle these items:

• Back up everything. Database, wp-content folder, wp-config.php, and .htaccess. Store copies locally and in the cloud.
• Document your current setup. Note your PHP version, active plugins, custom server configurations, and any cron jobs.
• Check DNS TTL values. Lower your TTL to 300 seconds (5 minutes) at least 24 hours before migration. This speeds up DNS propagation later.
• Audit your plugins. Deactivate any plugins you are not actually using. Fewer moving parts means fewer things that can break.

Method 1: Manual Migration

Manual migration gives you the most control. It is best for developers comfortable with phpMyAdmin and FTP.

Step 1: Export Your Database

Log into phpMyAdmin on your current host. Select your WordPress database and click Export. Choose the “Custom” method so you can select specific options. Use SQL format and check “Add DROP TABLE” to avoid conflicts on import.

Step 2: Download Your Files

Connect to your current server via SFTP and download the entire WordPress directory. Pay special attention to your wp-content folder, which contains themes, plugins, and uploads. This folder is irreplaceable.

Step 3: Create the Database on Your New Host

In your new hosting control panel, create a fresh MySQL database and user. Grant the user full privileges on the database. Write down the database name, username, and password.

Step 4: Import and Configure

Import your SQL file into the new database. Then edit wp-config.php with the new database credentials. Upload all files to your new server.

Step 5: Update DNS

Point your domain’s A record to your new server’s IP address. With TTL already lowered, propagation should complete within minutes rather than hours.

Method 2: Plugin-Assisted Migration

For most site owners, a migration plugin eliminates the technical complexity. Tools like All-in-One WP Migration, Duplicator, or UpdraftPlus handle the heavy lifting.

The general process:

1. Install your chosen migration plugin on the source site
2. Create a full export (database plus files)
3. Install WordPress on your new host
4. Install the same migration plugin on the fresh WordPress install
5. Import the export file
6. Update permalinks by visiting Settings > Permalinks and clicking Save

One important caveat: free versions of most migration plugins cap file sizes. If your site exceeds the limit, you will need the premium version or a manual approach for the file transfer.

Method 3: Managed Transfers

This is where premium managed WordPress hosts earn their keep. Providers like Kinsta, WP Engine, Cloudways, and SiteGround offer free migrations handled by their own teams.

The typical process:

1. Submit a migration request through the host’s dashboard
2. Provide your current host’s login credentials (or install a migration plugin they specify)
3. The host’s team handles the entire transfer
4. You verify the migrated site on a temporary URL
5. Update DNS when everything checks out

Kinsta provides unlimited free migrations for all plans and typically completes them within 24 hours. WP Engine offers a dedicated migration plugin that automates the process. Cloudways includes a free migration for every plan and assigns a dedicated migration engineer.

If migration stress is a dealbreaker for you, this alone can justify choosing a managed host. You can compare options in our Cloudways vs SiteGround breakdown.

Avoiding Downtime During Migration

Zero-downtime migration comes down to timing your DNS switch correctly.

The key is keeping your old site live until the new one is fully verified. Here is the sequence:

1. Complete the migration on the new server
2. Test thoroughly using a temporary URL or by editing your local hosts file
3. Verify email, forms, WooCommerce checkout, membership logins, and any integrations
4. Only after everything works, update your DNS records
5. Keep your old hosting account active for at least 48 hours after DNS changes, as a fallback

For WooCommerce sites, consider putting the store in maintenance mode during the final DNS switch to prevent orders from hitting the old database after migration.

Post-Migration Verification

After DNS has propagated and your site is running on the new host:

• Test all pages for broken links and missing images
• Verify SSL is working (your new host should handle this, but check)
• Test forms and checkout to confirm email delivery and payment processing
• Check page speed to confirm the new host is actually faster
• Monitor error logs for the first 48 hours
• Re-enable any caching and CDN settings

Common Migration Problems and Fixes

Serialized data issues. If your site URLs are stored differently in the old database, use a tool like WP-CLI’s search-replace command rather than a simple find-and-replace in SQL. WordPress stores serialized data that breaks with naive text replacement.

Mixed content warnings. After migration, some resources may still reference HTTP instead of HTTPS. A plugin like Really Simple SSL can fix this, or you can run a database search-replace from http to https.

Permalink errors. If pages return 404 errors after migration, regenerate your .htaccess file by visiting Settings > Permalinks and saving without changes.

Which Approach Should You Choose?

For most WordPress site owners, a managed transfer from your new host is the obvious choice. It is free, low-risk, and lets experts handle the technical details. If you are considering a switch to managed hosting, check our guide on what managed WordPress hosting actually is to understand what you are getting.

If your new host does not offer managed transfers, a migration plugin is the next best option. Reserve manual migration for situations where you need granular control or are dealing with unusual server configurations.

The most important thing is not to rush. A careful migration takes a few hours. Fixing a broken one can take days.