| 开发者 | estasoft |
|---|---|
| 更新时间 | 2026年11月6日 18:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
.estm packages, with optional password encryption. Restore a rollback snapshot in one step.wp estasoft-migrate has a command for every action, for scripts and servers without a browser.sodium extension is needed only for encrypted packages (included with PHP 7.2 and newer).estasoft-migration-database-sanitizer folder to /wp-content/plugins/, or install the zip from Plugins > Add New > Upload Plugin.Yes. Every feature is included and the code is licensed under the GPL v2 or later.
It copies tables in small batches, saves a checkpoint after each one, and picks the next batch size from how long the last one took. If a request is cut off, the job continues from the checkpoint. On servers where a background runner can be used, you can close the browser and the job keeps going.
Not until the last step. The data is built in temporary tables first, and a verified package plus a rollback snapshot are in place before the tables are switched with one atomic rename.
Yes. Choose a profile on the Sanitizer screen and export a sanitized package. Your live data is never changed by sanitizing; the masking happens in the package.
A single file with your database, split into checked blocks, optionally compressed and encrypted with a password. Any block that is damaged is detected before an import starts.
On the destination site, turn on Accept incoming migrations in Settings and copy the connection key. On the source site, choose Push or Pull under New migration and paste the address and key.
It switches itself off after 24 hours without a migration (you can choose 1 hour, 7 days or never), and each migration moves that time forward, so a running migration is never cut off. While it is on, a site that has the connection key can send a package and start an import, which replaces this site's data, or ask for a copy of the database. Requests are signed, a request can be used only once, HTTPS is required by default, and you can limit the addresses that may connect. If a key may have been seen by someone else, use Replace key and tick "Stop the old key at once".
Yes. WordPress refuses to connect to localhost and private network addresses (such as 192.168.x.x) unless you allow it, so turn on Allow local and private addresses in Settings on the site that starts the push or pull. Turn it off again when you no longer need it.
They are kept in a folder with a random name inside your uploads directory, with rules that deny web access and an empty index file. Downloads go through your admin session and a permission check. The plugin tests this by requesting a throw-away file from that folder and shows the result on the Packages and Settings screens. If your web server ignores .htaccess files (nginx does), add a rule that denies access to wp-content/uploads/estasoft-migrate-*, or protect the package with a password.
No. This version moves the database only. Use it together with your host's file copy, rsync or your usual deployment for wp-content.
Not yet. This version migrates single sites only, and the pre-flight check says so on a network.
.estm packages; push and pull between sites; serialization-safe search and replace; rule-based database sanitizer with three profiles; pre-flight checks; logs; WP-CLI commands.