Moving a WordPress site to a new host sounds risky, and many site owners delay it for months because they are afraid of breaking something. But most problems during a move come from a few small details, such as DNS timing, email settings and SSL certificates. If you prepare for these, your visitors will not notice that anything has changed.
This guide explains why people move hosts, how DNS timing really works, how to move your site without downtime, and the problems site owners most often report after a move.
Why Site Owners Move to a New Host
The most common reason is speed. A slow server makes every page slow, and caching plugins can only hide part of the problem. Data from the HTTP Archive shows that only about 23.5% of WordPress sites on mobile have a good server response time, so the hosting is often the main reason a site is slow. Our guide to WordPress Core Web Vitals explains why server response time matters so much.
Other common reasons are poor support, frequent outages, price increases when a discount ends, and limits on storage or resources. Some site owners also move because their host does not offer the PHP version, staging or backups they need.
How DNS Timing Works and What Google Recommends
When you move to a new host, the most important step is changing your domain's DNS records so they point to the new server. Visitors do not all see this change at the same time. Their internet providers keep a saved copy of your old DNS records for a period called the TTL, which stands for time to live.
The table below shows how long some visitors may still reach your old server after you change the DNS, based on the TTL value. This is why the old site must keep working during the move.
| TTL value | Time some visitors may still see the old server |
|---|---|
| 300 seconds | About 5 minutes |
| 3,600 seconds | About 1 hour |
| 14,400 seconds | About 4 hours |
| 86,400 seconds | About 24 hours |
Google gives clear advice for moving a site to new hosting while keeping the same URLs. Lower your DNS TTL to a short value at least a week before the move, so the change spreads faster. Keep the old hosting running until its server logs show no more visitors. Google also explains that its crawler may visit your site less often right after the move, and that the crawl rate should return to normal, or even increase, over the following days if the new server is fast and stable.
How to Move WordPress Without Downtime
The idea is simple. You copy the site to the new server, test it there while the old site stays live, and only then change the DNS. Visitors keep using the old site until the new one is ready.
- Lower the TTL a week before. In your DNS settings, set the TTL of your main records to 300 seconds. Write down all your current DNS records, including MX records for email, before you change anything.
- Make a full backup. Take a complete backup of files and database, and store it outside both hosting accounts.
- Copy the site to the new host. Use a migration plugin, your new host's migration tool, or copy the files and database by hand. Large sites are often easier to move with the host's own tool or by a developer, because big backups can time out.
- Test the new site before switching. Use your computer's hosts file or the temporary URL from your new host to view the new site. Check pages, forms, logins, the shop checkout and the WordPress admin area.
- Prepare SSL on the new server. Some hosts can only issue a free SSL certificate after the DNS points to them. Ask your new host how they handle this, so visitors do not see a security warning after the switch.
- Pause changes on the old site. Just before the switch, stop publishing content. On an online store, take a final copy of the database right before the switch, so no orders are lost.
- Change the DNS. Update the A record, or change the nameservers if you are moving DNS to the new host. Copy all other records, especially email records, exactly as they were.
- Watch both servers. Check the old server's logs until visits stop, then wait a few more days before you cancel the old hosting.
Want experts to move your site? We migrate WordPress sites to new hosting with no downtime, then tune the new server as part of our WordPress speed optimization service so you see the full speed benefit.
Problems People Often Report After a Move
Most migration problems are not caused by WordPress itself. They are caused by settings that live outside your website, such as email, DNS and SSL. These are the issues site owners ask about most often in forums like Reddit and the WordPress.org support forums.
Email stops working. This is one of the most common problems. In one Reddit thread, a site owner moved from Cloudways to SiteGround and suddenly stopped receiving emails, even though their mailboxes were still with GoDaddy. The likely cause was that the new host was set up to handle email for the domain, so it tried to deliver messages locally instead of sending them to GoDaddy. The fix is to check that the MX records still point to your real email provider, turn off email on the new host or mark it as remote, and send website emails through SMTP.
Contact forms do not send. Even when mailboxes work, emails sent by WordPress can fail or go to spam on a new server. Sending website email through a proper SMTP service solves this in most cases.
Security warnings in the browser. If the new server does not have a valid SSL certificate when the DNS changes, visitors see a warning page. Preparing SSL before the switch, as in step 5, prevents this.
Missing images or old content. This happens when uploads were not fully copied, or when content was added to the old site after the copy was made. A final sync before the switch avoids it.
After the Move
Once the new host is live, check the site closely during the first week. Check Google Search Console for crawl errors, test your forms again, and confirm that backups are running on the new server. Many hosts do not copy your old backup settings, so you may need to set them up again. Our guide to a WordPress backup strategy explains what to set up.
This is also a good time to measure the speed of your site and compare it with the old host. If you want a team to handle moves, backups, updates and performance checks for you, our WordPress maintenance plans include developer time that can be used for work like this.
