{"id":346625,"date":"2026-08-14T01:19:48","date_gmt":"2026-08-14T01:19:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/easy-migrate\/"},"modified":"2026-08-14T01:19:35","modified_gmt":"2026-08-14T01:19:35","slug":"cloud-migrate","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/cloud-migrate\/","author":15734145,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"3.20.0","stable_tag":"3.20.0","tested":"7.0.4","requires":"5.6","requires_php":"7.4","requires_plugins":null,"header_name":"Cloud Migrate","header_author":"djekanovic","header_description":"Migrate a WordPress site to another host with a single connection key. Install on both sites, pull the migration from the destination side. Works within tight host limits via small, resumable chunks.","assets_banners_color":"216997","last_updated":"2026-08-14 01:19:35","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/djekanovic\/cloud-migrate","header_author_uri":"https:\/\/github.com\/djekanovic","rating":0,"author_block_rating":0,"active_installs":0,"downloads":28,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"3.20.0":{"tag":"3.20.0","author":"djekanovic","date":"2026-08-14 01:19:35"}},"upgrade_notice":{"3.20.0":"

Renamed to Cloud Migrate. Nothing else changes; your settings and any migration in progress are kept.<\/p>","3.19.0":"

Hardens database access and adopts WordPress file-deletion APIs.<\/p>","3.18.2":"

Declares WordPress 7.0 compatibility and adds a translation template.<\/p>","3.18.1":"

Fixes zero-byte files being skipped during transfer. Update on both sites.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3646479,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3646479,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3646479,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3646479,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["3.20.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3646479,"resolution":"1","location":"assets","locale":"","width":1200,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3646479,"resolution":"2","location":"assets","locale":"","width":1200,"height":900},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3646479,"resolution":"3","location":"assets","locale":"","width":1200,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3646479,"resolution":"4","location":"assets","locale":"","width":1200,"height":900}},"screenshots":{"1":"Generate a connection key on the source site, paste it on the destination.","2":"Live progress with transfer speed, estimated time remaining and current chunk size.","3":"Site information panel showing environment and PHP limits with recommendations.","4":"Debug report for diagnosing a problem migration."}},"plugin_section":[],"plugin_tags":[151,2814,4151,4155,58759],"plugin_category":[59],"plugin_contributors":[272946],"plugin_business_model":[],"class_list":["post-346625","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-clone","plugin_tags-migrate","plugin_tags-migration","plugin_tags-move-site","plugin_category-utilities-and-tools","plugin_contributors-djekanovic","plugin_committers-djekanovic"],"banners":{"banner":"https:\/\/ps.w.org\/cloud-migrate\/assets\/banner-772x250.png?rev=3646479","banner_2x":"https:\/\/ps.w.org\/cloud-migrate\/assets\/banner-1544x500.png?rev=3646479","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/cloud-migrate\/assets\/icon-128x128.png?rev=3646479","icon_2x":"https:\/\/ps.w.org\/cloud-migrate\/assets\/icon-256x256.png?rev=3646479","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/cloud-migrate\/assets\/screenshot-1.png?rev=3646479","caption":"Generate a connection key on the source site, paste it on the destination."},{"src":"https:\/\/ps.w.org\/cloud-migrate\/assets\/screenshot-2.png?rev=3646479","caption":"Live progress with transfer speed, estimated time remaining and current chunk size."},{"src":"https:\/\/ps.w.org\/cloud-migrate\/assets\/screenshot-3.png?rev=3646479","caption":"Site information panel showing environment and PHP limits with recommendations."},{"src":"https:\/\/ps.w.org\/cloud-migrate\/assets\/screenshot-4.png?rev=3646479","caption":"Debug report for diagnosing a problem migration."}],"raw_content":"\n

Cloud Migrate copies a complete WordPress site \u2014 database, media, plugins and themes \u2014 from one host to another. You install the plugin on both sites, generate a connection key on the site you are moving from<\/strong>, paste it into the site you are moving to<\/strong>, and press Start. The destination pulls everything across by itself.<\/p>\n\n

There is no export file to download, nothing to upload by hand, and no need for FTP, SSH or database credentials.<\/p>\n\n

Built for real hosting<\/h4>\n\n

Most migration failures come from host limits, not from the migration itself. Cloud Migrate is designed around them:<\/p>\n\n

    \n
  • Resumable, chunked transfers.<\/strong> Work is split into small slices, each one bounded by the host's own memory_limit<\/code> and max_execution_time<\/code>. No single request needs more than a few seconds or a few MB.<\/li>\n
  • Adapts to what the host can take.<\/strong> 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.<\/li>\n
  • Batched small-file transfers.<\/strong> 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.<\/li>\n
  • Recovers from out-of-memory conditions<\/strong> by reducing the transfer pace and continuing, instead of failing.<\/li>\n
  • Survives different table prefixes.<\/strong> If the two sites use different prefixes, tables are imported under their original names and wp-config.php<\/code> is repointed at them (a backup is kept). Tables are never renamed, because WordPress stores the prefix inside user roles and capabilities.<\/li>\n
  • Handles newer database servers.<\/strong> Collations the destination does not recognise (for example MariaDB 11.4's uca1400<\/code> family) are mapped to the closest supported equivalent.<\/li>\n<\/ul>\n\n

    Safe by default<\/h4>\n\n
      \n
    • Your current administrator account is copied into the migrated database, so you can still sign in afterwards with the same username and password.<\/li>\n
    • The destination's original database tables are left untouched until you choose to delete them, so the migration can be undone.<\/li>\n
    • Serialized data is unserialized, rewritten and re-serialized properly \u2014 URLs are also replaced in JSON-escaped and URL-encoded forms, which is what page builders such as Elementor store internally.<\/li>\n
    • Connection keys are signed with HMAC-SHA256, are valid for three hours, and can be revoked at any time.<\/li>\n
    • A built-in debug report shows the environment, host limits, transfer throughput and every logged request. It contains no passwords and no connection keys.<\/li>\n<\/ul>\n\n

      What is transferred<\/h4>\n\n

      The database is always migrated. You choose whether to include media\/uploads, plugins, themes and must-use plugins.<\/p>\n\n

      External services<\/h3>\n\n

      This plugin communicates with the other WordPress site you are migrating to or from<\/strong> \u2014 a site whose address you supply yourself by pasting its connection key. No third-party service is contacted, and no data is sent anywhere else.<\/p>\n\n

        \n
      • What is sent:<\/strong> the connection key you generated, and requests for database rows and files.<\/li>\n
      • When:<\/strong> only while a migration is running, and only to the site the connection key was issued for.<\/li>\n
      • What is received:<\/strong> that site's database contents and files.<\/li>\n<\/ul>\n\n

        No analytics, telemetry, tracking or external API calls of any kind are made. The plugin loads no remote scripts, fonts or images.<\/p>\n\n\n

          \n
        1. Install and activate Cloud Migrate on both<\/strong> the source site and the destination site.<\/li>\n
        2. On the source<\/strong> site, open Cloud Migrate and click Generate connection key<\/em>, then copy it.<\/li>\n
        3. On the destination<\/strong> site, open Cloud Migrate, paste the key, choose what to include, and click Start migration<\/em>.<\/li>\n
        4. Leave the browser tab open while the migration runs. Progress, transfer speed and estimated time remaining are shown live.<\/li>\n
        5. When it finishes, check the site. If everything looks right, use Looks good \u2014 delete backups<\/em> to remove the old tables. If not, use Undo migration<\/em>.<\/li>\n<\/ol>\n\n\n
          \n

          Does this need FTP, SSH or database access?<\/h3><\/dt>\n

          No. The two sites talk to each other over the WordPress REST API, authenticated with the connection key.<\/p><\/dd>\n

          Will I be logged out after migrating?<\/h3><\/dt>\n

          No. User accounts come from the source site, but your current administrator account is copied across with its password hash intact, so the same username and password keep working.<\/p><\/dd>\n

          What if my host is slow or has low limits?<\/h3><\/dt>\n

          That is the case the plugin is built for. It measures each host's limits and sizes its work accordingly, backing off automatically when a request fails and resuming where it left off.<\/p><\/dd>\n

          What happens if a migration is interrupted?<\/h3><\/dt>\n

          Nothing is lost. Progress is saved after every slice of work. Reopen the page and click Resume<\/em>.<\/p><\/dd>\n

          Can I undo a migration?<\/h3><\/dt>\n

          Yes. The destination's original tables are kept until you explicitly delete them. Undo migration<\/em> puts the site back on them.<\/p><\/dd>\n

          Do both sites need the same plugin version?<\/h3><\/dt>\n

          They should. Some transfer optimisations require a matching version on both ends; when versions differ the plugin falls back to a slower but compatible mode and says so in the log.<\/p><\/dd>\n

          Is multisite supported?<\/h3><\/dt>\n

          Not yet. Multisite networks are detected and refused rather than migrated incorrectly.<\/p><\/dd>\n\n<\/dl>\n\n\n

          3.20.0<\/h4>\n\n
            \n
          • Renamed to Cloud Migrate. Your settings, connection keys and any migration already in progress are unaffected.<\/li>\n<\/ul>\n\n

            3.19.0<\/h4>\n\n
              \n
            • Hardened database access: every table name is now validated as a bare SQL identifier before it can reach a query, so a malformed or hostile name from the source site is rejected outright.<\/li>\n
            • Switched file deletion to WordPress's own wp_delete_file()<\/code>.<\/li>\n
            • Removed a redundant load_plugin_textdomain()<\/code> call; translations load automatically since WordPress 4.6.<\/li>\n
            • Documented in code why raw database and byte-range filesystem access are unavoidable for a migration tool.<\/li>\n<\/ul>\n\n

              3.18.2<\/h4>\n\n
                \n
              • Declared compatibility with WordPress 7.0.<\/li>\n
              • Added a translation template at languages\/cloud-migrate.pot<\/code> (161 strings), so the plugin is ready for translators.<\/li>\n<\/ul>\n\n

                3.18.1<\/h4>\n\n
                  \n
                • Fixed: zero-byte files (empty RTL stylesheets, placeholder scripts, index.html<\/code> guards) were reported as unreadable and skipped, because PHP 8 raises an error when reading zero bytes. They now transfer as real empty files.<\/li>\n
                • Skip messages now state the underlying reason instead of a generic \"unreadable\".<\/li>\n<\/ul>\n\n

                  3.18.0<\/h4>\n\n
                    \n
                  • Redesigned the admin screen: card layout, numbered steps, status badges and clearer progress reporting.<\/li>\n<\/ul>\n\n

                    3.17.0<\/h4>\n\n
                      \n
                    • Added: automatic fallback to single-file transfers if the source site cannot serve batch requests, so a migration completes instead of failing.<\/li>\n
                    • Added: the source site now reports PHP fatals as readable messages rather than a generic error page.<\/li>\n
                    • Hardened the source endpoint against a single problem file taking down a request.<\/li>\n<\/ul>\n\n

                      3.16.0<\/h4>\n\n
                        \n
                      • Fixed: out-of-memory conditions during parallel transfers. Batch size now accounts for the memory each in-flight response costs, payloads are released as soon as they are written, and an out-of-memory event automatically reduces the transfer pace and continues.<\/li>\n<\/ul>\n\n

                        3.15.0<\/h4>\n\n
                          \n
                        • Fixed: a large file at the head of the queue could stall the transfer indefinitely.<\/li>\n
                        • Fixed: the file phase could finalize while files were still queued.<\/li>\n
                        • Ticks now return promptly so progress updates in real time.<\/li>\n<\/ul>\n\n

                          3.14.0<\/h4>\n\n
                            \n
                          • Added: small-file batching and parallel requests. Sites made up of many small files migrate dramatically faster.<\/li>\n
                          • Added: transfer throughput, estimated time remaining and guidance on what limits the speed.<\/li>\n<\/ul>\n\n

                            3.13.0<\/h4>\n\n
                              \n
                            • Styled confirmation dialogs in place of browser popups.<\/li>\n<\/ul>\n\n

                              3.12.0<\/h4>\n\n
                                \n
                              • Transfer pace now scales up on capable hosts instead of being capped, with filters to raise the ceiling further.<\/li>\n<\/ul>\n\n

                                3.10.0<\/h4>\n\n
                                  \n
                                • The debug report is now scoped to the current migration only.<\/li>\n<\/ul>\n\n

                                  3.9.0<\/h4>\n\n
                                    \n
                                  • Added: unsupported database collations (such as MariaDB 11.4's uca1400<\/code> family) are mapped to the closest supported equivalent.<\/li>\n<\/ul>\n\n

                                    3.4.0<\/h4>\n\n
                                      \n
                                    • Fixed: exclusion rules no longer skip plugin source files that live in a directory named cache<\/code>.<\/li>\n<\/ul>\n\n

                                      3.2.0<\/h4>\n\n
                                        \n
                                      • Fixed: Elementor dynamic tags with empty settings no longer cause a fatal error after migration.<\/li>\n<\/ul>\n\n

                                        3.1.0<\/h4>\n\n
                                          \n
                                        • URLs are now replaced in JSON-escaped and URL-encoded forms as well as plain text, which page builders rely on.<\/li>\n<\/ul>\n\n

                                          3.0.0<\/h4>\n\n
                                            \n
                                          • Renamed to Cloud Migrate, moved to its own top-level admin menu.<\/li>\n<\/ul>","raw_excerpt":"Move a WordPress site to another host with a single connection key. No FTP, no SSH, no database credentials, no file size limits.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/346625","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=346625"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/djekanovic"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=346625"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=346625"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=346625"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=346625"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=346625"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=346625"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}