Moving a WordPress site to a new host or domain is usually the fiddliest job in WordPress. BackupEase Pro turns it into a pull migration: the new site fetches everything from the old one using a single-use key, then rewrites URLs and paths for you.
One-click migration requires BackupEase Pro on the destination site. The source site needs BackupEase installed and active so it can generate a migration key. See Installing BackupEase if you still need to set that up.
How pull migration works
Instead of exporting a file and importing it by hand, the destination site connects to the source over HTTPS and pulls the data across. Along the way, BackupEase:
- Authenticates using a single-use migration key, so the link cannot be reused after the migration.
- Runs a serialization-safe search-and-replace to update the old site URL and paths to the new ones.
- Performs an automatic
wp-config.phprewrite so the new site connects to its own database.
On the source site
- Open BackupEase Sign in to the site you are moving from and open the BackupEase dashboard.
- Generate a migration key In the Migration section, generate a new single-use migration key.
- Copy the key and site URL Copy the key, and note the source site URL. You will paste both into the destination.
On the destination site
- Start with a clean WordPress Set up a fresh WordPress install at the new location and activate BackupEase Pro.
- Open the Migration tab In the BackupEase dashboard, go to Migration and choose to pull from another site.
- Paste the key and source URL Enter the source site URL and the single-use migration key you generated.
- Start the migration Begin the pull. BackupEase transfers the files and database, then runs the search-replace and config rewrite. Keep the page open until it finishes.
The transfer is chunked and adapts to each server's limits, so it works on shared hosting where a single large upload would time out. If a step is interrupted, reopen the dashboard to continue.
After the migration
- Log in to the new site using the credentials from the source site.
- Re-save permalinks under Settings › Permalinks.
- Check URLs and SSL, then clear any cache or CDN.
- Spot-check pages, images, and forms to confirm the search-replace caught everything.
Once a migration key has been used, it will not work again. If you need to run the migration a second time, generate a fresh key on the source site.

