Salesforce Backup, priced in plain English. Per record metering, snapshot economics, and the renewal lever.

Salesforce Backup is bought reactively after a data incident. This guide rebuilds the buyer side conversation around retention, recovery, and renewal leverage.

Salesforce Backup and Restore is sold to compliance and operations leaders after a data incident. The pricing model is per record per month with a retention window and a recovery service line.

The buyer side question is not whether to buy backup. It is whether to buy Salesforce Backup or to keep the third party stack with Salesforce as the system of record.

This guide covers the 2026 pricing shape, the metering surprises, the third party alternatives, and the renewal lever. Read alongside the Salesforce advisory practice, the Salesforce knowledge hub, and the Salesforce pillar hub for the wider context.

The pricing model

Per record metering

Salesforce Backup is metered per record stored across the snapshot history. The unit is one record month. A million record org with daily snapshots over ninety days bills against ninety million record months.

Indicative rate band

• List rate. Around ten dollars per thousand record months.
• Volume tier. Five to seven dollars in committed estates.
• Multi org discount. Negotiable for global estates.
• Restore service. Priced per restore event for large rollbacks.

Metering surprises

Snapshot count

Daily snapshots over a ninety day window produce ninety record copies per record. Retention is the variable that drives the bill more than data volume.

Related object inclusion

• Standard objects. Counted as expected.
• Custom objects. Counted, often with surprising weight on attachment fields.
• File attachments. Counted separately by size.
• Big object backups. Often excluded by default. Confirm scope explicitly.

Recovery posture

RTO and RPO

Recovery point objective is the snapshot interval. Daily is the default. Hourly is achievable but expensive. The buyer side question is what the business actually needs, not what the platform supports.

Restore testing cadence

• Quarterly partial restore test. Validate one object family.
• Annual full restore test. Validate the entire org schema.
• Post deployment validation. After every major release.
• Compliance audit alignment. Match restore evidence with audit cadence.

Negotiation framework

Anchor on retention, not data volume

The Salesforce account team frames the conversation on data volume. The buyer side counter is to frame it on retention window. A ninety day retention is the default. A thirty day retention is enough for most compliance frameworks.

Terms to negotiate

• Retention flex. Right to shrink retention without retroactive pricing.
• Object scope. Confirm big object and attachment treatment.
• Restore credits. Pre paid restore events bundled into the deal.
• Audit report access. Granular per object reporting.

What to do next

1. Pull the current org record count by object family for the trailing twelve months.
2. Confirm the retention window required by the relevant compliance frameworks.
3. Audit big object and file attachment treatment in any existing backup proposal.
4. Run a quarterly partial restore test and an annual full restore test.
5. Compare Salesforce Backup against the leading third party tools on price and on RTO.
6. Negotiate retention flex, object scope, pre paid restore credits, and reporting access.
7. Align the backup renewal anniversary with the main Salesforce renewal anniversary.
8. Brief the Salesforce advisory practice and run the proposal through a buyer side review.

Frequently asked questions

How is Salesforce Backup priced?

Per record month across the snapshot history. The unit is one record stored for one month, counted across every snapshot retained in the window.

What is the typical retention window?

Ninety days is the default. Thirty days is enough for most compliance frameworks. Buyer side discipline is to size the window to actual requirements.

Are file attachments in scope?

Yes, but priced separately by size. Big objects are often excluded by default. Confirm scope explicitly in the proposal.

Is Salesforce Backup cheaper than third party?

Not always. Third party tools are often competitive on price and offer data sovereignty options that Salesforce Backup does not. The break even depends on org size and compliance posture.

How often should we test restore?

Quarterly partial restore. Annual full restore. Plus a validation pass after every major release.

Can we negotiate restore credits into the deal?

Yes. Pre paid restore events should be in the deal. The unit cost of an unplanned restore is materially higher than the negotiated rate.

Does Salesforce Backup cover Sandboxes?

Sandbox backup is typically out of scope. Confirm the production and sandbox split explicitly.