WordPress ·
How to Move a WordPress Site to a New Host Safely
By Manu Mathew, Technical Lead Engineer · Published 20 October 2026 · Last updated 20 October 2026
Your hosting plan is up for renewal, the site feels slow, or support has stopped answering. You want to move a WordPress site to a new host, but you have heard stories of lost emails, broken pages and a week of missing enquiries.
Most of those problems come from doing the steps in the wrong order. This guide walks through a safe order, written for small-business owners in Kozhikode, across Kerala and anywhere else, whether you do the move yourself or hand it to a developer.
Quick answer
To move a WordPress site to a new host safely, take a full backup of files and database, copy the site to the new host, test it there before touching the domain, then switch DNS during a quiet period. Check email records, SSL and forms afterwards, and keep the old hosting running until everything settles.
What do you need before you move a WordPress site to a new host?
You need working logins for four places and a complete, recent backup. Gathering these first saves most of the stress later.
- Old hosting account: control panel or file access, and a way to export the database.
- New hosting account: ready, with a PHP version at least as new as the old one.
- Domain registrar and DNS: whoever controls where your domain points. This is often a different company from the host.
- WordPress admin: an administrator login that you know works.
- Email setup: a note of where your business email lives. If it sits with the old host, it needs its own plan.
If you’re still choosing where to go, decide that first. Moving twice in a year is more work than waiting a few weeks.
What is the safe order to move a WordPress site to a new host?
Copy first, test second, switch the domain last. The old site stays live and untouched until the new copy is proven.
- Pick a quiet window and pause content changes, new orders if you can, and plugin updates.
- Take a full backup of files and the database, and keep a copy off both servers.
- Lower the DNS TTL (how long the internet caches your domain’s address) a day or two before the switch, so the change spreads faster.
- Copy the files and import the database on the new host, then update the database connection details in
wp-config.php. - Test the new copy before the domain points to it (more on this below).
- Switch DNS to the new host’s address.
- Set up SSL on the new host so the site loads over HTTPS.
- Check everything again on the live domain.
- Keep the old hosting running for a while as a fallback.
WordPress documents the technical side in its guide to moving WordPress. It also warns that a plain find-and-replace on the database can break saved settings, which is one reason to keep the same domain where you can.
How do you test the new host before switching the domain?
Open the new copy without changing public DNS, either through a temporary address from the host or a hosts-file entry on your own computer. Only you see the new server; visitors still reach the old one.
What I check on the new copy:
- Main pages and menus load, with images and styling intact.
- Forms send a test enquiry that actually arrives.
- Checkout or booking, if you have one, runs end to end in test mode.
- Admin login works, and plugins show no errors.
- Speed feels at least as good as before on a phone.
- Scheduled tasks such as backups or reminder emails are still set up.
If something breaks here, nothing public has changed. You fix it calmly and test again.
How do you avoid losing email, rankings or orders during the move?
Plan for each one separately, because each fails in a different way. Most problems come from DNS records, a forgotten final sync or a stray setting.
| Risk | What goes wrong | How to prevent it |
|---|---|---|
| Mail stops when DNS moves | Copy the existing mail records (MX) exactly, or move mail as a separate step | |
| Search rankings | Pages vanish or get blocked | Keep the same URLs, check the site isn’t set to discourage search engines, resubmit the sitemap |
| Orders and enquiries | New data lands on the old server | Pause changes, or do a final database sync just before the switch |
| HTTPS | Browser security warnings | Issue the certificate on the new host straight after the DNS change |
When the domain and URLs stay the same, Google treats it as a site move without URL changes. That is the gentler case. Changing the domain at the same time adds redirects and more risk, so I usually suggest doing one change at a time.
When should you cancel the old hosting?
Wait until DNS has settled, email works, and you have a recent backup from the new host. A week or two of overlap is a small price for a safe fallback.
Before cancelling, download one last full backup from the old account and keep it somewhere you control. Check that nothing else lives there, such as another domain, old email or a forgotten subdomain.
How I handle a WordPress host move with a client
I write the plan down first, agree a quiet window with you, and don’t touch the live site until the new copy has passed the checks above.
- A short written plan: what moves, what stays, who controls each account, and the rollback step if something goes wrong.
- Accounts stay in your name. I work with access you grant and can remove, so you keep control of the domain and hosting.
- A test checklist we both see, with the pages and forms that matter most to your business.
- A clear switch moment, agreed in advance, with me watching the site afterwards.
- A brief summary at the end: what changed, where backups are, and when it’s safe to close the old account.
Much of this works fully remotely. If you’re elsewhere in India or overseas, working remotely with me explains how calls, access and updates usually run.
Frequently asked questions
Will my website go down when I change hosts?
It shouldn’t if the move is done in the right order. The old site keeps serving visitors while the new copy is built and tested. During the DNS change some visitors may reach the old server for a short while, which is harmless if content changes are paused.
How long does it take to move a WordPress site to a new host?
The copy itself is often done within a day for a small site. DNS changes can take from minutes to a day or so to reach everyone. The real time goes into testing and the overlap period, which is worth planning around rather than rushing.
Can I move my WordPress site with a migration plugin?
Often, yes. Migration plugins work well for many small sites, but large media libraries, low server limits or custom setups can make them fail halfway. Whichever tool you use, take your own full backup first and test the new copy before switching the domain.
Do I need to move my domain name too?
No. Your domain registration can stay where it is; you only change the DNS records so the domain points to the new host. Moving the registration is a separate, optional task, and doing it at the same time adds another thing that can go wrong.
What happens to my business email during the move?
That depends on where your email is hosted. If it uses a separate email service, keep its existing mail records exactly as they are. If it lives with the old host, plan a separate email move, or keep it there until a new mailbox is ready and tested.
Need help moving your WordPress site?
If you’re planning to move a WordPress site to a new host and want it done carefully, I’m happy to talk it through. You can read more about my WordPress website work, reach me through the contact section or email me at manu@manu.co.in. Tell me a little about your business and the site, and we’ll go from there.