You can move WordPress to a new host without any interruption in service. There is one condition: the old server keeps serving the site until all traffic reaches the new one. The website and email do not disappear, because the only thing that changes is where the domain points. The address itself stays the same.
Table of contents
What does moving WordPress to a new host without downtime involve?
First you set up a complete copy of the site on the new server and test it. Then you change DNS. You switch off the old hosting at the very end, not earlier. The URLs do not change, so this is an infrastructure migration, not a domain change (for Google these are two completely different scenarios). Google describes this specific case in its guide to changing hosting without changing URLs. So where does downtime come from? Usually from doing the steps in the wrong order. The move itself is rarely to blame.
What should you prepare before migrating WordPress to a new server?
Without a full copy of the files and the database there is no point in starting. A convenient way to make one is a backup made with UpdraftPlus. And before you touch anything, write down the configuration of the old server:
- the PHP version and enabled extensions,
- the SSL certificate and how it is renewed,
- cron jobs,
- email accounts with their aliases and forwarding rules,
- DNS records: A, MX, TXT,
- access to the domain panel.
Second thing: who actually manages the DNS zone? The registrar, the current host, or maybe an external provider? You need to know this before you start, not halfway through. Oh, and lower the TTL in advance, which is the time other servers remember a record for. A lower TTL means a faster switch later. Simple.
How do you copy the files and database to the new server?
You move two things: the directory with the WordPress files and a database dump. wp-config.php then ties them together. In practice it looks like this:
- Upload the files, especially the wp-content directory and the wp-config.php file.
- Create a database and a user with privileges in the new hosting panel.
- Import the database dump.
- Enter the new database name, user, password and host in wp-config.php.
If the path or the address changes, you replace the references in the database with the WP-CLI search-replace command or with a plugin. That is how the official WordPress migration guide describes it. But with the same domain there is usually no need for that, so do not mess with the addresses without a reason. The documentation warns about one more thing: some export methods skip widget and plugin settings. That is why I recommend noting them down beforehand. Five minutes of work, and no stress later.
How do you test the site on the new hosting before changing DNS?
The simplest way is the hosts file on your own computer: you add the new server’s address and the domain. You already see the new version, while the rest of the world still sees the old one. It is a good way to calmly check contact forms, login, the cart and payments in a store, the SSL certificate, images and emails sent from WordPress. Planning bigger changes? Then a permanent staging environment for WordPress will come in handy. And then there is Google Search Console. The verification has to survive the move, for example through a DNS record or a file that is also present on the new server.
Changing DNS without an interruption: the order of steps
The DNS change itself does not cause downtime, as long as both copies of the site work correctly during the transition period. For the time of the switch, pause content editing and order taking. Or, if you cannot, run a final database sync right before the change so that nothing is left behind on the old server. Then point the A record (and AAAA, if you have one) to the new server’s address. Propagation time depends on the TTL, so some visitors still land on the old address for a while. That is normal. Issue the SSL certificate on the new server as soon as the domain starts pointing to it.
Moving email when you change hosting
Email lives independently of the website. The A record directs web traffic and the MX records direct messages, so you can move the two together or separately. The order is this: you create the same mailboxes on the new server, copy their contents (for example with an IMAP sync) and only then change MX. Update SPF, DKIM and DMARC as well.
Without SPF, DKIM and DMARC, emails from the new server easily end up in spam, and the customer does not even know you sent them anything. Keep the old mailboxes active until propagation is complete, and at the end pull over any messages that managed to arrive there. All in all, the least coordination is needed with website hosting with business email from a single provider.
Changing hosting and SEO: what to watch after the move?
Rankings should not suffer if the new server responds quickly and without errors. According to the same Google guide, the crawl rate may drop temporarily right after the change. Then it gradually comes back, sometimes even above the previous level. So do not panic if the first few days look weaker. In Search Console, watch server errors, crawl stats and page performance. And the old hosting? Switch it off only when its logs show that traffic has dropped to zero. That is what Google recommends.
Moving WordPress to a new host without downtime is essentially a matter of order: copy, tests, DNS, email, and finally switching off the old server. If the site does not run on WordPress yet, that is a different project than a hosting change. In that case you are looking at company websites built on WordPress, not a move.
Frequently asked questions
Do you need to set up 301 redirects when changing hosting?
No, if the domain and the URLs stay the same. The search engine and visitors reach the same addresses, only a different server handles them. Redirects are needed only when you change the domain or the URL structure.
How long does DNS propagation take after changing hosting?
It depends on the TTL set before the change and on the DNS servers that users rely on. Some refresh records faster, others slower. That is why the TTL is lowered in advance and the old server keeps running as long as traffic reaches it.
When can you switch off the old hosting?
When the old server’s logs no longer show any traffic and the email from the old mailboxes has been moved in full. Not before. Rushing risks losing emails or orders placed during the transition period.
