Local backup vs MigraSync Managed Cloud
MigraSync backups are designed around MigraSync Managed Cloud — encrypted off-site storage tied to your account. Some jobs may also leave temporary artifacts on your server during processing, but cloud vault copies are what power WP Restore and cross-site cloning.
MigraSync Managed Cloud (primary)
- Encrypted with your Master Vault Key (AES-256 at rest).
- Listed in Recent Backup Jobs and available in WP Restore.
- Counts toward your plan’s Managed Cloud Quota (GB) on the plugin dashboard.
- Required for clone to another site.
Important: If you lose the vault key, encrypted cloud backups cannot be decrypted. Keep the Recovery Sheet safe.
Local / on-server copies
During backup, MigraSync may use server disk for packaging and upload. You do not manage a separate “local backup folder” in the wizard — the customer-facing destination is MigraSync Managed Cloud.
Do not rely on server temp files as long-term disaster recovery. Use cloud backups + WP Restore instead.
Plan quotas
| Plan | Typical use |
| Backup trial | Test one site, limited cloud storage |
| Essential | One or more sites, managed cloud quota |
| Pro | Higher site count and cloud storage |
Current limits: Pricing → Backup and quota bars on MigraSync → General.
When cloud quota is full
- Purge old jobs from Recent Backup Jobs (see manage backup jobs).
- Upgrade to Pro if you need more storage.
- Adjust Auto purge policy on schedules so old points expire automatically.
Related