Reviewed by the SEOPointz team · Last reviewed June 2026. We’ve run live host-to-host migrations on WordPress and verified the free-migration terms below directly with each provider. SEOPointz may earn a commission from some links; it never changes what we recommend.
Switching web hosts feels riskier than it usually is. The fear is the same one everyone has: you click a button, your site disappears for a day, your rankings tank, and the contact form quietly stops emailing you. In practice, a clean migration is mostly about sequencing — doing a few unglamorous steps in the right order so that the moment your domain points to the new server, the site is already sitting there ready and tested. This guide walks through how to move a site without the downtime, the broken links, or the “why are my images all 404ing” panic.
Decide who actually does the move
You have three realistic options, and the right one depends on how much you trust yourself with a database. A free managed migration from the host is the lowest-effort path: their team copies everything and tells you when it’s ready. A plugin migration (tools like Duplicator, All-in-One WP Migration, or a host’s own migrator) automates the export-import and usually runs a search-and-replace on your old URLs automatically. A manual migration — copying files over FTP/SFTP and importing the database by hand — gives you the most control and is genuinely the safest route for large or unusual sites, where plugins tend to choke on file-size caps.
One honest caveat about the free option: most hosts cap it. Bluehost, for example, includes free WordPress migration but only within the first 30 days after signup. SiteGround offers a free transfer on every plan plus its own WordPress Migrator plugin, and Hostinger advertises free, largely automated migrations handled through a support request. Read the fine print before you assume “free” means “unlimited and forever.”
Back up everything before you touch anything
This is the one step with no acceptable shortcut. Take a full backup of both your files and your database, and download it somewhere off the server — not just to a backup plugin folder that lives on the same host you’re about to leave. If anything goes wrong mid-move, this is your undo button. While you’re in there, do some housekeeping: delete inactive plugins and themes, and update WordPress core, themes, and plugins to current versions. Stale, deactivated code is the most common source of conflicts on the new server, and there’s no reason to drag it along.
Build and test on the new host before you flip DNS
The trick to zero downtime is that you don’t migrate the live site — you migrate a copy, get it working privately, and only then send visitors to it. Move your files and database to the new host while your domain is still pointing at the old one. Then preview the new copy using a temporary URL or by editing your local hosts file so only your machine resolves the domain to the new server. Click through it like a visitor: load the homepage, a few posts, the checkout or contact form, and anything that talks to a third party. Fix problems here, where nobody can see them.
Update URLs, then point the domain
If your domain or paths changed at all, run a search-and-replace across the database so old URLs become new ones — most migration plugins do this for you, but verify it actually happened rather than assuming. Once the copy passes its test drive, change your DNS (usually the A record or nameservers) to point at the new host. Propagation can take anywhere from a few minutes to a day, during which some visitors hit the old server and some hit the new one. Because both copies are live and identical during that window, nobody sees an error — that overlap is the seamless part.
The post-migration checklist nobody enjoys
Your work isn’t finished when the site loads. Clear every cache — the plugin cache, the host’s server cache, and any CDN — or you’ll spend an hour debugging a “bug” that’s just a stale copy. Confirm SSL is active so you’re not throwing “not secure” warnings, send a real test through every form, and re-check internal links and images. Resubmit your sitemap in Google Search Console so crawlers re-index from the new server quickly. Keep the old hosting account running for a week or two as a safety net before you cancel it.
| Approach | Best for | Main limitation |
|---|---|---|
| Free managed migration | Anyone who qualifies for the host’s offer | Time windows and per-site limits (e.g. 30-day cap on some hosts) |
| Migration plugin | Small to mid-size WordPress sites | Free tiers cap upload/file size; large sites can fail |
| Manual (FTP + database import) | Large, complex, or non-standard sites | Requires comfort with files and databases |
Frequently asked questions
Will migrating my site hurt my SEO?
Not if you keep the same domain and URL structure and the content stays identical — Google is moving servers, not pages. The risks come from broken links, missing redirects when paths change, or extended downtime, all of which the steps above are designed to prevent.
How long does a website migration take?
The copy-and-test work is often done in a few hours for a typical site. The variable is DNS propagation after you flip the domain, which can range from a few minutes to roughly 24–48 hours depending on your old TTL settings.
Should I cancel my old hosting right away?
No. Keep it active for at least a week or two after the move so you have a working fallback while DNS finishes propagating and you confirm everything on the new host behaves correctly.
If you’re still choosing where to land, it’s worth weighing whether hands-off support is worth paying for in our look at the pros and cons of managed web hosting, and our in-depth Hostinger review covers one of the more popular migration-friendly hosts in detail.
