What Migrate Guru Actually Is
Migrate Guru is a free WordPress plugin built by BlogVault. It does one job: it moves a WordPress site from one host to another. According to the plugin's own listing on wordpress.org, it has more than 200,000 active installs. It also holds a 4.9-star rating across 1,621 reviews. Those numbers hold up because the mechanism behind the tool is genuinely well engineered. Instead of running the transfer through your server's own PHP process, Migrate Guru offloads the entire job to BlogVault's servers. That's why it rarely times out on large sites. The heavy lifting happens off your host, not on it.
It works over FTP and SFTP. It also has dedicated, one-click integrations with Bluehost, SiteGround, DreamHost, and Automattic's own hosting dashboards. Data from those host partnerships shows Migrate Guru is the engine quietly running inside several hosts' built-in "migrate my site" buttons. If you've ever clicked a one-button migration tool on a mainstream host and wondered what was actually happening behind the scenes, there's a decent chance it was this.
And it's free, for sites up to 200GB. For most WordPress sites — a typical business site runs well under 2GB — that ceiling will never be the limiting factor.
How the Transfer Actually Works, Step by Step
It's worth understanding the mechanics, because they explain both why the tool is reliable and why it can't do what some people expect it to do. When you install Migrate Guru on your source site and target site, the plugin doesn't move files directly from server A to server B. Instead, it packages your database and files, hands that package to BlogVault's own infrastructure, and BlogVault's servers push the content onto the destination host. That middle hop is the whole trick.
Most free migration plugins run entirely inside your hosting account's PHP process. On a shared host with a 30-second or 60-second script execution limit, that matters a lot. A database with 40,000+ posts and a media library pushing past 10GB will often time out partway through. You're left with a half-migrated site and no clear way to resume. Migrate Guru avoids that failure mode. The transfer runs on BlogVault's servers, not yours. Your host's execution limits never come into play for the bulk of the job.
That architecture also explains the free-tier cap. Running thousands of other people's migrations through your own infrastructure costs real server time and bandwidth. A hard limit of five free migrations per user per month is how BlogVault keeps the offer sustainable. Without it, the free tier would turn into an unlimited hosting-migration service for agencies.
Where It Actually Falls Short
Compared to other migration tools, Migrate Guru's limits are consistent and predictable rather than random:
- Five migrations per registered user, per month, on the free tier. Fine for a one-off move. Not fine if you manage a dozen client sites and migrate several in the same week.
- No localhost-to-live support. If you're building a site on a local dev environment and want to push it to production, this tool isn't built for that workflow — it migrates live-to-live.
- SFTP debugging can get messy on hosts with unusual configurations. A non-standard SFTP setup on a smaller boutique host can make the transfer stall, usually tracing back to a permissions mismatch on the target directory. That's not a Migrate Guru bug exactly — it's what happens any time a transfer tool meets a host that doesn't follow the usual conventions.
None of that makes it a bad tool. It makes it a tool with a narrow, well-defined job.
The One Job It's Built to Do — and Stop Doing
Here's the distinction that matters, and it's the reason this article exists instead of just being another "best migration plugin" roundup. Migrate Guru is architected to do a single transfer and then be done. It has no retention window. It doesn't keep a rolling history of your site. It doesn't run again next week unless you manually trigger it again. The job finishes, the copy lands on the new host, and that's the end of its involvement with your site.
You can see this reflected in BlogVault's own product lineup. BlogVault, the company behind Migrate Guru, sells BlogVault itself as a completely separate product. That product is built around continuous, automated backups with 30 days (or more, on paid tiers) of restore-point history. Per the company's own migration guide, migration and ongoing backup are treated as two different jobs that happen to share underlying transfer technology. That's not an accident. It's the same split we're arguing for here, confirmed by the company that built the free tool in question.
In other words: Migrate Guru moving your site is not the same as your site being protected. The move is the easy part. What happens in month three, when a plugin update breaks your checkout page and you need to roll back to how things looked yesterday — not last time you happened to migrate — is the part Migrate Guru was never asked to solve.
What You Actually Need After the Move
Site owners who've just landed on a new host often assume the job is finished the moment the move completes. In reality, the move is roughly the first 10 minutes of a much longer relationship with that hosting environment. There's DNS propagation, a new server stack, sometimes a new PHP version. There's often a different backup policy too — or no backup policy at all.
A recurring pattern: sites that migrate hosts and then go two or three months without independent backups are the ones most likely to end up asking "I made a change and now I can't undo it." A host-level backup, when one exists at all, is usually a once-daily snapshot. It's kept for a handful of days, stored on the same infrastructure as the site itself. That's the single point of failure you don't want if that host has an outage.
The Cybersecurity and Infrastructure Security Agency puts this plainly in its own data-backup guidance. A sound backup strategy keeps copies in a location separate from the original system. That separation exists specifically so one failure — a hack, a bad update, a hosting outage — doesn't take out your only copy along with the live site. That's the gap a one-shot migration tool was never going to close, by design.
This piece cross-checks that pattern against BlogVault's own published documentation and the wordpress.org plugin listing.
A specific mistake repeats itself across migrations often enough to be worth naming. A site owner migrates in 2026. Everything looks fine for a few weeks. Then a plugin update or a theme change breaks something on the new host. Without an independent backup from after the migration, the only "undo" option left is the state Migrate Guru captured at move time. By then that snapshot might be two or three months stale, missing every order, comment, and content update made since. That's not a hypothetical — it's the exact gap a one-shot migration tool leaves open.
Practically, after you've migrated with Migrate Guru or any similar tool, the sequence we recommend is:
- Confirm the new site loads correctly and DNS has fully propagated (usually within 24 to 48 hours).
- Set up an independent, off-host backup schedule — daily, at minimum, for anything with a checkout flow or regular content updates.
- Store backups somewhere other than the new host's own disk, so a host-level incident can't take your backups down with your site.
- Test a restore at least once. A backup you've never restored from is a backup you don't actually know works.
Migrate Guru vs. Manual Migration vs. Paid Tools
It helps to see where Migrate Guru sits against the two alternatives most site owners actually consider.
Manual migration means exporting a database via phpMyAdmin, copying files over SFTP by hand, and manually updating the site URL in the database. It gives you full control and costs nothing in licensing. It also takes real technical skill. A mismatched database collation, a missed `wp-config.php` edit, or a forgotten `.htaccess` file is enough to leave the new site broken. We've watched experienced developers lose 2-3 hours to a migration that a plugin would have finished in under 30 minutes. For anyone without server-admin experience, manual migration is a genuine risk, not just a time cost.
Paid migration services have a host's support team or a freelancer do the move for you. That removes the technical risk but adds a cost, typically somewhere between $50 and $300 per site depending on complexity. You're also waiting on someone else's schedule. For an agency moving one site a quarter, that's a reasonable trade. For a site owner who just wants their one site moved today, it's often overkill.
Migrate Guru sits in the middle: free, automated, no server-admin skill required, and done in the time it takes to configure a plugin rather than hours of manual work. The trade-off isn't cost or difficulty — it's scope. You get a reliable, well-tested one-time move and nothing else. That's a fair trade for most site owners, as long as you go in knowing exactly where its job ends.
Our Take, Plainly
Migrate Guru earns its reputation for what it does: a free, reliable, one-time move with no timeout headaches. We're not here to argue you should pay for something it already does well for free. We're here because too many sites treat "the migration is done" as "the site is protected," and those are not the same sentence. On a site with any real traffic, revenue, or client dependency, the ten minutes it takes to set up ongoing backups right after a migration is the cheapest insurance you'll buy this year.
At BackupYourSite, that's the specific gap we built for: automated, off-host backups that start the day your migration finishes, not the day something goes wrong. See how the setup works — most sites are fully protected inside the same 10 minutes it takes to verify the migration landed correctly.
If you're weighing a different migration path first, two related reads worth checking: our breakdown of All-in-One WP Migration's free import limit, and our guide to moving WordPress to a new host without a maintenance window.
Frequently Asked Questions
Is Migrate Guru actually free?
Yes, for sites up to 200GB, with a cap of five migrations per registered user per month. Larger or more frequent migration needs typically mean looking at BlogVault's paid tiers or a different tool.
Does Migrate Guru back up my site?
No. It performs a one-time transfer from one host to another. It does not keep a restore-point history, does not run on a schedule, and was not designed to protect a site on an ongoing basis — only to move it once.
Can I use Migrate Guru to push a local development site live?
No. Migrate Guru is built for live-to-live transfers between two hosted environments, not localhost-to-live pushes. For that workflow you'll want a different plugin or your host's deployment tooling.
What should I do right after migrating with Migrate Guru?
Confirm DNS has fully propagated, then set up an independent off-host backup schedule before you make any further changes to the new site. Test a restore once so you know it actually works when you need it.
Why does BlogVault sell a separate backup product if Migrate Guru is free?
Because migration and ongoing protection are different jobs. BlogVault's own migration guide treats them as two separate products built on shared transfer technology — a move tool and a protection tool, sold and built separately because they solve different problems.
How long does a Migrate Guru transfer usually take?
Per the plugin's own documentation, most sites under 2GB finish in under an hour, and the server-side architecture means it keeps running even if you close the browser tab. Sites approaching the 200GB ceiling can take considerably longer, simply because of the raw amount of data being moved.
Does Migrate Guru work with every host?
It works with most hosts over FTP or SFTP, plus one-click integrations on hosts like Bluehost, SiteGround, DreamHost, and Automattic-managed WordPress hosting. Hosts with unusual SFTP configurations or aggressive security rules can occasionally need manual troubleshooting.