A new host can mean faster pages, better support or lower costs. The move itself, however, worries many owners. The good news is that you can migrate a WordPress site with no visible downtime if you follow the right order. This guide walks through that order.

In this article
Why you should migrate a WordPress site carefully
Visitors and search engines notice broken pages, missing images and slow responses. A rushed move can also lose orders on a store. So a calm plan matters more than speed.
Plan how to migrate a WordPress site
- List your plugins, themes, cron jobs and email setup
- Check that the new host meets WordPress requirements
- Lower the DNS TTL to a few minutes, a day or two ahead
- Choose a quiet time, and pause content changes during the final copy
Copy the files and the database
First, take a full backup of the files and the database. Then copy both to the new server. You can use a migration plugin, or you can move them by hand over SFTP and a database export. Next, update the database details in wp-config.php.
Test the new server before switching DNS
This step is what makes zero downtime possible. Point your computer to the new server with a temporary URL or a local hosts file entry. Then click through the site: pages, forms, login and checkout. If you must change URLs, use a safe search-and-replace tool such as WP-CLI, because it handles serialized data correctly.
Switch DNS and keep the old site running
Once testing passes, do a final sync of recent content and orders. Then update the DNS records. Because you lowered the TTL, most visitors reach the new server within minutes. Keep the old host live for a few days, so nobody lands on an empty server while DNS settles.
After the move: quick checks
- Confirm HTTPS works and the certificate is valid
- Test email, contact forms and payment gateways
- Submit the sitemap again in Search Console
- Check redirects, caching and scheduled tasks
- Set up backups and uptime monitoring on the new host
Common mistakes when you migrate a WordPress site
The usual problems are forgetting email records, leaving the old site open to search engines, and skipping a final sync. Also, never cancel the old plan on the same day. If you would rather not risk it, our team can handle the move and then look after the site with a WordPress maintenance retainer.
Let’s connect
- WordPress consultant and technical architect for enterprise teams.
- Need help with a WordPress project? Get in touch
- See the WordPress services I take on for product and brand teams.
- Delivery notes from similar programmes are in the case studies.
Leave a Reply