One-Time Setup · $500

Salesforce Backup —
Automated, Scheduled & Restore-Ready

Salesforce doesn't back up your data the way most teams assume. We set up an automated Salesforce backup solution for your org — scheduled exports, verified restores, and a documented process — so one bad bulk update or runaway automation is a 30-minute fix, not a crisis.

Flat $500 one-time setup  ·  No ongoing subscription required  ·  Built for production Salesforce orgs

GI
Geeth IlanSalesforce Certified Architect · 15+ years · Founder, Radix2 Tech

We are a Salesforce consulting firm. We do not sell backup software. We have set up backup solutions for 8 client orgs and will recommend the tool that is right for yours — including if that means a competitor product.

Your Org Is One Mistake Away From Data Loss

Most teams discover their backup gap only after it has already cost them data.

One Bad Update Can Wipe Out Records

A mistaken bulk update, a runaway automation, or a careless data import can overwrite or delete records org-wide — and Salesforce gives you very little time or tooling to undo it.

Native Recovery Options Are Limited

Salesforce's built-in recovery tools are slow, incomplete, and not designed for routine use. By the time you realize data is missing, the window to recover it natively may already be closing.

No Clear Story for Auditors or Customers

When a customer or auditor asks how your org is protected against data loss, "we hope it doesn't happen" is not an answer. Without a documented backup process, you have no real proof of resilience.

When a Client Lost Every Opportunity Record

This is what a Salesforce data loss looks like in practice — and what having a backup in place actually changes.

US advertising agency200 Salesforce usersSales Cloud
What happened

A malfunctioning Apex trigger ran across the entire org and overwrote all Opportunity records — field values corrupted, stage history destroyed, pipeline data gone. Every open deal, every forecast figure, every relationship: wiped in minutes.

Without a backup, the options were

Manual reconstruction from email threads and exported spreadsheets, or Salesforce's Data Recovery Service — $10,000 flat fee, 6–8 week turnaround, and no guarantee of completeness. Many orgs never fully recover.

With our backup in place

We identified the clean checkpoint from before the trigger ran, restored into a sandbox for validation, confirmed record counts and field values, then promoted back to production. Total time: half a day. Additional cost: zero.

A Backup Process You Can Actually Rely On

Automated

Backups Run on a Schedule, Not on Memory

Once configured, your org is backed up automatically on a recurring schedule. No one has to remember to run an export — it simply happens in the background.

Recoverable

Restore in Minutes, Not Days

When something goes wrong, you restore from a known-good backup instead of rebuilding records from spreadsheets, emails, or memory.

Compliance-Ready

A Documented, Defensible Process

A configured retention policy and backup schedule give you a clear, documented answer when customers, auditors, or leadership ask how your data is protected.

Pick the Day, Not Just the Latest Snapshot

Every scheduled backup becomes a restore point — go back to before a bad deploy, not just to yesterday.

Mon
Tue
Wed
Restore Here
Thu
Fri

A bad bulk update on Friday doesn't mean losing the week. Restore your org back to any checkpoint in your retention window in minutes.

Set Up Once, Protected Going Forward

Audit Current Setup

We review your org's objects, data volume, and existing export or backup habits to understand what actually needs protecting.

Configure Backup Schedule & Retention

We set up automated backups on a recurring schedule with a retention policy sized to your org and compliance needs.

Validate the Restore Process

We run a real restore to confirm the backup actually works end-to-end, then hand the process over to your team with clear documentation.

What Your Salesforce Backup Covers

A properly configured Salesforce backup captures both your data and the metadata that gives it meaning — so a restore doesn't leave you with mismatched fields or broken layouts.

  • Standard objects: Leads, Contacts, Accounts, Opportunities, Cases
  • Custom objects and all custom fields
  • Files and Attachments (Content Documents)
  • Salesforce metadata: page layouts, flows, validation rules
  • Record relationships and lookup field values
  • User and profile configuration

How Often Should Salesforce Data Be Backed Up?

There is no single right answer — the correct automated backup frequency depends on how much data you can afford to lose, known as your recovery point objective (RPO).

Daily

The Right Default for Most Orgs

A daily automated backup schedule is the right starting point for most sales-active orgs — it caps your maximum data loss (RPO) at 24 hours without adding unnecessary storage overhead.

Twice-Daily

For High Lead or Deal Volume

Teams with heavy inbound lead volume, high deal velocity, or multiple integrations writing to Salesforce benefit from twice-daily automated backups to tighten the restore window.

Weekly

Compliance Floor, Not a Target

Weekly is the minimum frequency that satisfies most compliance frameworks, but it is a poor fit as your only backup cadence if the org is actively used for daily sales or service work.

What Actually Happens When You Restore

An automated backup is only as good as the restore behind it. Here is the process we validate during setup, step by step.

  • Step 1: Identify the affected records and the time window before the data loss occurred
  • Step 2: Choose the correct backup checkpoint from your retention window
  • Step 3: Restore into a sandbox first — never directly into production
  • Step 4: Validate record counts, field values, and relationships against the original org
  • Step 5: Promote the verified data back to production and document what was restored

Which Regulations Require a Salesforce Backup — and What Satisfies Them

GDPR, HIPAA, and SOC 2 are mentioned on every backup vendor page. Here is what each one actually requires and what configuration satisfies the specific clause.

HIPAA45 CFR §164.308(a)(7)
Contingency Plan
What it requires

A documented data backup plan, disaster recovery procedure, and evidence of testing. The covered entity must establish and implement procedures to create and maintain exact retrievable copies of electronic protected health information.

What satisfies it

Automated off-platform backup with a documented retention policy, plus a sandbox restore test you can show an auditor. The test log is your evidence.

GDPRArticle 32
Security of Processing
What it requires

The ability to restore availability and access to personal data in a timely manner in the event of a physical or technical incident. Controllers must implement appropriate technical measures to ensure resilience of processing systems.

What satisfies it

A point-in-time backup stored outside the primary processing environment with a defined RPO and RTO. Off-platform S3 storage means a Salesforce incident does not affect your recovery capability.

SOC 2CC9.1
Risk Mitigation
What it requires

The entity identifies, selects, and develops risk mitigation activities including controls to protect against disruptions that could affect the availability of the system.

What satisfies it

Automated, scheduled backups with documented recovery procedures and backup logs your auditor can inspect. A restore test report serves as evidence of control effectiveness.

Note: Salesforce's Business Associate Agreement (BAA) covers Salesforce as a platform — it does not cover your backup strategy. Off-platform storage in S3 is separate from Salesforce's BAA and requires its own data handling agreement with your storage provider.

What Salesforce Backup Actually Costs — at Your Org Size

No other page publishes this. Vendor sites hide pricing behind forms. Here is what each option costs for 20, 50, and 100-user orgs, including the cost of having no backup at all.

Option20 users / yr50 users / yr100 users / yrRestore typeStorage location
Salesforce Data Export (native)No automation, no point-in-time restore$0$0$0Manual CSV import onlyInside Salesforce
Salesforce Backup & Recover~$2.90/user/month — shares Salesforce infrastructure~$696~$1,740~$3,480Point-in-time, record-levelInside Salesforce
Spanning Backup~$4.00/user/month — enterprise feature set~$960~$2,400~$4,800Point-in-time, field-levelInside Salesforce
OdasevaStarts ~$1,750/month — enterprise segment only$21,000+$21,000+$21,000+Enterprise, full org restoreOff-platform
Radix2 Setup (S3)No per-user fee. Storage cost ~$1-5/month depending on org size.$500 one-time$500 one-time$500 one-timeFull restore validated before handoffOff-platform (S3)
No backup (Salesforce recovery service)Salesforce charges $10,000 per incident. Outcome not guaranteed.$10,000+$10,000+$10,000+6–8 week SLA, not guaranteedN/A

Pricing sourced from vendor sites and third-party review platforms, July 2026. Spanning and OwnBackup pricing may vary by contract term and Salesforce edition.

Where Your Backup Lives Matters as Much as Whether You Have One

Most teams do not consider this until it is too late. Salesforce-native backup tools store your backup inside the same infrastructure as your live org.

On-platform backup

Salesforce Data Export & Backup and Recover

Your live data and your backup both live inside Salesforce's infrastructure. A Salesforce platform-wide availability event affects both simultaneously. You cannot restore if the platform you are restoring from is unavailable.

Affected by Salesforce outages: Yes
Off-platform backup (how we set it up)

Automated export to Amazon S3

Backups are exported and stored in Amazon S3 — completely independent from Salesforce infrastructure. A Salesforce outage, data center issue, or platform failure has no effect on your backup files or your ability to restore once the platform recovers.

Affected by Salesforce outages: No

When does OwnBackup or Spanning make sense?

Enterprise tools are the right choice when you have 500+ users, need field-level granular restore (individual field history, not just record snapshots), have a dedicated Salesforce compliance team requiring enterprise SLA documentation, or use sandbox seeding from production data at scale.

For most 10–200 user orgs, the per-user subscription cost ($2.90–$4.00/user/month, or $3,480–$4,800/year for 100 users) outweighs the marginal benefit over a well-configured off-platform backup. We help clients make this call honestly. If OwnBackup is the right fit, we will tell you so.

Salesforce Backup & Restore, Answered

How do I automate Salesforce data backup?

You have two main options: Salesforce's built-in Data Export (found under Setup → Data Management → Data Export) runs weekly or monthly and requires manual download. For true automation — scheduled exports, off-site storage, and a validated restore — you need a configured backup process or a third-party tool. Radix2 sets this up for a flat $500 one-time fee.

What is the best Salesforce backup solution for a small business?

For most small and mid-size teams (10–100 users), Salesforce's native Data Export is a reasonable start but falls short in a real emergency — it requires manual steps and doesn't support granular record-level restore. Enterprise tools like OwnBackup and Spanning are comprehensive but cost $3–$6 per user per month. A configured, automated setup from a consultant (like Radix2) hits the middle ground: real automation, real restore validation, no ongoing subscription.

Does Salesforce automatically back up your data?

Not in a way most teams would consider reliable. Salesforce's Recycle Bin retains deleted records for 15 days. Data Export requires manual scheduling and downloads CSV files that you must store yourself. There is no built-in point-in-time restore for bulk update mistakes or runaway automations. A separate backup process is needed for real protection.

How often should you back up Salesforce data?

For most sales-active orgs, daily is the right default. If you have high lead or deal volume, twice daily gives you tighter restore windows. Weekly is the minimum for compliance purposes. The right frequency depends on how much data you can afford to lose — your recovery point objective (RPO).

Why does Salesforce need a separate backup solution?

Salesforce's native recovery tools are slow, incomplete, and not built for routine use. A dedicated Salesforce backup and restore process gives you a clean, point-in-time copy of your org you control on your own schedule.

Can we restore Salesforce data to any checkpoint, not just the most recent one?

Yes. Once automated backups are running, every scheduled snapshot becomes a restore point. You choose the checkpoint — yesterday, last week, or before a specific bad deploy — instead of being limited to whatever Salesforce happens to retain.

What does the $500 one-time setup include?

We audit your current data and metadata footprint, configure an automated backup schedule with a sensible retention policy, and validate that a real restore works end-to-end before handing the system over to your team.

What happens if you lose Salesforce data?

Without a backup, your options are limited: Salesforce's Recycle Bin (15 days, deleted records only), manual reconstruction from email threads, or a Salesforce Data Recovery Service request — which costs $10,000, takes weeks, and is not guaranteed. With an automated backup in place, the same scenario becomes a 30-minute restore.

Is this a recurring subscription?

No. The $500 fee is a one-time setup cost. You may still incur ongoing costs for the backup storage or tooling you choose to use, depending on your org size and retention requirements.

Do automated backups cover metadata as well as records?

Yes. We configure the backup to capture both your data and the relevant metadata, so a restore doesn't leave you with records that no longer match your current object and field configuration.

What is the step-by-step Salesforce restore process?

A validated restore follows five steps: identify the affected records and time window, choose the correct backup checkpoint, restore into a sandbox first, validate record counts and relationships, then promote the verified data back to production. Restoring to a sandbox first means a restore mistake never touches your live org.

Is automated Salesforce backup relevant for compliance and audits?

Yes. A documented, automated backup schedule with a defined retention policy gives you evidence of data protection controls for SOC 2 reviews, supports GDPR and CCPA retention obligations, and gives healthcare and financial services teams a concrete answer when frameworks like HIPAA require proof of a recovery process.

Your Data Deserves
a Way Back

A one-time $500 setup gets automated backups, retention, and a validated restore process running in your org — so the next mistake is an inconvenience, not a crisis.