Cloud Migrate
Cloud Migrate copies a complete WordPress site — database, media, plugins and themes — from one host to another. You install the plugin on both sites, generate a connection key on the site you are moving from , paste it into the site you are moving to , and press Start. The destination pulls everyth
Cloud Migrate copies a complete WordPress site — database, media, plugins and themes — from one host to another. You install the plugin on both sites, generate a connection key on the site you are moving from , paste it into the site you are moving to , and press Start. The destination pulls everything across by itself.
There is no export file to download, nothing to upload by hand, and no need for FTP, SSH or database credentials.
Built for real hosting
Most migration failures come from host limits, not from the migration itself. Cloud Migrate is designed around them:
- Resumable, chunked transfers. Work is split into small slices, each one bounded by the host’s own memory_limit and max_execution_time . No single request needs more than a few seconds or a few MB.
- Adapts to what the host can take. It starts at the fastest pace both servers allow, halves it automatically after a failed request, and climbs back once conditions improve. Nothing to configure.
- Batched small-file transfers. Sites with thousands of small files are limited by request count, not bandwidth, so many files are fetched per request and several requests run in parallel.
- Recovers from out-of-memory conditions by reducing the transfer pace and continuing, instead of failing.
- Survives different table prefixes. If the two sites use different prefixes, tables are imported under their original names and wp-config.php is repointed at them (a backup is kept). Tables are never renamed, because WordPress stores the prefix inside user roles and capabilities.
- Handles newer database servers. Collations the destination does not recognise (for example MariaDB 11.4’s uca1400 family) are mapped to the closest supported equivalent.
Safe by default
- Your current administrator account is copied into the migrated database, so you can still sign in afterwards with the same username and password.
- The destination’s original database tables are left untouched until you choose to delete them, so the migration can be undone.