how to move a wordpress site to a new host without downtime

Moving a WordPress site sounds risky and usually is not. Almost all the anxiety comes from one thing: people change the DNS first and then start copying files, which guarantees a window where visitors hit a half-built site. Do it the other way round and the switch itself is close to instant.

The principle is simple. Build a complete, working copy on the new host, test it properly on a temporary address, and only then point the domain. Until that final step, your live site carries on untouched — and if anything goes wrong, you have changed nothing that visitors can see.

What you actually need to copy

A WordPress site is two things: a folder of files and a database. Miss either and the copy will not work.

• The wp-content folder — your themes, plugins and every uploaded image. This is the part that is genuinely yours and cannot be re-downloaded.
• wp-config.php — mainly for reference. You will need new database credentials on the new host, but the salts and any custom constants are worth keeping.
• The database — every post, page, comment, user and setting. Export it as SQL rather than using a plugin's own format.
• Anything outside the WordPress folder — a robots.txt, verification files, custom .htaccess rules, cron scripts.
• Email, if it is on the same domain. This is the single most commonly forgotten item and the one people notice fastest.

Build and test before you switch

1. 01Create the hosting account and database on the new host.
2. 02Upload the files and import the database.
3. 03Update wp-config.php with the new database name, user and password.
4. 04Reach the site on a temporary address — a hosts-file entry or a preview URL — WITHOUT changing public DNS.
5. 05Click through it properly: the homepage, a blog post, a category page, the search, a contact form, and the admin area.
6. 06Check images actually load. Broken images almost always mean the uploads folder did not copy completely.

A hosts-file entry is the most reliable way to preview. It points your machine alone at the new server while the rest of the world still sees the old one, so you are testing the real site at its real domain, with no URL rewriting to confuse matters.

Lower your DNS TTL before you switch

This is the step that separates a clean migration from a messy one, and it has to happen in advance.

TTL — time to live — tells other servers how long to cache your DNS records. If it is set to 24 hours, some visitors will keep hitting the old server for a day after you switch. Drop it to 300 seconds at least 24 hours beforehand, and the changeover propagates in about five minutes instead.

After the switch

• Re-issue the SSL certificate on the new host. Certificates do not travel with the site, and a browser warning undoes all the careful work above.
• Check for mixed content — resources still loading over http:// on an https:// page.
• Submit the site in Google Search Console and confirm it can be crawled.
• Test email sending. Contact forms often break quietly because the new host handles outbound mail differently.
• Set up backups on the new host. Do not assume they are on by default.

Done in this order, a WordPress migration is undramatic. The site is built and verified before anything public changes, the DNS switch is a five-minute event rather than a day-long limbo, and the old site is still there if you need it.