Getting started
Migrator packs your WordPress database and wp-content files into a single self-hosted archive. You can restore it on the same site as a rollback point or migrate it to a fresh server.
Requirements
Section titled “Requirements”- WordPress 6.5 or newer
- PHP 8.1 or newer
- MySQL 5.7+ or MariaDB 10.4+
- Recommended:
tarorzlibPHP extensions for fast archive generation
Migrator operates entirely on your own server. It requires no third-party accounts, introduces no artificial file size caps, and transmits no site data outside your infrastructure unless you configure off-site storage.
Create your first backup
Section titled “Create your first backup”- In wp-admin, navigate to Migrator > Backup.
- Select a backup preset:
- Full site: Includes the complete database, plugins, themes, and media uploads.
- Database only: Dumps tables without file assets (ideal for frequent backups).
- Media only: Backs up uploads without database tables.
- Click Create backup now.
- Migrator processes the dump in chunked steps with a live progress bar. Once finished, the backup appears in your backup list.
Download the backup archive
Section titled “Download the backup archive”Every backup is saved to wp-content/migrator-backups/ as a universal .tar.gz archive containing database.sql, manifest.json, and the archived wp-content directories.
To download:
- Go to Migrator > Backups.
- Locate the backup row.
- Click Download.
The download is served through an authenticated handler to administrators only. Because archives use standard .tar.gz formatting, you can inspect or extract them locally using standard desktop tools (tar, 7-Zip, Archive Utility) without needing the plugin.
Restore on the same site
Section titled “Restore on the same site”A restore overwrites the selected site components with the state stored in the archive:
- Under Migrator > Backups, click Restore on the target archive.
- Select which components to bring back:
- Database: Restores tables and content.
- Plugins: Replaces
/wp-content/plugins/. - Themes: Replaces
/wp-content/themes/. - Uploads: Restores media files.
- Confirm the action. Before writing any table data, Migrator takes an automatic pre-restore database snapshot to safeguard your current state.
On environments with DISALLOW_FILE_MODS enabled, wp-admin restores are limited to the database and uploads. Code files (plugins and themes) must be restored via WP-CLI:
wp migrator import path/to/backup.tar.gz --only=plugins,themesMigrate to a new host
Section titled “Migrate to a new host”Moving an existing site to a new domain or host requires three steps:
- Export: On the original site, create and download a Full site backup.
- Setup: Install a clean WordPress instance on the new server and activate the Migrator plugin.
- Import: Open Migrator > Restore, upload the
.tar.gzfile, and proceed with the restore.
During database extraction, Migrator detects domain and directory path changes between the source and destination. It performs a serialization-safe URL and path rewrite, preserving byte counts inside serialized arrays and options so widgets, menus, and plugin settings remain intact.