Importing a Backup from Another Backup My Org Server or Backup Folder
Available in Backup My Org version 1.4.1.37+
Overview
BackupMyOrg supports importing backups that were created on a different Backup My Org server or under a different identity on the same server. This is useful when migrating server environments or consolidating backup data. The process involves copying the physical backup files to the correct location and then using the Import Backups button on the Manage Identities page to register them.
Prerequisites
Access to the backup directory from the source BMO server (the folder named with the 24-character backup ID)
The destination BMO server must have the target identity already configured with a local Save Location
Access to MongoDB Compass (if re-importing a backup ID that already exists)
Steps
1. Locate the Source Backup Folder
On the source BMO server, find the backup directory you want to migrate. It will be located under the identity's Save Location and named with the backup's 24-character ID, for example:
C:\_backup\SourceOrg\6940749e90a49c060a34c8ba\This folder contains the backup entries JSON, scratch files, and archived content.
2. Copy the Backup Folder to the Destination
Copy the entire backup folder (e.g., 6940749e90a49c060a34c8ba) into the Save Location configured for the target identity on the destination BMO server.
To find the Save Location, go to Manage Identities, click the Edit button for the identity, and note the Save Location for Backups and Restores field.
Place the copied folder directly inside that Save Location path. For example, if the Save Location is C:\\_backup\\AGOL, the result should be:
C:\_backup\AGOL\6940749e90a49c060a34c8ba\3. Handle Existing Backup IDs (If Applicable)
Note: If the backup ID you are importing already exists as a BackupReport entry in the destination server's database, the import will update its Save Location and file paths automatically. However, if you encounter issues, you may need to manually remove the existing entry:
Open MongoDB Compass and connect to your BMO database.
Navigate to the BackupReports collection.
Search for the document with the
_idmatching the backup ID you are importing.Backup the entry, then Delete that document or change the _id.
Proceed with the import.
4. Run the Import
In BackupMyOrg, navigate to the Manage Identities page.
Find the identity whose Save Location contains the copied backup folder.
Click the Import Backups button (the file import icon) in the identity's row.
Wait for the operation to complete. The button will display a spinner while processing.
5. Confirm the Import
After the import finishes, a dialog will appear with a status report:
Successful imports will be listed by name and backup ID.
Errors (e.g., missing backup entries files, duplicate IDs) will be listed individually.
You should see a message similar to:
Successfully imported 1 backup(s):
- Imported Backup 6940749e90a49c060a34c8ba (6940749e90a49c060a34c8ba)6. Verify in Restore
To confirm the backup is ready for use:
Navigate to the Backup History page.
The imported backup will appear as "Imported Backup <backupId>" at the top of the list (sorted by most recent).
You can now select it and proceed with a restore as usual.
Troubleshooting
Issue | Solution |
|---|---|
"No new backups found to import" | The backup directory may already be registered. Check if it appears in Backup History. |
"Missing <backupId>-backupEntries.json" | The copied folder is incomplete. Ensure the backup entries JSON file exists inside the backup directory. |
Import button is disabled | The identity uses cloud storage (S3, Azure, or Google). Import is only available for local storage identities. |
Restore fails with file-not-found errors | Re-run the import. It will re-scan and rewire any file paths that still reference the old location. |