FAQ
Frequently asked questions about Migrator backups, restores, and server migration.
Can I open and extract the backup file without Migrator?
Section titled “Can I open and extract the backup file without Migrator?”Yes. Migrator uses the universal, standard .tar.gz archive format. The archive contains:
database.sql: A clean MySQL/MariaDB database dump.manifest.json: Metadata detailing table counts, WordPress version, PHP version, and original paths.- Archived
wp-contentdirectories (plugins, themes, uploads).
You can inspect or extract the contents on macOS, Linux, or Windows using 7-Zip, tar, or any standard desktop archive utility without needing WordPress or the plugin installed.
What is serialization-safe search and replace?
Section titled “What is serialization-safe search and replace?”WordPress and WooCommerce store complex options, widget settings, and plugin configurations as serialized PHP strings (e.g. s:19:"https://example.com";). In serialized strings, the number preceding the string represents its exact character length in bytes.
A naive SQL REPLACE() query changes the text but leaves the old length counter intact. When PHP tries to deserialize the corrupted record, it fails and discards the entire setting, breaking widgets, menus, and plugin configurations.
Migrator unpacks serialized data structures, replaces strings, recalculates length counters, and re-serializes the data accurately.
Is there a file size limit on backups?
Section titled “Is there a file size limit on backups?”No. The free edition of Migrator imposes no artificial size caps. Your site size is limited only by available disk space on your server.
For web-based operations, Migrator processes dumps and uploads in small 4 MB chunked HTTP steps with a live progress bar. For multi-gigabyte stores, running wp migrator export via WP-CLI bypasses browser limits entirely.
How are backup files protected against unauthorized downloads?
Section titled “How are backup files protected against unauthorized downloads?”Backups are saved to wp-content/migrator-backups/. On Apache and IIS servers, Migrator places access configuration files that block direct web traffic.
Because nginx ignores .htaccess files, Migrator adds two layers of protection:
- Each backup file name includes a cryptographically random token (e.g.
backup-site-2026-11-20-a8f3b2c1.tar.gz), making it impossible to guess. - In-browser downloads are handled through an authenticated WordPress admin endpoint that verifies administrative privileges before streaming bytes.
What happens if a restore fails mid-way?
Section titled “What happens if a restore fails mid-way?”Before applying any changes to the database, Migrator captures a full database snapshot.
- If a database query fails or URL rewriting is interrupted, Migrator automatically restores the pre-restore snapshot, leaving your active site untouched.
- If the database succeeded but file extraction stopped (for instance, running out of disk space), the notice displays the exact path to the snapshot file in
wp-content/migrator-backups/so you can restore or inspect it at any time.
Can I restore files without touching my database?
Section titled “Can I restore files without touching my database?”Yes. In the restore modal under Migrator > Backups, select only the components you wish to overwrite (e.g. untick Database and check only Plugins or Themes). This allows you to roll back code modifications without losing recent customer orders or blog comments.
Does Migrator support WordPress Multisite?
Section titled “Does Migrator support WordPress Multisite?”The free edition backs up single-site installations and individual multisite databases. Migrator Pro adds native network-to-network backup and migration directly from the Network Admin dashboard.