Salesforce data storage is one of the least-negotiated line items in the platform contract and one of the steepest unit prices in the entire enterprise software stack. The list price for incremental Salesforce data storage runs at orders of magnitude above the equivalent storage in any general-purpose cloud, and that pricing differential compounds across the contract term as the data footprint grows. Enterprises that develop a deliberate storage strategy — both contract-side and architectural-side — routinely save 40 to 70 percent on this category relative to the do-nothing trajectory.
This guide breaks down how Salesforce data storage is priced, what the included allowances look like by edition, what the per-GB add-on rates actually run at, and what archival and architectural moves contain the spend without compromising operational capability.
Salesforce data storage measures the total size of records across the org: standard objects (Account, Contact, Opportunity, Case, Lead, etc.) and custom objects. Records are billed at 2 KB per record for most standard and custom objects, regardless of the actual byte count of the record contents. Person Accounts, Email Messages, Knowledge Articles, and a small set of other object types use different per-record sizing. The 2 KB sizing means a thousand records consume 2 MB regardless of whether each record has three fields or three hundred.
The implication is that storage cost scales with record count more than with field count or record contents. Enterprises with high-volume operational use cases — service environments with millions of cases, marketing environments with millions of leads, integration environments that synchronize millions of records from upstream systems — accumulate storage consumption faster than enterprises with smaller record volumes regardless of the underlying data footprint.
| Edition | Base data storage | Per-user incremental |
|---|---|---|
| Enterprise Edition | 10 GB org-wide | 20 MB per user license |
| Unlimited Edition | 10 GB org-wide | 120 MB per user license |
| Performance Edition | 10 GB org-wide | 120 MB per user license |
| Professional Edition | 10 GB org-wide | 20 MB per user license |
| Industries / Einstein 1 | 10 GB org-wide | 120 MB per user license (with bundle inclusion in some cases) |
A 1,000-user Enterprise Edition org therefore receives 10 GB + (1,000 × 20 MB) = 30 GB of included data storage. A 1,000-user Unlimited Edition org receives 10 GB + (1,000 × 120 MB) = 130 GB. The included allowance is the first variable the buyer should compute against the actual data footprint, because the edition mix can substantially change the included storage envelope without explicit storage add-on purchases.
Salesforce data storage above the included allowance is sold in incremental blocks at list rates that typically run between $4,000 and $5,000 per GB per year. The rate varies modestly across edition tiers, customer size, and the specifics of the master agreement, but the order of magnitude is consistent. The negotiated rate after discount typically lands in the $1,800 to $3,200 per GB per year band for mid-size enterprises with reasonable negotiation discipline, and as low as $1,200 to $2,000 per GB per year for large enterprises with significant procurement leverage.
Even at the post-discount rate, the per-GB economics of Salesforce data storage are dramatically higher than general-purpose object storage in any hyperscaler. The differential reflects the fact that Salesforce storage is operational primary storage backed by indexed access, transactional guarantees, and the platform's broader query and automation infrastructure. The differential is real, but the differential also means that low-value records living in Salesforce data storage are a category where architectural intervention pays back quickly.
The largest single Salesforce storage cost reduction in recent advisory work came from archiving closed cases older than 24 months to an external data warehouse with a virtualization layer back into Salesforce. The intervention eliminated 340 GB of primary storage at an annualized cost of approximately $850K, with an archive cost of roughly $4K per year.
500+ engagements · $420M+ in client savings · 34% average reduction.
Contact Us →Five record categories drive most of the storage accumulation in mature Salesforce environments.
Email Messages and Tasks. Email logging via Einstein Activity Capture, Salesforce Inbox, and outbound email automation produces high record volumes. Email Messages are billed at higher per-record rates than the default 2 KB and accumulate fast in environments with active email integration.
Closed Cases and historical Service records. Service environments produce millions of cases across years of operation. The cases retain operational value for a defined window — typically 12 to 24 months — and then become reference data that does not justify primary storage cost.
Leads from marketing operations. High-volume marketing programs produce Lead records faster than the qualification process converts or culls them. Stale Lead records consume storage and produce minimal operational value beyond an aggregation window.
Audit and history records. Field History tracking, Setup Audit Trail records, and similar audit-category data accumulate across the contract term and frequently grow uncontrolled because the records are below the level of typical attention.
Integration synchronization tables. Custom objects used for inbound integration staging frequently accumulate records indefinitely because the integration design did not include a retention policy.
The highest-impact strategy is archiving low-value records to an external system — typically a data warehouse, lakehouse, or dedicated archive tier — with a query-time virtualization layer back into Salesforce when required. The archive typically lives at a cost of $0.02 to $0.20 per GB per month in the chosen hyperscaler, compared with the $1,200 to $3,200 per GB per year of Salesforce data storage. The cost differential is two to three orders of magnitude.
The archival pattern is well-established and supported by multiple third-party archival tools, native Salesforce Big Object capability, and custom-built archive pipelines. The selection between the options should be driven by the operational requirements: which records need query-time access from within Salesforce, which records require formal retention compliance, and which records can be archived to a cold tier without operational impact.
Salesforce Big Objects are billed differently from standard data storage and are designed for high-volume, query-pattern-limited data sets. Big Objects do not appear on most reports of storage consumption because they are billed under a separate consumption envelope. Audit data, historical interaction records, and similar high-volume categories that fit the Big Object query model can be moved to this storage tier at substantially lower cost than standard data storage.
Many storage accumulations result from the absence of a retention policy rather than from operationally required records. A formal retention policy that defines how long each object type is retained in primary storage, enforced through automated archival processes, prevents the steady-state growth that produces most of the storage cost trajectory.
Because the per-user storage allowance varies across edition tiers, the edition mix decision affects the included storage envelope. Migrating selected users to Unlimited or Performance Edition expands the included storage allowance even if the underlying functional needs of those users do not require the edition's other capabilities. The migration is rarely cost-effective for storage alone, but the storage benefit should be factored into edition decisions made for other reasons.
Storage consumption is forecastable from a small set of growth inputs: user count growth, average activity per user, the retention horizon of high-volume objects, and the integration data ingestion volume. A simple monthly forecasting model that projects consumption across the next 24 months consistently identifies storage allowance breaches 9 to 15 months before they would otherwise emerge, which provides ample time for intervention before reactive add-on purchases become necessary.
The forecasting model should run at the level of the major consuming objects rather than at the aggregate org level. Aggregate forecasts hide the specific objects that are driving consumption and obscure the targeted interventions that would otherwise be obvious. Per-object forecasts surface the high-growth categories and support the kind of targeted retention or archival decisions that produce the largest cost reductions.
Four negotiation moves consistently produce results in the storage category at contract events.
Negotiate storage pricing into the master agreement. Storage rates negotiated at the master contract are materially lower than storage rates purchased reactively during the term. Lock the rate at signing.
Negotiate growth allowances that scale with user counts. An allowance that grows automatically with user growth prevents the recurring negotiation cycle as the user base expands. The allowance can typically be negotiated at modest incremental cost.
Negotiate price protection across the contract term. The list price for storage trends upward in Salesforce's published price book. Lock the negotiated rate against price increases for the contract term.
Negotiate Big Object allowance bundling. If the operating model uses or plans to use Big Objects, negotiate the Big Object allowance into the master contract rather than purchasing it incrementally during the term.
The clearest indicator of mature storage discipline is a quarterly review of storage consumption by object type, with an explicit archival policy applied to high-volume objects approaching their retention threshold. Enterprises with the discipline contain storage growth at sub-linear rates relative to user growth; enterprises without it consistently breach storage allowances and purchase add-on capacity reactively.
Salesforce data storage is one of the highest-leverage cost optimization opportunities in the platform contract. The per-GB economics are unfavorable relative to alternatives, the consumption is driven by knowable record categories, and the architectural moves that contain the consumption are well established. Yet storage discipline is consistently weak in enterprise environments because the line item is small in any single budget cycle and the consumption grows below the level of typical attention.
Enterprises that establish the discipline — quarterly consumption review, formal retention policy, archival pipelines for high-volume objects, deliberate edition mix decisions, and contract negotiation that locks rates and growth allowances at master events — consistently reduce the storage envelope by 40 to 70 percent within two renewal cycles. The reduction sustains because the discipline persists. The aggregate impact across the engagement portfolio that informs this advisory work has contributed materially to the $420M+ in client savings produced across 500+ engagements.
The storage category rewards deliberate attention. The drivers are knowable, the negotiation moves are repeatable, and the architectural patterns are durable. Enterprises that invest the attention recover the investment many times over across the contract life.
One field-tested negotiation tactic per month. No vendor pitches.
Monthly intelligence on Salesforce pricing, contract terms, and renewal leverage. Built for buyers.