Moving your WordPress site to a new host sounds risky. What if the site goes down, emails stop, or Google sees errors? The good news is that a move doesn’t need any downtime, and you don’t need to pay for it.
The short answer: copy your site to the new host while the old one keeps running, test the copy privately, then point your domain to the new host. Visitors keep seeing the old site until the switch, and the new one from then on. There’s no gap in between.
This guide uses Migrate Guru, a free plugin that copies sites up to 200 GB. It works on almost any host, and it doesn’t need you to download or upload big backup files. If you’re not sure how domains, hosting and DNS fit together, read Domain, Hosting and DNS Explained in Plain English first. It makes Step 5 much easier to follow.
Before you start
Get these ready first. It takes 10 minutes and saves hours of panic later.
- Your old hosting login. You need the WordPress admin login and access to the hosting dashboard (cPanel or similar).
- Your new hosting account. Choose a plan with room for your site. If you’re still choosing, our guide to the best web hosting for small business websites compares the main options.
- Your domain registrar login. This is where you bought the domain (GoDaddy, Namecheap, Hostinger and so on). You’ll change the DNS here in Step 5.
- Where your email lives. If your business email runs on your old host’s cPanel mail, moving can break it. If it runs on Google Workspace or Microsoft 365, it’s safe, but you still need to copy its records. Step 6 covers both.
Lower your DNS TTL a day early
TTL (“time to live”) tells internet providers how long to remember where your domain points. It’s often set to several hours. At your DNS provider, change the TTL of your domain’s A record to 300 seconds (5 minutes) at least 24 hours before the move. Then, when you switch, most visitors reach the new host within minutes instead of hours.
Why Migrate Guru (and when to use something else)
There are three popular free migration plugins. Each one has a catch in its free version:
| Plugin | Free version | Best for |
| Migrate Guru | Sites up to 200 GB; copies server to server, so no file downloads | Most sites moving between two live hosts |
| Duplicator (Lite) | Bundles the site into an archive plus an installer file; up to about 500 MB with its DupArchive engine | Small sites, or moving to or from a local computer |
| All-in-One WP Migration | No size limit of its own, but your new host’s upload limit applies; bigger imports need the paid Unlimited Extension | Very small sites on hosts with high upload limits |
Checked on the plugins’ official pages, October 2026.
We use Migrate Guru because the free version handles big sites and you never download or upload a backup yourself. Two limits to know: it can’t move a site to or from a local computer, and each account can move up to 5 different sites a month. That’s plenty for one business site.
One more thing: many hosts migrate your site for free when you sign up, including Hostinger, SiteGround and Cloudways. Check your new host’s dashboard first. If they offer it, let them do the copy, then still follow Steps 4–7 to test and switch safely.
Step 1: Take a full backup of the old site
Migrate Guru copies your site, but it doesn’t keep a backup. So make your own first, and download it to your computer. If anything goes wrong, you can restore from it.
Use your host’s backup tool or a free plugin like UpdraftPlus. Our guide on how to back up and restore a WordPress site walks through it.
Freeze changes from now on. Don’t publish posts, edit pages or install plugins on the old site until the move is finished. Anything you change after the copy won’t reach the new host. If you run a WooCommerce store, pick a quiet time of day, because orders placed during the copy can be missed.
Step 2: Set up WordPress on the new host
- In your new hosting dashboard, add your domain as a website. The host will ask whether you want to point the domain now: don’t change anything at the registrar yet.
- Install a fresh copy of WordPress for that domain using the host’s one-click installer. Any username and password will do for now, because the migration replaces them with your old site’s logins.
- Find the temporary or preview URL your host gives the new site. Most hosts show one in the site’s dashboard, often under “Preview” or “Temporary domain”. Note it down.
- Note the new server’s IP address. It’s usually on the hosting dashboard’s main page or under account details.
Step 3: Copy the site with Migrate Guru
- On the new site: log in to the fresh WordPress, go to Plugins → Add New, search for Migrate Guru, then install and activate it. Open it and copy the migration key it shows. The key works for 24 hours.
- On the old site: install and activate Migrate Guru the same way.
- Open Migrate Guru on the old site, enter your email address, and choose your new host from the list, or pick the general option if yours isn’t listed.
- Paste the migration key and enter the new site’s URL.
- Click Migrate. The copy runs on Migrate Guru’s servers, so you can close the browser. You’ll get an email when it starts and another when it’s finished.
How long it takes depends on your site’s size. The plugin’s page says about 1 GB of files and database usually takes under 30 minutes. If the key method fails, Migrate Guru lets you enter the new host’s FTP or cPanel details instead.
When it’s done, your old site is still live and unchanged. Visitors haven’t noticed a thing. The copy now sits on the new host, waiting for you to check it.
Step 4: Test the new site before anyone sees it
This is the step that makes the move downtime-free. You check the copy privately while the public still sees the old site.
The easy way: open the preview URL from Step 2. Some pages may look slightly off there, because WordPress expects your real domain, so use it for a quick look only.
The reliable way: the hosts file. Your computer has a small file that can override DNS for you alone. Add one line to it, and only your computer opens your domain from the new host.
- Windows: open Notepad as administrator, then open C:\Windows\System32\drivers\etc\hosts.
- Mac: open Terminal and type sudo nano /etc/hosts.
Add this line at the bottom, using your new server’s IP address and your domain:
123.45.67.89 yourdomain.com www.yourdomain.com
Save the file and open your site in a private browser window. You’re now looking at the new host. Check:
- the homepage, a few posts and pages, and the images;
- that you can log in to wp-admin with your old password;
- contact forms (send yourself a test message);
- menus, search and any shop or booking pages;
- the site on your phone’s browser (your phone still sees the old site, which is a good way to compare).
When everything looks right, delete that line from the hosts file and save it again. Otherwise your computer will stay stuck on the new server’s IP address.
Step 5: Point your domain to the new host
Now you make the switch. There are two ways, and your new host will tell you which it expects:
| Method | What you change | Where |
| Change the A record | The domain’s A record (and the www record) to the new server’s IP | Wherever your DNS is managed: registrar, old host or Cloudflare |
| Change the nameservers | The domain’s nameservers to the new host’s | At your domain registrar |
Changing the A record is usually faster and safer. It changes only where the website lives, and your email records stay untouched. If you use Cloudflare, make the change in Cloudflare’s DNS tab, and it applies almost instantly. Our Cloudflare for beginners guide explains how its DNS works.
With the low TTL from earlier, most visitors reach the new host within minutes. A few internet providers can take up to 24–48 hours. That’s fine, because both copies are identical and both are online, so whichever one a visitor reaches, they see your site.
Step 6: Turn on SSL and protect your email
SSL (the padlock). Your new host can only issue a free SSL certificate once the domain points to it. Right after the switch, go to the new host’s SSL section and turn on the free certificate (usually Let’s Encrypt). It normally takes a few minutes. If you use Cloudflare in proxy mode (orange cloud), visitors keep seeing the padlock in the meantime.
Email. This is the part most guides skip, and it’s where moves usually go wrong.
- Email on Google Workspace or Microsoft 365: if you change the A record, nothing happens to your email. If you change the nameservers, first copy your MX, SPF (TXT) and DKIM records into the new host’s DNS. Otherwise your email stops arriving.
- Email on the old host’s cPanel mail: your mailboxes don’t move with Migrate Guru. Create the same mailboxes on the new host before the switch, or keep the old host’s MX records pointing to the old server until you’ve moved the email separately.
After the switch, send a test email to your business address from a personal account, and reply to it.
Step 7: After the move
- Check that you’re on the new host. Enter your domain at a free tool like dnschecker.org. When most locations show the new server’s IP address, the switch has worked.
- Clear the caches. Clear your caching plugin, your host’s cache and Cloudflare’s cache if you use it.
- Re-save permalinks. Go to Settings → Permalinks and click Save Changes without changing anything. This fixes most “page not found” errors after a move.
- Check Google Search Console. Your domain hasn’t changed, so you don’t need to tell Google anything. Just watch the Pages report for new errors over the next week.
- Remove Migrate Guru from both sites. You don’t need it anymore.
- Keep the old hosting for 1–2 weeks. It’s your safety net while DNS settles everywhere. Download a final backup from it, then cancel.
Once you’re settled, it’s a good time to check your speed on the new host. Our guide to speeding up a slow WordPress site has the quick wins.
Common problems and quick fixes
| Problem | Likely cause | Fix |
| “Error establishing a database connection” | Wrong database details in wp-config.php | Ask the new host to check the database name, user and password in wp-config.php |
| Pages show “404 not found” | Permalinks not rebuilt | Settings → Permalinks → Save Changes |
| “Your connection is not private” | SSL not issued yet on the new host | Turn on the free SSL in the new host’s dashboard; wait a few minutes |
| “Too many redirects” | SSL settings clash, often with Cloudflare | In Cloudflare, set SSL/TLS to Full instead of Flexible |
| Emails stopped arriving | MX records lost when nameservers changed | Re-add the MX, SPF and DKIM records at the new DNS provider |
| Some visitors still see the old site | DNS hasn’t updated for their provider yet | Wait up to 48 hours; both sites are identical, so no harm done |
| Migrate Guru stops partway | A security plugin or firewall blocks it | Pause the security plugin on both sites, or use the FTP/cPanel option |
Related guides: WordPress Troubleshooting: How to Fix the Most Common Errors
FAQ
Will moving hosts hurt my Google rankings?
Not if your domain and URLs stay the same, which they do with this method. Google only sees that your site now loads from a different server. A faster host can even help a little. Just make sure SSL works right after the switch and watch Search Console for errors that week.
How long does a WordPress migration take?
The copy itself usually takes under an hour for small and medium sites. Plan for an afternoon in total, including testing. DNS can then take a few minutes to 48 hours to update everywhere, but your site stays online the whole time.
Is Migrate Guru really free?
Yes. There are no paid upgrades. The limits are 200 GB per site and 5 different sites per account each month, and it can’t move sites to or from a local computer.
Do I need to move my domain too?
No. Your domain can stay at its current registrar. You only change where it points (the A record or nameservers). Transferring the domain is a separate, optional job you can do later.
What if the migration fails?
Nothing happens to your live site, because it’s never touched. Check the error email, pause any security plugin, and try again, or use Migrate Guru’s FTP/cPanel option. If it still fails, ask your new host’s support. Many will do the move for free.
Should I let my new host migrate the site instead?
If they offer it free, yes, it saves time. But still test the copy using the hosts file before you switch DNS, and handle the email records yourself. Hosts copy the website, not always your email setup.
Final word
A zero-downtime move comes down to one rule: build and test the new site first, switch last. Lower your TTL a day early, copy the site with Migrate Guru, check it privately through your hosts file, then point the domain. Look after SSL and email straight after the switch, and keep the old host for a couple of weeks as your safety net.
If you’re moving because your current plan feels slow or limited, see shared hosting vs VPS before you pick the new one, so you only have to move once.


