📋 Executive Summary
Salesforce's cloud platform comes with inherent limits on data storage and API calls that, if not managed proactively, can result in unexpected six-figure overage bills or halted integrations. Data storage overages cost roughly $250/GB/month — over 10,000x the price of commodity cloud storage. API limits are org-wide and edition-dependent, with exceeded limits blocking all integrations simultaneously.
CIOs must treat storage and API governance as an integral part of Salesforce management — monitoring consumption, implementing archiving strategies, optimizing integrations, and negotiating better entitlements upfront before they're needed.
📑 Table of Contents
- Understanding Salesforce Storage Limits
- Salesforce API Call Limits
- Monitoring Usage with Salesforce Tools
- Strategies for Optimizing Storage Usage
- Strategies for Optimizing API Usage
- Negotiating Better Storage & API Entitlements
- Tools & Strategies Reference Table
- CIO Recommendations
- Frequently Asked Questions
Understanding Salesforce Storage Limits
Salesforce categorizes storage into two types: Data Storage for database records (Accounts, Contacts, Cases, custom objects) and File Storage for attachments, documents, Salesforce Files, Content, and Chatter files. Each has separate allocations and overage costs.
| Storage Type | Base Allocation | Per-User Addition | Overage Cost |
|---|---|---|---|
| Data (Enterprise/Professional) | 10 GB per org | +20 MB per user | $125/mo per 500 MB (~$250/GB) |
| Data (Performance/Unlimited) | 10 GB per org | +120 MB per user | $125/mo per 500 MB (~$250/GB) |
| File Storage (Enterprise+) | 10 GB per org | +2 GB per user | ~$5/mo per 1 GB |
| Data (Essentials) | ~1 GB per org | Varies | $125/mo per 500 MB |
💡 Cost Scenario
Enterprise org with 100 users: Data = 10 GB + (100 × 20 MB) = 12 GB data storage. File = 10 GB + (100 × 2 GB) = 210 GB file storage. At ~2 KB per record, 10 GB holds roughly 5 million records. One SaaS company adding ~1 TB of files/year would face ~$250,000/month in file storage overages — making external storage solutions essential.
At $250/GB/month for data storage vs. AWS S3 at $0.023/GB/month, Salesforce charges over 10,000x commodity rates. The platform provides just enough for CRM needs, expecting customers to archive or offload excess. Reaching storage caps prevents new data creation or file uploads, disrupting business operations.
📋 Overpaying for Salesforce storage? Our optimization specialists identify savings and negotiate better entitlements.
License Optimization →Salesforce API Call Limits
Salesforce imposes daily API call limits — programmatic requests from external systems, integrations, or scripts. These are org-wide and scale with user licenses and edition.
| Edition | Base Allocation | Per-User Addition | Example: 200 Users |
|---|---|---|---|
| Enterprise / Professional | 15,000–25,000 per 24h | +1,000 calls/user/day | ~200,000 calls/day |
| Unlimited / Performance | ~100,000 per 24h | +5,000 calls/user/day | ~1,000,000 calls/day |
| Developer / Sandbox | 15,000 per 24h (flat) | N/A | 15,000 calls/day |
24-Hour Rolling Window
API limits reset on a rolling basis — usage from 24 hours ago "rolls off" each hour. All integration users count against the same org-wide pool. SOAP, REST, Bulk, and other platform APIs all count.
Concurrent Call Limit
Maximum 25 concurrent long-running API requests (lasting 20+ seconds) in production. Additional calls are rejected. The Bulk API has a separate limit of 15,000 batches per 24 hours.
Exceeding the daily cap causes Salesforce to block all further API requests until usage drops. All integrations — customer mobile apps, middleware, data sync jobs — halt simultaneously. APIs return HTTP 503 errors. Critical business processes can be disrupted for hours.
🤝 Struggling with API limit constraints? Our advisors help enterprises optimize integration architecture and negotiate capacity.
Salesforce Advisory →Monitoring Usage with Salesforce Tools
📊 Storage Usage Monitoring
Salesforce's Storage Usage page (in Setup) breaks down data and file consumption by object and file type. Admins should review monthly to identify large contributors — a custom object with millions of records, massive email attachments, or managed package data lingering after uninstallation.
Set up reports or dashboards to trend usage over time. Use the native Salesforce Optimizer to flag high storage usage. Salesforce sends email alerts at 100% capacity — but by then you're in crisis mode.
Best Practice: Set internal alert thresholds at 80% of storage capacity. Assign a Salesforce admin or Center of Excellence team member responsibility for monthly monitoring and reporting.
🔌 API Usage Monitoring
System Overview / Company Information: Shows "API Requests, Last 24 Hours" — a quick health check showing usage vs. maximum. Also shows 7-day and monthly trends.
Event Monitoring (Shield): Paid add-on providing granular logs of every API call — user, URI, timestamp. Export to Splunk or SIEM tools. REST Limits Endpoint: /services/data/v<version>/limits returns current usage programmatically. Poll with external scripts for automated alerts at 80-90% thresholds.
Pro Tip: Use separate integration user accounts for different systems. While this doesn't increase overall limits, it isolates and monitors usage per integration, making it easy to identify the heaviest API consumers.
Strategies for Optimizing Storage Usage
📦 Data Archiving & Lifecycle Management
Big Objects: Salesforce's native feature for storing billions of records outside standard limits — don't count against entitlements. Ideal for historical data rarely queried in real-time. Requires async SOQL or custom code (not standard reports).
External Archives: Extract aged data to AWS S3, Azure, or on-premises databases. Third-party tools (DataArchiva, OwnBackup Archiver) automate transfers preserving referential integrity. External storage costs cents/GB vs. Salesforce's $250/GB.
Salesforce Connect (External Objects): Links to external database tables — data appears as read-only objects in Salesforce without consuming storage. Slightly slower access but works well for large datasets users only occasionally reference.
Auto-Archiving: Salesforce automatically archives old events and tasks. Use analytical snapshots or summary objects to retain metrics while archiving raw detail. Always back up data before deletion.
Rule of Thumb: Delete what you don't need, archive what's old, offload to cheaper storage. Keep Salesforce lean for CRM-active data only. Our Salesforce License Optimization Service provides hands-on help.
📎 File Storage Optimization
External repositories: Integrate with SharePoint, Google Drive, Box, or AWS S3 using Files Connect. Files remain accessible within the CRM interface without Salesforce storage charges.
Attachment purging: Periodically extract and purge old attachments — especially email-to-case attachments. Set policies: attachments older than 3 years move to external storage. Version management: Multiple file versions each consume storage. Delete old versions. Tune Chatter and Enhanced Email settings to prevent double-storage.
🧹 Regular Data Cleanup
Quarterly/yearly governance cycles: remove debug logs, archived platform events, duplicates, and unused fields. Watch for managed packages storing custom object data — records can linger after uninstallation. Monitor high-growth elements: integrations creating hundreds of thousands of logging records should redirect that data externally.
📄 White Paper: 10 Salesforce Negotiation Tactics — including how to secure storage and API entitlements upfront.
Download White Paper →Strategies for Optimizing API Usage
🔧 Optimize Integration Design
Bulk API: Up to 10,000 records per batch in a single request. Inserting 100,000 records via REST = ~1,000 calls; Bulk API does it in ~10 batches. Use for migrations, periodic syncs, any high-volume scenario.
Composite API: Combine multiple sub-requests in one call. Mobile app needing account + contacts = one round-trip instead of separate calls. Caching & push-based sync: Cache commonly queried data externally. Use Platform Events or Change Data Capture to push notifications on changes — eliminating polling entirely.
Optimize queries: Selective SOQL with proper filters and indexes. Retrieve only needed fields. Faster queries avoid the 20-second concurrent threshold.
Integration Review: Our Salesforce License Optimization Service includes integration architecture assessments to identify API waste and optimization opportunities.
🎛️ Governance & Throttling
Throttle approaching limits: Implement client-side throttling — if approaching 90% of daily limit, slow non-critical transactions or queue them. Design backoff/retry logic. Schedule wisely: Distribute heavy jobs across off-peak hours. Don't let a nightly job consume 80% of calls.
Prioritize consumers: Mission-critical integrations (customer-facing) get priority over batch exports. Create an integration policy. Parallelism control: Limit concurrent threads to 25 max active Salesforce calls.
🧠 Middleware & Architecture
An enterprise iPaaS (MuleSoft, Boomi, Informatica) acts as a buffer — aggregating data, caching, providing retry logic. If multiple systems need the same data, middleware makes one Salesforce call and distributes results. Reduces redundant traffic and centralizes monitoring.
Edition considerations: Upgrading to Unlimited Edition (5,000 calls/user vs. 1,000) may be more cost-effective than building complex workarounds. Some organizations buy cheap platform licenses purely to boost the API pool.
📊 See how enterprises have optimized Salesforce licensing and avoided costly overages.
Salesforce Case Studies →Negotiating Better Storage & API Entitlements
A crucial aspect often overlooked: the opportunity to negotiate higher limits upfront, during licensing discussions or renewals. Salesforce monetizes additional usage aggressively — they can "nickel-and-dime" you on storage and API calls if not pre-negotiated.
📈 Assess & Project Needs Before Negotiations
Before renewing or purchasing, analyze data growth trends and integration roadmap. If you'll double your data in 2-3 years or launch new API-heavy systems, quantify that. Armed with projections, approach Salesforce for solutions rather than paying list prices under duress.
Key Principle: It's always cheaper to negotiate storage and API capacity before you need it. Salesforce's flexibility drops once you're already over limits. See our Salesforce Contract Negotiation Service.
💰 Negotiate Extra Storage at a Discount
Rather than buying 500 MB blocks at $125/month reactively, ask Salesforce to bundle additional storage (e.g., 50 GB) at a flat or discounted rate. Even 50% off or a one-time fee (vs. recurring) saves significantly long-term. At minimum, lock in a lower $/GB rate for future overages.
Call out storage concerns explicitly — many customers forget and get surprised. Salesforce reps have flexibility, especially when storage concerns could block adoption.
🔌 Address API Limits Upfront
Salesforce offers API Call Add-On packs — get pricing and compare against adding platform licenses to boost the pool. If considering a higher edition for API needs, use it as a bargaining chip: "Can Salesforce offer an API increase on Enterprise Edition for a fee?"
Ensure contract language provides flexibility for limit exceedance scenarios. Clarify how Salesforce will handle consistent approaches to caps.
📋 Bundle & Document Strategically
Co-term wisely: When negotiating multiple products, leverage interplay. Storing data in Heroku or Marketing Cloud data extensions can be an alternative. Address premium support (20% of net cost), sandboxes, and other upsells simultaneously.
Document everything: If a Salesforce AE verbally assures "we'll sort it out if you hit limits," get it in writing. Only the contract governs.
Expert Guidance: Read our 10 Salesforce Negotiation Tactics white paper for field-tested strategies to secure better terms.
🤝 Preparing for a Salesforce renewal? Our team has negotiated hundreds of contracts saving clients millions.
Contract Negotiation →Tools & Strategies Reference Table
| Tool / Strategy | Purpose | When to Use |
|---|---|---|
| Storage Usage Page | View data/file consumption by object. Included. | Monthly monitoring. Before data-heavy projects. |
| System Overview (API) | Quick check of API calls used vs. limit (24h). | Daily/weekly. When integrations seem slow. |
| Event Monitoring (Shield) | Granular API call logs by user, time, operation. | Large orgs needing integration attribution. |
| Data Archiving (External) | Offload old data to cheap external storage. | Fast growth. Post-merger imports. History >X years. |
| Big Objects | Billions of records within Salesforce, outside limits. | Historical/log data needing occasional async access. |
| External File Storage | Offload files to SharePoint, Box, S3 via Files Connect. | High file usage. Document-heavy processes. |
| Bulk API | High-volume data ops in batches. Far more efficient. | Migrations, nightly syncs, >10k records at a time. |
| Composite API | Multiple sub-requests in one call. | Chatty integrations and mobile apps. |
| Platform Events / CDC | Push-based integration. Eliminates polling. | Near-real-time sync without constant polling. |
| Middleware (iPaaS) | Buffer, cache, aggregate, centralized integration. | Many integrations or complex ERP/e-commerce workflows. |
| Throttling / Queueing | Rate-limit API clients to prevent exceeding caps. | Any integration build. Partner-facing APIs. |
| Data Cleanup | Delete duplicates, logs, unused fields, orphaned records. | Quarterly/yearly. Before purchasing extra storage. |
| Negotiated Add-Ons | Pre-arranged extra storage/API at negotiated rates. | During contract renewal or initial purchase. |
CIO Recommendations
✅ CIO Action Plan for Salesforce Storage & API Management
- 1. Establish ongoing monitoring & governance — treat storage and API as key operational metrics. Alert at 80% capacity. Assign clear ownership within your Salesforce admin team or Center of Excellence.
- 2. Implement a data lifecycle policy — define retention periods by data type (cases >5 years archived, inactive leads >3 years deleted). Enforce with scheduled jobs. Communicate that Salesforce isn't infinite storage.
- 3. Invest in archiving solutions — evaluate Big Objects, external databases, or third-party tools. The investment pays for itself vs. $250/GB/month overage fees. Also improves Salesforce performance.
- 4. Optimize integrations — work smarter — mandate Bulk API for high-volume ops, Composite API for chatty integrations, and event-driven patterns for real-time sync. Audit legacy integrations for refactoring.
- 5. Deploy middleware and caching — centralize data flows with iPaaS to reduce redundant API calls and provide automatic throttling and retry logic.
- 6. Engage Salesforce proactively — if you foresee limit exceedance (data migrations, marketing campaigns), talk to your account team in advance for temporary increases.
- 7. Negotiate storage & API at renewal — project growth, bundle additional storage at discounted rates, address API limits upfront. Lock in pricing for future overages. See our Salesforce Contract Negotiation Service.
- 8. Plan edition upgrades strategically — evaluate whether upgrading to Unlimited (5x more API calls) is more cost-effective than complex workarounds or add-on packs.
- 9. Clean data regularly — quarterly cleanup governance. Remove duplicates, debug logs, orphaned records. Always clean before purchasing extra storage.
- 10. Engage independent licensing expertise — Salesforce's pricing has many hidden costs. Independent advisors benchmark pricing, identify optimization, and negotiate contracts that prevent surprise bills. Our case studies show consistent savings.
Key Takeaways
Storage Is Intentionally Expensive
$250/GB/month for data storage is 10,000x commodity rates. Invest in archiving solutions — the ROI vs. overage fees is immediate and dramatic.
API Limits Are Org-Wide
All integrations share one daily pool. Exceeding it blocks everything simultaneously. Use Bulk, Composite, caching, and event-driven patterns.
Negotiate Before You Need It
Storage and API capacity negotiated upfront costs far less than reactive purchases. Use buying power at renewal time.
Monitor at 80% Thresholds
Proactive monitoring prevents crisis. Set alerts, assign ownership, treat storage/API as key operational metrics.
Salesforce Advisory Services
Frequently Asked Questions
Related Salesforce Resources
Salesforce Contract Negotiation Case Studies
How we've helped global enterprises slash Salesforce costs and secure favorable terms.
All Salesforce Negotiation Case Studies
Browse our full library of Salesforce negotiation success stories.
10 Salesforce Negotiation Tactics
Field-tested strategies for securing better terms across licensing, storage, and API.
Salesforce License Optimization Strategies
Comprehensive guide to reducing Salesforce licensing costs and eliminating shelfware.
Salesforce Org Strategy: Consolidation vs. Multi-Org
CIO playbook for single-org vs. multi-org architecture and licensing implications.
Managing ISV AppExchange App Licensing Costs
CIO playbook for controlling third-party Salesforce app licensing costs and risks.
Salesforce License Optimization Service
Hands-on service identifying optimization opportunities across your Salesforce estate.
Salesforce Contract Negotiation Service
Expert negotiators securing better terms, lower pricing, and favorable contract structures.
Related Salesforce Articles
Explore more articles in this topic area:
Optimize Your Salesforce Storage, API & Licensing Costs
Our independent Salesforce advisors help enterprises monitor usage, implement optimization strategies, negotiate better entitlements, and avoid surprise overage bills.
📚 Explore our full Salesforce knowledge base with articles, white papers, and case studies.
Salesforce Knowledge Hub →Fredrik Filipsson
Fredrik Filipsson brings 20+ years of enterprise software licensing expertise, including experience working directly for IBM, SAP, and Oracle. He has helped hundreds of organizations — including numerous Fortune 500 companies — optimize Salesforce licensing, negotiate contracts addressing storage and API entitlements, and implement governance frameworks preventing costly overages across CRM platforms.