Create Backup
Before you run an Update, Upsert, Delete, or Delete Hard operation, it is a good idea to save a copy of the current data in Salesforce so you can restore it if something goes wrong. The Create Backup button does exactly that — it queries the records you are about to change and downloads them as a CSV file to your local machine.
- Create Backup is only available for Update, Upsert, Delete, and Delete Hard actions. It is not shown for Insert because there is nothing to back up before inserting new records.
- For Update, Delete, and Delete Hard: an active field mapping to the
Idfield must exist. - For Upsert: an active field mapping to the selected Upsert Field must exist.
- All queued records must have a non-blank value in the key field (
Idor Upsert Field).
What Gets Backed Up
The fields included in the backup depend on the action:
| Action | Fields Backed Up |
|---|---|
| Update | All actively mapped target fields, plus LastModifiedDate and LastModifiedBy |
| Upsert | All actively mapped target fields, plus LastModifiedDate and LastModifiedBy |
| Delete / Delete Hard | All accessible fields on the object |
Output
The backup is saved as a CSV file named <ObjectName>-Backup-<timestamp>.csv (for example,
Account-Backup-2026-04-02T10-30-00.csv) and downloaded to your local machine automatically.
Brobench also verifies that every queued record was found in Salesforce. If the returned count does not match, it raises an error — which usually indicates a permissions issue — so you can investigate before proceeding.
When to Use It
Click Create Backup after configuring your field mapping and before clicking Run Import. This gives you a point-in-time snapshot of the exact records you are about to modify, which you can reload into Quick Loader later if you need to undo the changes.