The Best Website Migration tool for WordPress

Moving a WordPress site can take ten minutes, or it can turn into the afternoon where you start questioning your career choices. Most of us have had both.

This thread split the community more cleanly than most. One camp trusts a migration plugin and doesn’t look back. The other camp thinks plugins are the thing that goes wrong, and moves everything by hand. A third camp is newer: agency owners handing the whole process to an AI agent with SSH access, then reviewing the results.

This post is a summary of a Tuesday Toolbox discussion inside The Admin Bar community, where agency owners shared what they use to migrate WordPress sites and why they trust it.

The Most Mentioned Migration Approaches

These came up repeatedly in the discussion:

• Migrate Guru
• Manual
• AI Agents
• All-in-One WP Migration
• Duplicator
• ManageWP
• BackupBuddy

A number of other tools came up as well (we’ll get to those).

Why Agencies Choose These Migration Tools

Migrate Guru

The most-recommended plugin, and the one people describe as dependable.

Migrate Guru came up more than any other plugin in the thread. The praise was short and consistent, which is its own kind of endorsement.

“Nothing beats Migrate Guru for reliability.”

Greg Dietrich

Greg has tried dozens of options over the years. He noted it can be a bit slow, since it backs up to BlogVault’s servers first and then deploys to the new location, but he thinks that’s part of why it’s reliable and gentle on server resources.

Sam Lomeli described it as smooth and able to handle almost any size site, and pointed out it comes from the BlogVault and WP Remote team. Tim Dickinson called it “so easy to use and free.” Nate Hoffelder said it “works 99% of the time.” Marc Bijl, Scott Macon, Adam Wright, Jeffrey Sung, Craig Caruso, Richard Toupin, and Melanie Barkdull Adcock all use it, and Marc Hyde runs it as his second choice behind SiteGround’s migrator. Matthew Granat added that he’s “never looked back” since being pointed to it.

Even some manual-migration folks keep it around. Dan Lockcuff has used it on simple sites but says rsync is his real friend on large, complicated ones. Nick Sanders reaches for it on large sites after trying All-in-One and Duplicator.

Best fit: agencies who want a free, hands-off migration that works across most hosts without much setup.

Manual

Copy the files, move the database, fix the URLs.

A big chunk of the thread skips plugins entirely, and the reasons were nearly identical.

“Migrating manually is simple and straightforward in 99% of cases: copy files, export/import the database, adjust wp-config and sometimes htaccess, and replace the URL in the database if necessary.”

Nazar Hotsa

Nazar added a practical tip: some plugins, like Elementor, have their own URL search-and-replace tool that needs to run on top of the database replace, but “that’s just another 10-second job.”

Kristjan Koppel’s version is a three-step method: copy the files, use WP-CLI to export and import the database, and run a search-replace for URLs (including inside serialized data). Maurice Hason cited reliability, no extra plugin bloat, and full control. Alison Donnellan and Alex Celeste agreed. Alex said he’s done it so many times creating local copies that it’s the most straightforward route, and he wouldn’t trust a plugin to get everything right.

Alison’s take was balanced: “Plugins aren’t necessarily bad, if they make it easier to do then it solves a problem.” She just prefers to avoid the occasional problems plugins introduce, especially on poor hosts.

For those who go further, Patrick Gallagher’s team handles migrations that are either enormous (hundreds of sites) or extremely complicated (live WooCommerce stores with near-zero downtime). His view: in those cases you shouldn’t lean on a plugin, and the right way is server-side tooling like scp and rsync. Dan Lockcuff, Rob Marlbrough, and David Appleby agree. David migrates server to server with SSH and rsync, usually into GridPane, tests before switching DNS, and uses GPT to help with the commands. Rob does rsync plus MySQL directly between servers, “no matter the stack.”

Nate Hoffelder’s “cleaner” approach is worth knowing: migrate only the database and the wp-content folder, build a fresh WordPress install on the new server, then connect it to the uploaded database. Many hosts add their own files, and this is the best way to leave those behind. Vanessa Wood pointed out that with SSH and WP-CLI on both ends, this is only “a handful of commands.”

Rachelle Wise prefers manual via SSH or cPanel and falls back on a backup plugin when she can’t get the access she needs.

Best fit: agencies comfortable with SSH, WP-CLI, or cPanel who want full control and the cleanest possible result, especially on large or high-stakes sites.

AI Agents

The newest approach in the thread, and the one that surprised people.

A handful of members described handing migrations to Claude with SSH access. What stood out was how careful they were.

Vanessa Wood built her process incrementally. She did “heaps of migrations manually first,” then handed over one step at a time, with Claude logging each run and building the skills and tools as they went. Now an agent on her own VPS stack clones the site, runs the search-replace, checks SSL, MX, and TTL, runs a smoke test, and then pings her for approval before flipping DNS in Cloudflare. The old site stays live so she can flip back instantly. Her reason for trusting it: “it’s MY process, part scripted and part skilled up.”

Stephan Wik’s version has Claude dump and import the database, rsync the media, run the search-replace, clean up, and verify the migration before the DNS switch. If DNS is on Cloudflare, it can handle that through the API too. His caveat: have plenty of backups in case things go “pear-shaped.”

Rachelle Wise finds Claude “amazingly helpful” over SSH or cPanel, and said it can do the whole thing if it has full access on both ends. Patrick Gallagher noted that server-side tooling used to be over many people’s heads, but “everyone has super powers with Claude now.”

Best fit: agencies who already know how a migration should work and want to systematize it, with an approval gate before DNS changes and a rollback path.

All-in-One WP Migration

The long-time favorite, with a licensing headache.

All-in-One came up from members with years of loyalty to it.

“All in one WP migration. Been using it for years and it never ever fails.”

Vernita Kruger

Carl Kruck has used it “on dozens of websites” and also uses it to back up to his pCloud account. Amanda Lewensky and Uschi Rapp both pay for it, and Amanda takes manual backups on top. Kenson Clarke, Tye Brown (as his number two), and Nick Sanders (as his first choice) also use it.

The complaints were about licensing, not function. Amanda noted a recent renewal invoice of $150, despite only having it installed on one site, with the rest still running her original lifetime license. “They really need to sort out the licensing.” Andrew Thomas said he uses an older version from before a size limit was added.

Best fit: agencies who value a simple import/export workflow and have a license arrangement they’re comfortable with.

Duplicator

Reliable, with the same pricing complaint.

Duplicator Pro earned strong reliability marks. Surajit Sen Sharma said Duplicator Gold “never failed me, even from multisite to single.” Mark Collard said it always works. Jake Hundley runs UpdraftPlus and Duplicator Pro together.

Tye Brown said it’s never failed on any server setup he’s tried, but he’s looking for a replacement: after an ownership change, his renewal is $100 more than when he started, though they lower it when he complains. He likes that he can work on other jobs while it runs, and that it performs various database checks along the way.

Best fit: agencies who want a dependable, full-featured migration plugin and are willing to watch renewal pricing.

ManageWP

The clone-from-the-dashboard option.

Nate Hoffelder called ManageWP the easiest: back up the old site, set up the new one, and clone from one to the other. His tip: the old and new sites can’t both have “www” in the URL. Cami MacNamara and Moydul Haque both use it and like it.

Rob Marlbrough was less enthusiastic. He said ManageWP cloning “works ok” but often requires staging subdomains and a search-replace.

Best fit: agencies already managing sites through ManageWP who want a built-in clone.

BackupBuddy

A cautionary tale about a tool people love that may be running out of road.

David Innes has used it since around 2011 (it’s been through several rebrandings, including iThemes BackupBuddy, SolidBackups, and now Kadence Backups). He works on a lot of existing sites, sometimes testing and re-uploading up to ten a day, and what he loves is that it makes a single .zip file and has a sophisticated installer. His point: “your backup is only as good as your ability to restore it.” Moving a site from local to live, he said, rarely takes more than a few minutes, with no need to spin up an empty WordPress first.

But he’s now looking for a replacement. The standalone version seems to have stalled in favor of a cloud-based backup, and it can struggle on the weakest hosting. He still has archives dating back to 2011.

Tim Taricco agreed completely, calling it the simplest, most reliable backup plugin he’s found, though he uses Migrate Guru for migrations. Cami MacNamara still has a lifetime license and uses it when client hosting gives her trouble.

David’s criteria are worth noting if anyone has suggestions: a single .zip archive and a competent installer.

Best fit: existing license holders doing local-to-live workflows. For new setups, the stalled development is worth weighing.

Notable Mentions

These also came up in the thread:

• UpdraftPlus: Nazar Hotsa’s favorite plugin, but he only reaches for it when he doesn’t have hosting control panel access. Jake Hundley pairs it with Duplicator Pro.
• WPVivid: Linus Ahimsa and Shawn McGinnis use it, and Linus says even the free version is good enough
• WP Migrate Pro: James Rice’s pick
• ASE Pro: Wibowo Sulistio uses its backup and migration feature because it can do a full site or just the parts you need, including posts of a certain post type and their related data
• SiteGround Migrator: Marc Hyde’s first choice, with Migrate Guru second
• BlogVault: Rob Watson and Melanie Barkdull Adcock use it (it’s the service behind Migrate Guru). Rob also noted Pantheon has its own migrator plugin that makes moving to Pantheon easy.

Patterns We Noticed

A few things stood out across the thread:

• The plugin vs. manual split is real, and it’s about trust. The manual camp isn’t against convenience. They’ve seen plugins fail on awkward hosts, and they want to know exactly what happened. The plugin camp has found one that works and doesn’t see a reason to leave.
• Migrate Guru is the closest thing to consensus. For plugin users it’s the name that came up most, and most of the praise was about reliability rather than features.
• The move itself is rarely the hard part. Tobias Johansson made the sharpest point in the thread: the real problem is the two timelines, a new dev site and a live site the client keeps adding content to. Ben Wade’s advice was to set clear conditions up front and warn that there may be quick hiccups at migration time, especially if multiple people are making changes behind the scenes.
• Licensing and renewal creep is pushing people around. Duplicator and All-in-One both came up with complaints about pricing and licensing changes, even from happy users.
• Server-side skills are getting more accessible. Several members said AI tools have made rsync, WP-CLI, and SSH approachable for people who weren’t comfortable with them before. The approach that worked wasn’t blind automation. It was building up gradually, with approval gates and verification before DNS changes.
• Safety habits show up everywhere. Test before switching DNS. Keep the old site live for an instant flip back. Take backups first. These came up from manual and AI users alike, and from plugin users too.
• Fresh installs give cleaner results. Nate’s migrate-only-the-database-and-wp-content approach is the same instinct behind the manual camp: don’t drag along files you didn’t choose.

How to Choose the Right Migration Method

These questions can help narrow it down:

• How much access do you have to the old and new hosts (SSH, cPanel, or just WordPress admin)?
• How large and how complex is the site? Is it a live WooCommerce store with zero-downtime needs?
• Are you migrating one site, or doing this regularly across many?
• Will the client keep editing content during the move? If so, how will you handle the content freeze?
• Do you want to migrate everything, or just the database and wp-content?
• Are you comfortable with the plugin’s licensing and renewal pricing?
• If using an AI agent, what’s your approval gate before DNS changes, and what’s your rollback plan?

Frequently Asked Questions About WordPress Site Migration

What is the best WordPress migration plugin? Migrate Guru was the most recommended plugin in this community, mainly for reliability, and it’s free according to members. All-in-One WP Migration and Duplicator were the next most mentioned, and both have strong reliability records but come with licensing and renewal complaints.

Should I use a plugin or migrate manually? It depends on your access and the site’s complexity. Plugins make sense when you don’t have SSH or control panel access, or when you want something quick. Manual or server-side migration (copy files, move the database, run a search-replace) gives you more control and avoids plugin issues, and is what several members prefer for large or complicated sites.

What’s the cleanest way to migrate a WordPress site? One member’s approach: migrate only the database and the wp-content folder, build a fresh WordPress install on the new server, and connect it to the uploaded database. This leaves behind any extra files the old host added. It’s more work than a plugin, but it can be done in a handful of commands with SSH and WP-CLI.

Can I use AI to migrate WordPress sites? Several members do, with SSH access and a careful process. The pattern: learn the process manually first, hand over one step at a time, and keep an approval step before DNS is switched. Verification, backups, and an easy rollback (keeping the old site live) were part of every setup described.

How do I avoid problems when a client keeps editing the live site during a migration? This came up as the hardest part of many migrations. The advice was to set clear expectations in advance, agree on a content freeze if possible, and warn clients that there may be small issues at the moment of cutover, especially when multiple people are making changes.

What should I check before switching DNS? Members mentioned testing the new site before the cutover, checking SSL, MX records, and TTL, running a smoke test, and keeping the old site live so you can switch back immediately if something’s wrong.