Linux 软件免费装
Banner图

Migrator - Site Migration and Backup

开发者 motylanogha
更新时间 2026年7月30日 21:49
PHP版本: 8.1 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

backup migration restore clone wp-cli

下载

1.2.4 1.2.1 1.2.2 1.2.0 1.2.3 1.2.7 1.2.5 1.2.8 1.2.9 1.1.0 1.2.10 1.2.11

详情介绍:

Migrator packs your database and everything in wp-content into a single file you can download, keep as a backup, and restore, on the same site or on a brand-new install somewhere else. When you restore onto a different address, Migrator rewrites the old URLs and file paths to the new ones for you, so the site just works. Everything happens on your own server. There is no account to create, no file size sold back to you, and nothing is ever sent to a third-party service. Because it is fully open, you can read exactly what it does: the source lives at https://github.com/wppoland/plogins-migrator, which is also where to file a bug or request a feature. How it works
  1. On the site you want to copy, create a backup. Migrator writes your database to a portable SQL dump and streams every file in wp-content into one archive next to it.
  2. Download that archive (or, on a big site, build it from the command line, see below).
  3. On the destination, the same site to roll back, or a fresh WordPress install to move to, restore the archive. Migrator imports the database, puts the files back, and rewrites the source site's web address and paths to this one.
The address rewrite is safe for serialized data: Migrator walks the actual data structures rather than doing a blind text replace, so the byte-length counts PHP stores inside serialized options and meta stay correct and nothing breaks. A few things worth knowing Backups are written to a protected folder (wp-content/migrator-backups) that denies direct web access, and the in-browser download is served only to logged-in administrators through an authenticated handler, the files are never exposed at a guessable URL. Each item inside an archive carries a checksum, so a truncated or corrupted backup is caught before it is ever restored over a live site. Restoring overwrites the destination database and files, that is the point of a restore, so it asks for confirmation and is limited to administrators. Migrator never overwrites its own plugin folder during a restore, so it cannot pull the rug out from under itself mid-import. For large sites where a browser request would time out, every job also runs from WP-CLI, which has no timeout: wp migrator export wp migrator import path/to/backup.migrator What's included

安装:

  1. Upload the plugin to /wp-content/plugins/migrator, or install it from Plugins → Add New.
  2. Activate it. There are no required dependencies.
  3. Open Migrator in the admin menu to create a backup, or use wp migrator export from the command line.

屏幕截图:

  • The file-size explorer: scan wp-content and see each folder's size so you can leave out what you do not need.

常见问题:

Documentation and links

Does restoring delete what is already on the destination?

Yes. A restore replaces the destination's database and files with the contents of the archive, that is what restoring a backup means. It is limited to administrators and asks for confirmation first. Always keep a separate backup of anything on the destination you want to keep.

Will my links break when I move to a new domain?

No. When you restore onto a different address, Migrator rewrites the old site URL and file paths to the new ones, including inside serialized data, so internal links and settings keep working.

My site is large and the browser export stops. What do I do?

Use WP-CLI, which has no request time limit: wp migrator export to build the archive and wp migrator import <file> to restore it.

Does it send my data anywhere?

No. Migrator runs entirely on your own server. It creates no account and contacts no external service. Your backups stay in wp-content/migrator-backups until you download or delete them.

Where are my backups stored?

In wp-content/migrator-backups, a folder protected from direct web access. Removing the plugin deletes that folder and its contents.

Does this plugin work on WordPress Multisite?

It runs on Multisite: network activate it or activate it on individual sites, and each site keeps its own settings and data. Restoring a network is a different matter. The free edition refuses an import when either the archive or the target site is a network, so network migration needs the Migrator Pro add-on.

How does Migrator compare to Duplicator and All-in-One WP Migration?

All three back up, clone and migrate WordPress, and all three run on your own server. The differences worth knowing, comparing the free editions:

  • Size limits: Migrator's free edition has no artificial size limit. All-in-One WP Migration limits imports in its free version and sells a paid Unlimited extension to remove that cap. Duplicator's free edition has no advertised size cap either.
  • Serialization-safe URL rewriting: all three do it.
  • Exclusions and stored-backup management: free in Migrator and in Duplicator; part of the paid tier for All-in-One WP Migration.
  • Scheduling, incremental backups, cloud storage and multisite: paid in all three (Migrator PRO, Duplicator Pro, paid All-in-One WP Migration extensions).
  • WP-CLI: Migrator ships wp migrator export, import and replace in the free version.
  • Licensing: Migrator is GPLv2 and fully open source, including PRO.
Competitor details as of July 2026; check the vendors' own sites for their current features and pricing.

更新日志:

1.2.11 1.2.10 1.2.9 1.2.7 1.2.6 1.2.5 1.2.4 1.2.3 1.2.2 1.2.1 1.2.0 1.1.1 1.1.0 1.0.3 1.0.2 1.0.1 0.3.3 0.3.2 0.3.1 0.3.0 0.2.0 0.1.0