A Salesforce backup policy is a short written document that says what you back up, how much data you can afford to lose, how long you keep each copy, and how you prove that restores work. It turns backup from a tool setting into rules your team can follow and auditors can check.
This template walks through each section of the policy in order: scope, RPO and RTO, retention, restores and testing cadence. Every figure in it is an example, not a benchmark, so set your own with the business owners and your compliance team.
For the background, including who is responsible for Salesforce data, what causes data loss and how backup differs from archiving, read our Salesforce data backup and recovery strategy guide. This post assumes you have chosen a backup approach and now need to write it down.
What does a Salesforce backup policy cover?
A good policy fits on a few pages, and every section has a named owner. Use these five sections as its outline.
1. Scope: what the policy protects
Start by listing exactly what the policy covers, because anything outside its scope will not be backed up or tested. Name the people accountable for each part.
- Orgs: production, plus any sandbox that holds real customer data. A seeded sandbox counts if it holds unmasked production records; sandbox seeding with masked data keeps it out of scope.
- Data: the standard and custom objects in scope, including files and attachments.
- Metadata: custom objects and fields, page layouts, Flows, Apex code, profiles and permission sets. Restoring records without their metadata will not bring the org back to a working state, so back up both.
- Storage location: where the copies live. Keep them outside the production org's control domain, in line with the 3-2-1 rule.
- Exclusions: anything deliberately left out, with the reason and who approved it.
- Owners: who runs backups, who approves restores and who signs off the policy.
2. RPO and RTO: recovery targets by data tier
Recovery Point Objective (RPO) is the most data, measured in time, you can afford to lose. Recovery Time Objective (RTO) is the longest you can wait for it to be restored. NIST contingency planning guidance sets both through a business impact analysis, so ask each business owner rather than picking one number for the whole org.
Group objects into tiers, then match backup frequency to each tier's RPO and the restore method to its RTO.
Check each target against what your tooling can deliver. Salesforce's native Data Export runs weekly at most and only monthly in some editions, so it cannot meet an hourly RPO. If your targets are tighter, compare Salesforce backup solutions.
3. Retention: how long you keep each copy
Retention rules say how long each backup is kept, what moves to an archive and when copies are destroyed. The periods come from your regulatory regime, not from Salesforce, so record the source of each one in the policy.
- Backup copies: for example, daily backups for 30 days and monthly backups for 12 months.
- Archive: which records move out of the live org, and after how long. See Salesforce data archiving for the options.
- SOX: SEC Rule 2-06 requires accounting firms to keep records relevant to audits and reviews for 7 years, and many public companies align financial-data retention with it. See SOX compliance for Salesforce.
- HIPAA: covered entities must keep the documentation the Security Rule requires for 6 years, according to the HHS audit protocol. See HIPAA data backup.
- GxP: FDA guidance on 21 CFR Part 11 covers electronic records kept under FDA requirements. See Part 11 backup and restore.
- Legal hold: how you suspend deletion for records under investigation or litigation, and who can lift the hold.
- Disposal: how and when expired backups are deleted, and who approves it.
Write the schedule as part of your wider Salesforce data retention policy, so the rules for backups, archives and the live org don't contradict each other.
4. Restores: who can bring data back, and how
The policy should say who may request a restore, who approves it and how it is carried out. A rushed restore can cause a second incident, because reloading records can fire Flows and triggers, send emails or overwrite good data with stale values.
- Request and approval: who can ask for a restore, and who signs it off for each tier.
- Compare first: check what changed between the backup point and now, and restore only what was lost.
- Smallest scope first: restore a field, record or object before you consider a full-org rollback.
- Automation control: decide whether triggers and Flows run during the restore.
- Recycle Bin: treat it as a short safety net, not a backup. Records are retained for 15 days by default, and Salesforce documents an optional 30-day extension that Salesforce Support must activate.
For a step-by-step walkthrough, see restoring deleted records. For an outage or a large-scale incident, link this section to your Salesforce disaster recovery plan.
5. Testing cadence: proving the backups work
A backup you have never restored is untested. HIPAA's contingency plan standard lists testing and revision procedures alongside a data backup plan and a disaster recovery plan, and the same habit applies to any regulated org.
- Backup job checks: for example, review failed jobs and alerts every week.
- Restore spot checks: for example, every month, restore a sample of records and fields into a sandbox and compare them with production.
- Full recovery exercise: for example, every quarter, restore a whole object with its relationships and time it against your RTO.
- Metadata restore test: after each major release.
- Policy review: at least once a year, and after a major change such as a new org, a merger or a new regulation.
Record every test in a log with the date, scope, time to restore, issues found and fixes made. That log is the evidence an auditor will ask for.
How do you put the policy into practice?
A policy only works if it shows up in the team's routine. These steps take it from a document to a habit.
- Get sign-off. Business owners agree the tiers and targets, and compliance agrees the retention periods.
- Configure the jobs. Set backup frequency per tier and send failure alerts to a named owner.
- Back up around releases. Add a metadata backup before and after every deployment in your Salesforce DevOps process, so you can roll back a bad release.
- Schedule the tests. Put the testing cadence in the team calendar and keep the test log with the policy.
- Review after incidents. After every restore, check whether you met the RPO and RTO, and update the policy if you didn't.
How does Flosum Backup & Archive support the policy?
Flosum Backup & Archive runs automated, incremental backups of Salesforce data and metadata, so you can set backup frequency to match each tier's RPO. Point-in-time and field-level restores with relationship rebuilding help you hit your RTO without a full-org rollback, and archiving covers long retention periods while reclaiming org storage.
It can be deployed Salesforce-native, in the Flosum-hosted cloud, or customer-hosted, so your copies sit in the control domain your policy names. It also works alongside Flosum's risk and governance controls for regulated orgs.
FAQs
Want to see how this works on your own org? Book a personalized demo to see how Flosum can back up your Salesforce data and metadata, meet your recovery targets, and keep records for as long as your compliance team requires.
Thank you for subscribing




