Running low on Salesforce data storage: your options before you buy more

The short answer: The Salesforce data storage limit for most editions is 10 GB per org plus a per-user amount, and most records count about 2 KB each, whatever they hold. When you run low, check Storage Usage in Setup, find the objects that fill it, and work down this list: delete what’s truly disposable, archive, use Big Objects, move data outside Salesforce, then buy more.

Storage Usage says 96%. Your account manager has already offered to fix that for you, which is kind of them. Before you say yes, it’s worth asking what’s in there.

Most orgs don’t run out of space because of today’s data. They run out because of closed cases from 2016, tasks that logged themselves, and emails nobody will reread. Nobody decided to keep them. Nobody decided to delete them either, which is the part that usually needs fixing first.

How does Salesforce calculate data storage?

Salesforce counts most records at a flat size of about 2 KB, regardless of how much data the record holds. Salesforce’s article on estimated record sizes says “Most Salesforce records consume approximately 2 KB of data storage,” and adds that these are approximations that vary with custom fields, rich text content and related records.

The exceptions on that list matter more than the rule:

  • Person Accounts count 4 KB, because each is an Account and a Contact joined together.
  • Campaigns count 8 KB. Campaign Members count 1 KB each, but a large list adds up.
  • Articles count 4 KB, and email messages vary. Salesforce’s example is a 100 KB HTML email taking 100 KB.
  • Quote, Order and Work Order line items each carry their own 2 KB.
  • Files aren’t part of data storage at all. They count separately, at their actual size.

At 2 KB a record, 10 GB is roughly five million records. That sounds like plenty until you count the activities.

How much storage does your edition get?

For data, Salesforce Help lists a minimum of 10 GB per org, plus an amount for each user license. Professional and Enterprise add 20 MB per user, and Unlimited and Performance add 120 MB per user. Essentials and Starter get 10 GB with no per-user addition. Salesforce’s example: a Professional org with 10 users gets 10.2 GB.

For files, Salesforce lists 10 GB per org for Professional, Enterprise, Unlimited and Performance, and 1 GB for Essentials and Starter. The minimums apply to Salesforce and Salesforce Platform user licenses, and orgs with custom user licenses need to ask Salesforce for exact figures.

One thing catches people out: Salesforce says file and data storage are calculated asynchronously. Delete a million records and Storage Usage may not move for a while. Don’t delete a second batch because the first looks like it didn’t work.

How do you see what’s using your storage?

Open Setup and go to Storage Usage. Salesforce’s file storage article points admins there to see current usage and the major contributors. Salesforce’s record size article refers to the same area as “Monitor Data and Storage Resources”. Read two things:

  1. Which objects hold the most records. Multiply by the sizes above for a rough guide to where the space is.
  2. Whether the problem is data or files. They have separate allocations, and the fixes differ.

For files, the same article notes that Content Bodies typically contribute the largest portion of file storage. Reduce it by deleting the related ContentDocument and ContentVersion records, not the Content Body directly.

What usually fills Salesforce data storage?

Activities, cases, email messages and campaign members, mostly. These are high-volume, low-regret records that pile up quietly, and most of them are never opened after the quarter they closed. That’s my observation, not a Salesforce statistic, so check your own Storage Usage first.

Email messages are the one to watch. A plain-text message is small, but an HTML one with a signature, logo and disclaimer can be much larger, and a busy case queue generates a lot of them.

What are your options, in order?

Work in this order, because each step is easier to reverse and less work to run than the one after it.

1. Delete what’s truly disposable. Test records, junk leads, spam cases. Salesforce’s deletion article says deleted records stay in the Recycle Bin for 15 days, and that after you empty it, “once purged, they cannot be recovered.” Delete through the UI for small volumes and Data Loader for big ones.

2. Archive. Move old records out of data storage into somewhere you can still read them. Salesforce has its own product for this, covered below, and some third-party apps do it too. The point of archiving is that the records are kept, with a retention period, not just removed.

3. Big Objects. Salesforce’s Big Objects guide says they’re built to hold hundreds of millions or billions of records, and describes “historical archive” as a use case. The trade-offs are real: triggers, flows and processes aren’t supported on big objects, they support only object and field permissions rather than sharing rules, and the guide says to build a custom object as a working dataset if you want reports. Salesforce’s allocations page lists big object storage for 1 million records per org on certain editions. In my opinion it’s a developer’s solution, not an admin’s.

4. External storage. Keep the records, or the files, in a store outside Salesforce and show them through a connector. It moves your retention and security questions to someone else’s system, so know who owns them before you commit.

5. Buy more. Sometimes it’s the right answer: the data is live, legally needed in the org, and can’t be shrunk. Ask your account team what’s available under your contract. It’s a decision, not a default.

What is Salesforce’s own archive product?

Salesforce Archive is Salesforce’s data archiving product. Salesforce’s page says it lets you build policies that offload inactive records, files and attachments from production on a schedule, view archived records in the context of Salesforce records, restore them one at a time or in bulk, and place records on legal hold. The page gives no edition or availability details, and it doesn’t say where archived data is stored, so ask your account team before you plan around it. Salesforce Help also documents an older Archive managed package and a migration path to the app, so check which one you have. We haven’t used either.

What can go wrong when you delete records?

Three things, and the last one hurts most. Parents take children with them, links break, and the undo window is short.

  • Cascade deletes. Deleting a parent can delete its children. Salesforce’s recovery article notes that cascade-deleted children don’t show in the Recycle Bin, only the parent does, and that undeleting the parent brings them back. If a child was deleted before its parent, it’s permanently deleted and undeleting the parent won’t return it.
  • Broken links. Records that pointed at what you deleted lose that link. Check what refers to an object before you clear it.
  • No undo after 15 days. After a purge, the recovery article says you can only recreate records from an export, with new IDs, and you then have to relink everything yourself.

Export what you plan to delete, with Ids, first. Rehearse in a sandbox. Do a small batch.

What to do Monday:

1. Open Setup, Storage Usage, and write down the top three objects and whether data or files is closer to the limit. A Data Health Check can do this for you if you’d rather not.

2. For the biggest object, run a report by age: how many records are older than two years and untouched? Our post on data quality metrics covers staleness.

3. Ask who would object if those records vanished. If nobody can say, the answer is archive, not delete.

Where we come in

Lazarette, by GTM Cloud, is pre-release and isn’t publicly listed yet. It archives old records on a policy, previews every run including the lookups it would clear, keeps archived records readable on the parent record, and restores them. See the Lazarette page.

Questions people ask

How much data storage do I get in Salesforce?

Salesforce Help lists 10 GB per org for most editions, plus a per-user amount: 20 MB per license for Professional and Enterprise, and 120 MB for Unlimited and Performance. Essentials and Starter get 10 GB without a per-user addition. Custom user licenses need confirming with Salesforce. Check your edition’s row before you plan around a number.

Do files count toward data storage?

No. Files are tracked separately and consume their actual uploaded size, per Salesforce’s record size article. Data storage counts records at about 2 KB for most objects. Images in Article rich text fields are stored in file storage. Check both allocations in Storage Usage, because the fixes differ.

Why didn’t my storage drop after I deleted records?

Salesforce says data and file storage are calculated asynchronously, so large deletions can take time to show. Wait before concluding it failed. Also confirm you deleted the right object, because activities are often the bulk, and check Storage Usage again the next day before you decide anything else.

Sources