Salesforce Backup & Recovery

Back up the records. Be ready to recover.

Protect Salesforce records and files with full or incremental backups. Browse independent snapshots, export what you need, and preview record recovery before an administrator approves a write.

From snapshot to controlled recovery
  1. Capture a snapshot

    Selected objects, accessible records, optional files

  2. Preview the restore

    Records, fields, relationships, warnings

  3. Review the receipt

    Completed writes and record mappings

Recovery targets the original Salesforce org. Review intended writes before confirmation.

Independent recovery points

Choose full or incremental capture. Each completed snapshot stands on its own, so browsing and recovery do not depend on replaying an incremental chain.

Recovery with a clear preview

Inspect fields, relationships, warnings, and files before confirming. Create copies or overwrite eligible existing records in the original org.

Distinct operational roles

Operators run backups and viewers browse or export snapshots. Scheduling and restore writes require administrator access, with receipts for recovery activity.

The workflow

A clear path from capture to recovery.

Backups run independently from archive and reclamation. Keep a usable snapshot and a controlled restore process for the moment data changes unexpectedly.

  1. Choose objects and files

    Select the objects to protect and include accessible Salesforce Files and classic Attachments. Capture respects the source user’s visibility.

  2. Capture on your schedule

    Run full or incremental backups on demand, or schedule hourly, daily, or weekly captures. Review job status and the visible capture window.

  3. Inspect and preview

    Browse completed runs, export records, or download verified files. Select up to 200 records for a restore preview and review the fields, destination, and warnings.

  4. Confirm and reconcile

    An administrator confirms the preview. Inspect the restore receipt and record mappings, then verify the workflow. Salesforce validation rules and automation still apply.

Technical fit

Built around your operating environment.

Connect the product to your infrastructure, access requirements, and operational responsibilities.

Data and file coverage
Protect selected accessible records and supported files. This is record and file recovery, separate from metadata or a full-org disaster-recovery image.
Recovery behaviour
Create copies with selected relationship remapping, or overwrite captured writable fields on existing records. Recovery targets the original org.
Storage planning
Choose the destination database for your deployment environment. Independent snapshots and file versions need capacity planning, retention ownership, and database-level backups.
Recovery objectives
Capture spans a time window rather than an atomic org snapshot. Measure recovery with your record set, relationships, source limits, and automation.

Follow configuration, operation, and troubleshooting guides for your environment.

Explore the documentation

Questions worth asking.

Understand the scope before deciding how this fits your organisation.

How is backup different from archiving?

Backup keeps recovery points for loss or unwanted changes. Archiving moves inactive history out of the production workload while retaining access. Backup capture does not enter the archive or purge lifecycle.

Can we restore an entire Salesforce org?

Recovery covers selected records and supported files in the original org. It does not restore Salesforce metadata, provide cross-org recovery, or recreate an entire org as a disaster-recovery image.

What happens to relationships and files?

When creating copies, selected parent and child references are remapped where supported. Unselected lookups retain their original IDs. Included Salesforce Files and classic Attachments are recreated on restored parents; existing files remain.

Does an incremental backup depend on older snapshots?

A completed incremental result is an independent snapshot. Unchanged record payloads are copied from the baseline while changed records are fetched again. This reduces source payload, not the storage needed for each snapshot.

See it with your workflow in mind.

Walk through your Salesforce environment, the records that matter, and the outcome you need. See how the product fits your team’s day-to-day work.

Book a demo