Skip to content

Configuration

Migrator provides granular control over what gets backed up, when automated jobs run, and where off-site copies are delivered.

When triggering a manual or scheduled backup, you can pick from three built-in presets:

  • Full site: Includes the complete MySQL/MariaDB database along with /wp-content/themes, /wp-content/plugins, and /wp-content/uploads.
  • Database only: Generates a raw SQL dump. Useful for frequent automated exports of orders and post revisions.
  • Media only: Packages media assets without database tables.

You can exclude specific data structures and files to reduce archive size and speed up backup jobs:

Under Migrator > Settings > Database Exclusions, you can skip non-essential database tables and cache records:

  • Transients and object caches: Skips temporary _transient_* and _site_transient_* rows in wp_options.
  • Spam comments: Leaves out comments flagged as spam or trash.
  • Post revisions: Excludes older revisions while preserving published posts.
  • WooCommerce customer sessions: Skips woocommerce_sessions table data.
  • Action Scheduler logs: Skips completed or failed action logs (actionscheduler_logs, actionscheduler_actions).

Under Migrator > Settings > File Exclusions, you can define rules for file processing:

  • Skip specific folders: Exclude cache directories (such as wp-content/cache/ or plugin cache folders) and earlier backup dumps (wp-content/migrator-backups/ is automatically excluded).
  • File patterns: Provide glob patterns to ignore matching files, such as *.log, *.zip, or .git.
  • Maximum file size: Set a threshold (e.g. 50MB) to skip massive video files or raw logs during automated runs.

To enable hands-free backups:

  1. Open Migrator > Schedules.
  2. Enable the Full backup schedule.
  3. Choose an interval:
    • Every 2 hours
    • Every 4 hours
    • Every 12 hours
    • Daily (at a designated server hour)
    • Weekly
  4. Retention rule: Specify how many historical copies to keep locally and off-site (for example, keep the last 5 copies). Older archives exceeding this number are pruned automatically.
  5. Secondary database schedule: You can run an independent database-only schedule on a tighter loop (e.g. every 2 hours) while maintaining full site backups on a weekly interval.

Under Migrator > Settings > Safeguards:

Enable Back up the site before plugin, theme and WordPress updates. When active, WordPress update routines (manual or background auto-updates) trigger an automatic backup snapshot immediately before any files on disk are touched. If multiple plugin updates occur within a 10-minute window, they share a single unified snapshot to avoid redundant archive creation.

Check Email me when an automatic backup fails to receive instant administrative alert notifications if a scheduled or pre-update backup encounters an error.

Storing copies on external infrastructure protects against server hardware failures:

  • FTP / FTPS: Deliver backup archives to an external FTP or secure FTPS host. Provide hostname, port (default 21), username, password, and remote target directory.
  • Local or mounted folder: Save archives directly to a separate storage volume or NFS mount outside the WordPress root.

Migrator Pro expands storage targets to direct cloud APIs without external sync daemons:

  • Amazon S3: Presets for AWS regions, standard IAM access keys, and storage classes.
  • Cloudflare R2: Zero-egress fee S3-compatible bucket integration.
  • Backblaze B2, Wasabi, DigitalOcean Spaces: Native S3 API compatibility.
  • SFTP: Secure SSH file transfer with key or password authentication.
  • WebDAV: Nextcloud and ownCloud integration.
  • Google Drive and Dropbox: Direct OAuth token integration.