Switching hosts rarely breaks your site itself. It breaks the things around it: email, DNS, and SSL. Here’s what actually fails after a migration, and how to fix each.
Moving a WordPress site to a new host is usually the easy part. The files copy, the database imports, and the site loads on a temporary URL looking exactly as it should. Then you point your domain at the new server and the problems start: email stops arriving, half your visitors see the old site, and the browser slaps a “Not Secure” warning on your homepage. None of that means the migration failed. It means the pieces that live around your site, your email, your DNS, and your security certificate, do not automatically follow the files. Here is what breaks most often after switching hosts, why, and how to fix each one without panicking.
Key Takeaways
The site files migrate cleanly, but three things routinely break: email, because mail service does not move just because the website did, DNS, because changes take time to propagate across the internet, and SSL, because the new host must issue a fresh certificate only after your domain points to it. Most “migration failures” are really just one of these caught mid-change. Prevent nearly all of them by lowering your DNS record TTL a day ahead, sorting out email before you switch, keeping the old host running for at least 48 hours, and letting the new SSL certificate issue before you force HTTPS. Fix the rest with a database URL search-and-replace and a cache purge.
Why things break right after a host migration
The core reason is simple: a migration moves your website, but your domain still decides where email, web traffic, and certificate checks are sent. When you change the domain’s DNS to point at the new host, everything that relied on the old pointing has to be reestablished. Email routing, the security certificate, and any URLs saved inside your database do not update themselves. So the failures you see are not corruption, they are loose ends from the handoff, and each one has a specific, fixable cause.
Email is the failure that catches everyone
This is the number one surprise. If your email was hosted on the same server as your website with the old host, pointing your domain to a new web host can cut off your mail, because the domain’s MX records, the settings that route email, may change or stop matching a working mailbox. Before you migrate, decide where email will live. If you are keeping it with the old provider or a separate service, make sure the MX records stay pointed there after the switch. If email is moving too, create the mailboxes on the new host first and confirm they work before you flip DNS. Losing a day of client email is the most avoidable migration disaster there is.
DNS propagation: wait before you panic
After you change nameservers or DNS records, the update does not reach the whole internet instantly. It spreads gradually, and the change can take up to 24 to 48 hours to fully propagate, governed by each record’s TTL, or time-to-live. During that window, some visitors load the new host and some still hit the old one, which looks like random breakage but is completely normal. Two things make it painless: lower your records’ TTL a day before migrating so changes take effect faster, and test the new site ahead of time using the host’s temporary URL or your computer’s hosts file. Above all, do not cancel the old host until propagation is complete.
The “Not Secure” SSL warning
A fresh “Not Secure” warning after migration almost always means the new host has not issued a valid SSL certificate for your domain yet. Most hosts issue a free certificate automatically, often through Let’s Encrypt, but the certificate can only validate once your domain actually points to the new server. So the order matters: let DNS point over, let the certificate issue and show as active, and only then force HTTPS site-wide. Forcing HTTPS before the certificate is live is what turns a temporary warning into a site that will not load at all.
Mixed content and broken images
If images vanish or the browser warns about mixed content, your database is still holding old URLs, either the previous domain or insecure http links. The fix is a careful search and replace of those URLs in the database, using a tool like WP-CLI or a reputable search-and-replace plugin, followed by updating your site address and clearing every cache. Do not edit URLs by hand across thousands of rows, and always back up the database before a replace. Once the stored URLs match your live domain and protocol, the broken images and warnings clear up.
A migration order that prevents most of this
Sequence the move and most failures never happen.
- Lower your DNS TTL a day ahead. Shorter TTL means your later DNS change propagates faster.
- Copy the site and test on a temporary URL. Confirm it works on the new host before any DNS change, following a reliable WordPress migration guide.
- Sort out email first. Decide where mail lives and confirm mailboxes and MX records before you touch the domain.
- Point DNS to the new host. Change nameservers or records, then wait for propagation rather than assuming it is instant.
- Let SSL issue, then force HTTPS. Confirm the certificate is active before redirecting all traffic to HTTPS.
- Search-replace URLs and purge caches. Fix any old domain or http links in the database and clear site, plugin, and CDN caches.
- Keep the old host live for 48 hours. Do not cancel until propagation is done and everything checks out.
Frequently Asked Questions
Why did my email stop working after changing hosts?
Because email routing did not move with your website. If mail lived on the old server, pointing your domain to a new host can break it unless the MX records still point to a working mailbox. Sort out email and MX records before you migrate.
How long does DNS take to update after a migration?
Up to 24 to 48 hours to fully propagate, depending on your records’ TTL. During that time some visitors see the new host and some the old, which is normal. Lowering TTL beforehand speeds it up, and you should not cancel the old host until it finishes.
Why does my site say “Not Secure” after moving hosts?
The new host has not issued a valid SSL certificate for your domain yet, usually because DNS has not fully pointed over. Let the certificate issue and show active, then force HTTPS. Forcing HTTPS too early can take the site offline.
What causes broken images and mixed content warnings?
Old URLs saved in your database, either the previous domain or http links. Run a database search and replace to update them to your live domain and https, then clear all caches. Back up the database before making the replacement.
Should I cancel my old host right after migrating?
No. Keep it running for at least 48 hours until DNS fully propagates and you have confirmed the site, email, and SSL all work on the new host. Canceling early can cause downtime you cannot quickly reverse.
How do I test the new site before pointing my domain?
Use the new host’s temporary URL or edit your computer’s hosts file to preview the site on the new server. This lets you catch problems before any visitor is affected by the DNS change.
Final Word
A host migration that “fails” almost never means your site is broken. It means email, DNS, or SSL got caught mid-handoff, and each of those has a clear fix. The real trick is order: lower your TTL early, settle email before you flip DNS, let the SSL certificate issue before forcing HTTPS, and keep the old host alive for a couple of days as a safety net. Handle the database URLs and caches last, and the scary post-migration symptoms resolve on their own. Treat the move as a sequence rather than a single switch, and switching hosts becomes routine. For more, see how to fix a WordPress “updating failed” error and why managed WordPress hosting beats basic shared hosting.