Adds Pull and Push: copy a live site to another server over HTTP, with resume and changes-only updates. Off until you switch it on.<\/p>","1.4.0":"
Recommended for everyone. Backups made with 1.3.x may contain damaged percent signs and non-ASCII text. After updating, make a fresh backup.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3707868,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3707868,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3671394,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3671394,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3769343,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"meta\":{\"title\":\"Plogins Migrator - Site Migration and Backup, Live Preview\",\"author\":\"WPPoland\"},\"landingPage\":\"\\\/wp-admin\\\/admin.php?page=migrator\",\"preferredVersions\":{\"php\":\"8.2\",\"wp\":\"latest\"},\"login\":true,\"steps\":[{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"woocommerce\"},\"options\":{\"activate\":true}},{\"step\":\"runPHP\",\"code\":\"true, 'completed'=>true));\\nif (function_exists('wc_get_product_id_by_sku') && class_exists('WC_Product_Simple')) {\\n $demo = array('Trailwind Running Shoes'=>89, 'Harbor Leather Wallet'=>39, 'Amber Soy Candle'=>18, 'Coastal Pullover Hoodie'=>49, 'Field Canvas Backpack'=>59, 'Matte Ceramic Mug'=>14);\\n foreach ($demo as $name=>$price) {\\n $sku = 'demo-'.sanitize_title($name);\\n if (wc_get_product_id_by_sku($sku)) { continue; }\\n $p = new WC_Product_Simple();\\n $p->set_name($name); $p->set_sku($sku); $p->set_regular_price((string)$price);\\n $p->set_status('publish'); $p->set_catalog_visibility('visible');\\n $p->save();\\n }\\n}\"},{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"plogins-migrator\"},\"options\":{\"activate\":true}}]}"}},"all_blocks":[],"tagged_versions":["1.1.0","1.2.0","1.2.1","1.2.10","1.2.11","1.2.12","1.2.13","1.2.14","1.2.15","1.2.16","1.2.17","1.2.18","1.2.2","1.2.3","1.2.4","1.2.5","1.2.7","1.2.8","1.2.9","1.3.0","1.3.2","1.3.3","1.3.4","1.3.5","1.3.7","1.3.8","1.4.0","1.5.0","1.5.1","1.6.0","1.6.1","1.6.2","1.6.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3605916,"resolution":"1","location":"assets","locale":"","width":1600,"height":1200},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3605916,"resolution":"2","location":"assets","locale":"","width":1600,"height":1200}},"screenshots":{"1":"The Migrator screen: create a backup with presets and exclusion options, alongside restore and your saved backups.","2":"The file-size explorer: scan wp-content and see each folder's size so you can leave out what you do not need."}},"plugin_section":[],"plugin_tags":[151,2814,4151,4155,152],"plugin_category":[59],"plugin_contributors":[264912],"plugin_business_model":[],"class_list":["post-337425","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-clone","plugin_tags-migrate","plugin_tags-migration","plugin_tags-restore","plugin_category-utilities-and-tools","plugin_contributors-motylanogha","plugin_committers-motylanogha"],"banners":{"banner":"https:\/\/ps.w.org\/plogins-migrator\/assets\/banner-772x250.png?rev=3671394","banner_2x":"https:\/\/ps.w.org\/plogins-migrator\/assets\/banner-1544x500.png?rev=3671394","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/plogins-migrator\/assets\/icon-128x128.png?rev=3707868","icon_2x":"https:\/\/ps.w.org\/plogins-migrator\/assets\/icon-256x256.png?rev=3707868","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/plogins-migrator\/assets\/screenshot-1.png?rev=3605916","caption":"The Migrator screen: create a backup with presets and exclusion options, alongside restore and your saved backups."},{"src":"https:\/\/ps.w.org\/plogins-migrator\/assets\/screenshot-2.png?rev=3605916","caption":"The file-size explorer: scan wp-content and see each folder's size so you can leave out what you do not need."}],"raw_content":"\n
Migrator packs your database and everything in Everything happens on your own server. There is no account to create and no file size sold back to you, and nothing leaves your server unless you add an off-site destination you own or switch on Pull and Push. The source lives at github.com\/wppoland\/plogins-migrator<\/a>, which is also where to file a bug or request a feature.<\/p>\n\n How it works<\/strong><\/p>\n\n The address rewrite is safe for serialized data<\/strong>: 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.<\/p>\n\n Scheduled backups and off-site copies<\/strong><\/p>\n\n Back up daily or weekly and keep as many copies as you choose. Each scheduled backup can also be copied off the server, to an FTP or FTPS server or to a local or mounted folder outside the web root. Older scheduled copies are deleted automatically, on the server and at the destination, once they fall outside your retention setting.<\/p>\n\n Pull and push between live sites<\/strong><\/p>\n\n Copy a whole site to another server over HTTP, with no archive to download or upload and no SSH or FTP. On the site you are copying, switch on Migrator > Pull and Push. On the destination, run A few things worth knowing<\/strong><\/p>\n\n Backups are written to Restoring overwrites<\/strong> 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.<\/p>\n\n For large sites where a browser request would time out, every job also runs from WP-CLI, which has no timeout:<\/p>\n\n What's included<\/strong><\/p>\n\n Documentation and links<\/strong><\/p>\n\n Reporting a security issue: email hello@wppoland.com, and under our coordinated disclosure policy<\/a> we confirm within two business days, assess within five, and patch a critical issue within seven days of confirming it.<\/p>\n\n All six plugins named here back up and migrate WordPress. What separates them is what you get without paying, so the grid reads the free edition of each. Every entry was checked against vendor pricing pages and vendor documentation on 29 July 2026; the All-in-One WP Migration and Duplicator columns were checked again on 27 October 2026.<\/p>\n\n The columns, left to right: Migrator<\/strong>, AIO<\/strong> is All-in-One WP Migration, Dupl<\/strong> is Duplicator, WPvivid<\/strong>, Updraft<\/strong> is UpdraftPlus, WPMigr<\/strong> is WP Migrate. A cell reads yes<\/strong> if the free edition does it, paid<\/strong> if that vendor sells it in a paid tier or add-on, no<\/strong> if the vendor does not offer it at any price, part<\/strong> if only partly, and ?<\/strong> if the vendor does not say. A row of paid<\/strong> is a paywall, not a missing feature; no<\/strong> is the one that means the thing does not exist.<\/p>\n\n Where Migrator is ahead in free.<\/strong> Scheduled backups with a retention rule, an off-site copy over FTP\/FTPS or to a folder outside the web root, no size limit beyond what your own server allows, and a database snapshot taken before every import and put back automatically if the database import fails. No other free tier here documents that rollback. Automation is not the paid tier here: a site that wants a nightly backup landing somewhere other than the server it protects needs nothing beyond the free plugin.<\/p>\n\n What PRO adds.<\/strong> Cloud destinations (S3, R2, Backblaze, Wasabi, SFTP, WebDAV), incremental backups, encrypted archives, recovery points, Table Sync, multisite restore, deploying to an empty server, resetting a staging site to a clean install, and a white-label mode that puts an agency's own name on the plugin. From 49 EUR per year.<\/p>\n\n Exports to a single Builds a package plus an installer. The vendor's readme states that the free plugin makes backups of any size, encrypts archives with AES-256 and a password, and stores backups locally or on its own Duplicator Cloud. Scheduling, other cloud destinations, recovery points, multisite and server-to-server import are in the paid plans, from a $79 list price.<\/p>\n\n Scheduled backups with one retention rule, Dropbox, Google Drive, S3, OneDrive, DO Spaces, FTP and SFTP as destinations, and server-to-server transfer with a migration key. Archives split at 200 MB. The vendor states databases cannot be backed up incrementally, encryption in Pro covers the database only, and table-level merging is sold as a separate product.<\/p>\n\n Free scheduling from every 2 hours up to monthly, with Google Drive, Dropbox, S3, Rackspace, FTP, Swift and email as destinations. Archives split at 400 MB. Multisite, incremental file backups and database encryption are Premium, $70 to $399\/yr excluding VAT.<\/p>\n\n Lite exports a ZIP and does not import at all. Moving files between live sites, and push and pull, are paid, $49 to $219 for the first year. No tier offers a cloud or FTP destination.<\/p>\n\n Competitor prices are in USD, Migrator PRO is priced in EUR, and no conversion is implied. List prices and tier limits change without notice, so confirm on the vendor's own page before you buy. Migrator itself is free under GPLv2 with no account to create; PRO is 49 to 149 EUR per year.<\/p>\n\n Migrator Pro is a separate paid plugin that extends Migrator.<\/p>\n\n Included in Migrator:<\/p>\n\n Migrator Pro adds:<\/p>\n\n The free edition is not a trial and its features stay available without a time limit.<\/p>\n\n Plogins Migrator is fully translatable and ships the 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n Migrator sets no size limit. A browser export runs in short steps, so PHP time limits do not stop it, and uploads go in 4 MB pieces, so your host's upload limit does not apply. A browser restore runs as one long request, and some hosts or proxies (Cloudflare, nginx) cut those off. For a big site, restore with The restore may still be running on the server. Wait a few minutes, then check the site. To avoid it, restore over WP-CLI. If a restore stops after the database was replaced, the error message gives the path of the database dump taken before the restore, so you can put the old database back.<\/p><\/dd>\n The archive is checked before the database is touched, so an unfinished or corrupt archive is refused with the site left as it was. If the database import or the URL rewrite fails, the previous database is restored automatically. If a later step fails (for example, the disk fills while files are extracted), the site is left part restored, and the message says what state it is in and where the previous database dump is, so you can restore it by hand.<\/p><\/dd>\n Yes. Install WordPress and Migrator on the destination, then restore the archive there. The database prefix in the new site's wp-config.php must match the source site's; the restore checks this first and tells you the value to set.<\/p><\/dd>\n No. An archive holds the database and everything in Not yet. Restore it with the plugin that made it, then create a Migrator backup to use from then on.<\/p><\/dd>\n It is Migrator's own streaming format, not a ZIP. Restore it with Migrator, or check its contents first with Details in the backups list.<\/p><\/dd>\n Only where you tell it to. Migrator creates no account and calls no service of ours. Backups stay in If you switch on Pull and Push, a site holding your connection token or an enrolled key can download this site's files and database, user password hashes included. It is off by default, nothing is answered without that credential, and you can switch it off again when the move is done.<\/p><\/dd>\n Install Migrator on both sites. On the old one, switch on Migrator > Pull and Push. On the new one, run Files, yes: In Yes. Orders (including HPOS tables), products and settings move with the database. You can leave out WooCommerce sessions and Action Scheduler tables to make the archive smaller.<\/p><\/dd>\n 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.<\/p><\/dd>\n Comparing free editions:<\/p>\n\n See the grid above for all five competitors. Vendor details as of July 2026.<\/p><\/dd>\n\n<\/dl>\n\n\nwp-content<\/code> 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.<\/p>\n\n\n
wp-content<\/code> into one archive next to it.<\/li>\nwp migrator pull https:\/\/your-old-site.example<\/code>: the first run prints a key, which you paste on the source's Pull and Push screen, then you run the same command again (a source without the OpenSSL extension takes a connection token instead). The files and the database travel in small pieces, an interrupted pull carries on where it stopped when you run it again, and the next run fetches only what changed. Addresses are rewritten while the database streams in, the database keeps its exact bytes so accented text survives, and the old host's own platform plugins and server-bound drop-ins are left behind. wp migrator push<\/code> sends the destination's file changes back.<\/p>\n\nwp-content\/migrator-backups<\/code>. On Apache and IIS that folder denies direct web access. nginx ignores those rules, so every backup file name also carries a random token and is never at a guessable URL. The in-browser download is served only to logged-in administrators through an authenticated handler. Each item inside an archive carries a checksum, and a finished archive ends with an end marker, so a truncated or corrupted backup is caught before it is restored over a live site.<\/p>\n\nwp migrator export\nwp migrator import path\/to\/backup.migrator\n<\/code><\/pre>\n\n\n
wp-content<\/code> into a single archive<\/li>\nwp migrator pull<\/code>: resumable, and the next run fetches only the changes<\/li>\nwp migrator push<\/code>, and run the low-level transfer commands through wp migrator remote<\/code><\/li>\nexport<\/code>, import<\/code> and replace<\/code> commands for sites too large for the browser<\/li>\nwp migrator replace<\/code> command, to change a domain, URL or path safely<\/li>\n\n
How Migrator compares<\/h3>\n\n
Migrator AIO Dupl WPvivid Updraft WPMigr\n--------------------------------------------------------------------------\nFull backup + migration yes yes yes yes yes part\nNo size cap, free tier yes no yes yes yes ?\nScheduled backups yes paid paid yes yes no\nCloud or FTP destination yes paid part yes yes no\nIncremental backups paid paid no paid paid no\nEncrypted archives paid yes yes part part ?\nServer to server transfer yes paid paid yes paid paid\nMultisite net. restore paid paid paid part paid paid\nImports chosen tables paid ? no paid paid paid\nPaid plan, from EUR49 $69 $79 $49 $70 $49\n<\/code><\/pre>\n\nAll-in-One WP Migration<\/h4>\n\n
.wpress<\/code> file, and its AES-256 password-protected export is in the free plugin, which is one thing Migrator keeps in PRO. The free export is bounded by your host's PHP limits; lifting them is the Unlimited extension at $69\/yr. Multisite is a separate add-on at $319\/yr.<\/p>\n\nDuplicator<\/h4>\n\n
WPvivid<\/h4>\n\n
UpdraftPlus<\/h4>\n\n
WP Migrate<\/h4>\n\n
Migrator Pro<\/h3>\n\n
\n
\n
\n
Translations<\/h3>\n\n
plogins-migrator.pot<\/code> template. Translations are delivered by WordPress.org language packs from translate.wordpress.org, which is where Polish, German and Spanish are being contributed; the package itself carries no compiled translation files.<\/p>\n\n\n\n
\/wp-content\/plugins\/plogins-migrator<\/code>, or install it from Plugins > Add New.<\/li>\nwp migrator export<\/code> from the command line.<\/li>\n<\/ol>\n\n\n\n
Does restoring delete what is already on the destination?<\/h3><\/dt>\n
Will my links break when I move to a new domain?<\/h3><\/dt>\n
How large a site can I move?<\/h3><\/dt>\n
wp migrator import <file><\/code>, which has no time limit.<\/p><\/dd>\nMy host times out or shows a 502 during a restore. What now?<\/h3><\/dt>\n
What happens if a restore fails?<\/h3><\/dt>\n
Do I need WordPress installed on the new host?<\/h3><\/dt>\n
Does it back up WordPress core and wp-config.php?<\/h3><\/dt>\n
wp-content<\/code>. WordPress core comes from the fresh install, and wp-config.php stays the destination's own, so its database credentials are never overwritten.<\/p><\/dd>\nCan I import a .wpress file from All-in-One WP Migration, or a Duplicator package?<\/h3><\/dt>\n
Can I open a .migrator file without the plugin?<\/h3><\/dt>\n
Does it send my data anywhere?<\/h3><\/dt>\n
wp-content\/migrator-backups<\/code> unless you add an off-site destination (an FTP or FTPS server, or a folder outside the web root), and then a copy goes there. Scheduled backups older than your retention setting are deleted automatically.<\/p>\n\nHow do I copy a live site to another server without downloading a backup?<\/h3><\/dt>\n
wp migrator pull https:\/\/old-site.example<\/code> with WP-CLI. The first run prints a key: paste it on the old site's Pull and Push screen and run the command again. A server without the OpenSSL extension cannot check keys, so there you set a connection token and add --secret=<token><\/code>. The new site keeps its own WordPress core, wp-config.php and table prefix (the prefixes must match), its database is dumped before it is replaced and put back if the import fails, and Migrator's own folder is never overwritten. Running the same command again fetches only what changed.<\/p><\/dd>\nCan I send changes back to the original site?<\/h3><\/dt>\n
wp migrator push https:\/\/old-site.example<\/code> sends what changed since the pull. The old site must grant push access to your key on its Pull and Push screen, and its server needs a writable folder beside the web root on the same disk, where the upload is staged before it is swapped in. The database is pushed only to hosts that serve the transfer API on a standalone route; wp migrator remote db-push --help<\/code> explains it. While a push applies its changes the old site shows a maintenance page; if the push stops part way, run it again to finish.<\/p><\/dd>\nWhere are my backups stored?<\/h3><\/dt>\n
wp-content\/migrator-backups<\/code>. On Apache and IIS the folder denies direct web access; on nginx, which ignores those rules, each file name carries a random token so it cannot be guessed. Removing the plugin deletes that folder and its contents. Copies on an off-site destination stay there.<\/p><\/dd>\nDoes it work with WooCommerce?<\/h3><\/dt>\n
Does this plugin work on WordPress Multisite?<\/h3><\/dt>\n
How does Migrator compare to Duplicator and All-in-One WP Migration?<\/h3><\/dt>\n
\n
wp migrator export<\/code>, import<\/code> and replace<\/code> are in the free plugin.<\/li>\n1.6.3<\/h4>\n\n
\n
1.6.2<\/h4>\n\n
\n
1.6.1<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
migrator_step_seconds<\/code> filter sets how long one export step may work, for hosts whose proxy cuts requests short.<\/li>\n<\/ul>\n\n1.5.1<\/h4>\n\n
\n
wp migrator pull<\/code>, PRO adds the wp-admin screen.<\/li>\n<\/ul>\n\n1.5.0<\/h4>\n\n
\n
wp migrator pull<\/code>, resume an interrupted pull, fetch only the changes on the next run, and send file changes back with wp migrator push<\/code>. Off until you switch it on.<\/li>\nwp migrator remote<\/code> runs the low-level transfer commands, such as keygen, files-stats or db-push.<\/li>\n1.4.0<\/h4>\n\n
\n
%<\/code> characters in the database. In 1.3.8, permalink structures, text such as \"50%\" and serialized values containing %<\/code> were damaged on restore.<\/li>\nwp migrator import<\/code> reports errors cleanly.<\/li>\n1.3.8<\/h4>\n\n
\n
1.3.7<\/h4>\n\n
\n
1.3.6<\/h4>\n\n
\n
1.3.5<\/h4>\n\n
\n
1.3.4<\/h4>\n\n
\n
1.3.3<\/h4>\n\n
\n
1.3.2<\/h4>\n\n
\n
1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
migrator\/backup_destinations<\/code> filter instead of the free plugin knowing about them.<\/li>\n1.2.18<\/h4>\n\n
\n
1.2.17<\/h4>\n\n
\n
1.2.16<\/h4>\n\n
\n
1.2.15<\/h4>\n\n
\n
1.2.14<\/h4>\n\n
\n