內容簡介
Cloud Migrate 是一款專為 WordPress 網站遷移設計的外掛，能夠輕鬆將整個網站（包括資料庫、媒體、外掛和佈景主題）從一個主機轉移到另一個主機，無需手動上傳或下載檔案，簡化了遷移過程。
【主要功能】
• 完整網站遷移，包括資料庫和媒體
• 支援可恢復的分段傳輸
• 自動適應主機限制，無需手動配置
• 保留原始資料庫表格，便於回退
• 確保安全性，使用 HMAC-SHA256 簽名連接金鑰
• 無需第三方服務，完全在本地進行遷移
外掛標籤
開發者團隊
原文外掛簡介
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.
Serialized data is unserialized, rewritten and re-serialized properly — URLs are also replaced in JSON-escaped and URL-encoded forms, which is what page builders such as Elementor store internally.
Connection keys are signed with HMAC-SHA256, are valid for three hours, and can be revoked at any time.
A built-in debug report shows the environment, host limits, transfer throughput and every logged request. It contains no passwords and no connection keys.
What is transferred
The database is always migrated. You choose whether to include media/uploads, plugins, themes and must-use plugins.
External services
This plugin communicates with the other WordPress site you are migrating to or from — 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.
What is sent: the connection key you generated, and requests for database rows and files.
When: only while a migration is running, and only to the site the connection key was issued for.
What is received: that site’s database contents and files.
No analytics, telemetry, tracking or external API calls of any kind are made. The plugin loads no remote scripts, fonts or images.
