Moving a WordPress site means transferring its files and database, then checking that the new copy works before traffic is sent to it. A migration plugin can reduce manual work, but it cannot replace a separate, restorable backup or a post-move check.
Quick answer: choose a full-site migration tool when moving a complete site between hosts; use a database-focused tool when your workflow is staging and development; and choose a backup tool only if its migration process covers the files, database, and URL changes you need. Test the destination before changing DNS.
How to choose a WordPress migration plugin
- Full-site transfer: does it move the database, uploads, themes, plugins, and relevant configuration?
- Destination limits: check archive size, server memory, execution time, PHP version, storage, and multisite support before starting.
- URL and serialized-data handling: a domain change requires safe database search-and-replace. Avoid editing a raw SQL file with a simple text replacement because serialized settings can be damaged.
- Rollback: make an independent backup and know how to restore it before overwriting a live destination.
- Workflow: a one-time host move, a staging push/pull, and a backup restore are different jobs; pick for the job you have.
WordPress migration plugins compared
| Tool | Best fit | Check before choosing |
|---|---|---|
| Duplicator | Packaging a site for a controlled move or clone | Confirm the package builds successfully and that the destination can extract/import it. Review the current documentation for the workflow and host requirements. |
| All-in-One WP Migration | Exporting a site to an archive and importing it on another WordPress install | Check the current import and file-size limits for your version and hosting setup. Do not assume an extension or limit is included in every installation. |
| Migrate Guru | A guided host-to-host transfer for owners who prefer a wizard | Check whether your source/destination configuration is supported and read the provider’s current requirements. Keep an independent source backup. |
| WPvivid Backup & Migration | Owners who want backup and migration functions in one plugin | Check storage destination, backup completeness, and the exact restore/migration steps. A backup stored only on the site being moved is not an independent copy. |
| WP Migrate | Developer workflows that push or pull database, media, theme, and plugin data between environments | It is a workflow tool with configuration choices; verify which components and add-ons your task requires, and protect destination data before a push. |
This is a fit guide, not a lab ranking: no timed migration test was performed for this article. Plugin versions, plan features, and host limits change, so confirm them in the linked product documentation before you begin.
Which tool should you use?
For a complete site move
Start with a tool designed to package or transfer the whole site, such as Duplicator, All-in-One WP Migration, Migrate Guru, or WPvivid. Compare the required steps with your site size and host restrictions. If you are moving to a new domain as well as a new host, confirm how the tool handles old URLs, redirects, SSL, and serialized data.
For staging or developer push/pull work
WP Migrate is built around moving selected WordPress data between environments. That can suit a developer who needs to pull a production database to a local or staging copy, or push approved changes back. It is not interchangeable with a simple one-click backup; inspect the transfer scope and protect data at both ends.
For backup and restore
Choose a backup tool only after confirming that it can restore the files and database you need, and that you can access the backup if the original site is unavailable. Keep a copy away from the site itself. A database-only backup is not a complete site backup.
A safer migration workflow
- Record the source: note the current site URL, WordPress and PHP versions, DNS settings, email setup, scheduled tasks, and any special integrations.
- Create and verify a separate backup: include both the database and site files, store it off-site, and check that the archive is complete and accessible.
- Prepare the destination: confirm storage, PHP/database compatibility, SSL, and access. Avoid overwriting a destination that contains data you need.
- Run the transfer on a staging or temporary URL: follow the plugin’s current instructions. If changing domains, use a migration method that safely updates database URLs.
- Check the new copy: test the homepage, several posts and pages, images, forms, login, plugins, redirects, canonical URLs, and mobile rendering. Check browser errors and the site’s logs.
- Switch traffic only after validation: plan the DNS change and keep the old site available during propagation. Recheck the live domain, HTTPS, forms, and important URLs after cutover.
- Keep the rollback path: do not delete the source or backup until the new site has been verified and the owner is satisfied.
Common migration problems to prevent
- Broken images or uploads: check that the uploads directory transferred and that its URLs work on the destination.
- Login loops or mixed content: verify the WordPress Address and Site Address, HTTPS certificate, and any cached old URLs.
- Missing forms or plugin settings: compare the active plugin list and test important functions rather than relying on the homepage alone.
- Unexpected content loss: review the destination before import; some migration workflows replace destination tables instead of merging them.
- Search visibility changes: keep URLs where possible. If URLs must change, map old to new pages with direct redirects and check canonical tags and sitemaps after launch.
Official documentation
- WordPress: Tools Export screen — what the built-in WXR export contains and how it is imported.
- Duplicator documentation — package, restore, storage, and troubleshooting guides.
- All-in-One WP Migration user guide — archive export and import workflow.
- WPvivid on WordPress.org — current plugin description and support information.
- WP Migrate — current product scope for environment-to-environment migrations.
If your destination is Bluehost, see our guide to configuring a domain and uploading a WordPress site on Bluehost. For a move involving a different host, use that provider’s current migration and DNS instructions.
If you are choosing a destination host, compare its current migration process and renewal cost before moving. See our Cloudways managed hosting overview and our Hostinger vs Bluehost comparison for current provider details. For a WooCommerce destination, read the Cloudways ecommerce overview as well.
Reviewed October 2026. Product capabilities and host requirements can change; verify current documentation for your WordPress version, plugin version, and hosting plan before migrating. This guide does not claim hands-on tests of these plugins.
