Move WordPress to a New Host Without Downtime

The golden rule of migration

Never delete anything on the old host until DNS has fully propagated and you've tested the new one. Downtime happens when people rush the cutover.

Step 1 - Full backup

From cPanel or hPanel:

1. Files: full public_html backup (including .htaccess and wp-config.php).
2. Database: export a .sql dump with phpMyAdmin.
3. Store the archive locally and in object storage — a backup on the same server isn't a backup.

Step 2 - Restore on the new host

The easy path is a migration plugin (Hostinger, Cloudways, and SiteGround all ship one):

• Install WordPress on the new host, then run the host's migration tool.
• For a manual move, upload the archive, restore files to the document root, create a database, import the .sql, and update wp-config.php credentials.

Step 3 - DNS cutover

• Nameserver swap: update at your registrar to the new host's nameservers.
• A-record swap: point @ and www at the new server IP.

Propagation takes 1-24 hours (usually 1-4). Both hosts running in parallel means visitors keep getting the old site until DNS flips — zero downtime.

Step 4 - Verify before you cancel

Once propagation completes:

• Padlock + valid SSL on the new host
• All media and pages load
• Contact forms and WooCommerce payments work
• Email still routes (check MX records)
• Search console shows the new server in crawl logs

Then cancel the old plan and delete old backups.

Comparing moving to a host? Read Hostinger vs Bluehost or migrate to Cloudways for the managed route.