Salesforce Storage Full? Archive Before You Buy More

Running out of Salesforce data storage is one of the most common problems I see in orgs that have been around for a few years, especially ones with records syncing in from other systems every day. Usually nobody has done anything wrong. The org has just been quietly collecting every record it ever received, and nobody ever decided when old data was allowed to leave.

The easy answer is to buy more storage and move on. That fixes this year's problem and guarantees the same conversation next year.

The better answer is to archive everything older than a cutoff the business agrees on, get the org back under capacity, and set up a monthly job that keeps it there on its own. Here's how to think about it if you're staring at that banner.

Why Salesforce storage fills up

Salesforce gives you two separate buckets. Data storage holds records: accounts, contacts, opportunities, cases, tasks, custom objects. File storage holds attachments, files and documents. The banner you're seeing is almost always about data storage.

The allocation is smaller than most people expect. On Professional and Enterprise Edition you get 10 GB of data storage for the org plus 20 MB per user license. Unlimited and Performance get 10 GB plus 120 MB per user. A 25 person team on Enterprise is working with roughly 10.5 GB, and since most records count as about 2 KB each, a few million records gets you there faster than you'd think.

The usual culprits are not the records your team touches every day. They are:

• Integration data. Transactions, usage records, logs or events pushed in by another system every day, forever.
• Activity history. Years of logged emails and tasks, especially if an email sync tool logs everything automatically.
• Duplicates and junk. Old imports, test records and duplicate accounts nobody merged.
• Nobody owning it. Retention is the kind of decision that falls through the cracks when there's no dedicated admin, which is one of the things I see break first when an admin leaves.

The fix: archive on purpose, then automate it

1. Find out what's actually eating the space

Go to Setup and search for Storage Usage. It breaks down data storage by object, largest first. In my experience, a few objects usually account for most of it. You're rarely cleaning up everything, just the two or three objects that grow without limits.

While you're in there, check for duplicates and old import junk. Merging and deleting those is worth doing anyway, since duplicate accounts quietly break integrations too.

2. Agree on a retention rule with the business

This is the step people skip, and it's the most important one. Before anything gets deleted, sit down with whoever owns reporting, finance and compliance and answer three questions:

• How far back do people actually report on this data? (Often it's the current year plus one prior year.)
• Does anything legally need to be kept, and for how long?
• When someone needs an old record, how fast do they need it?

Write the answer down as a simple rule, like "transaction records older than 24 months move to the archive." That rule is what makes the rest of this boring, which is exactly what you want.

3. Decide where archived data lives

Archiving is not deleting. The data needs to go somewhere people can still get to it. Common options:

• Your data warehouse, if you already have one and your analysts already work there.
• Salesforce's own Archive product, if you'd rather keep everything inside the Salesforce ecosystem.
• A plain export to secure cloud storage, for small teams with low retrieval needs.

Pick the cheapest option that still meets the "how fast do they need it" answer from step 2.

4. Export, verify, then delete in batches

Export the records past your cutoff, then confirm the counts match before you delete a single row. Then delete in batches, not all at once. Before you start, check for:

• Automations that fire on delete, such as flows, triggers or roll up summaries that will recalculate.
• Integrations that might try to re-sync deleted records back in.
• Reports and dashboards that quietly depend on historical data.

Expect the storage number to lag a bit. Salesforce calculates storage usage in the background, so it may not drop the moment you finish.

5. Automate the monthly job

A one time cleanup buys you a year or two. A scheduled job means you never have this conversation again. Set up a monthly archive that moves anything past the rolling cutoff, so the org stays roughly the same size no matter how much new data comes in. Give it a simple log so someone can see each run happened and how many records moved.

6. Put a number on the dashboard

Add storage usage to whatever your ops team already looks at. If it's creeping up even with the archive job running, something new is growing and you'll catch it early instead of in a banner.

How to tell if this is you

• You've seen a storage warning in Salesforce, or you're already pricing extra storage.
• One or two objects make up most of your data storage.
• Another system pushes records into Salesforce every day and nothing ever removes them.
• Nobody can tell you how long you're supposed to keep old records.
• Reports and list views have gotten noticeably slower over the past year.

FAQ

How much data storage does Salesforce include?

Professional and Enterprise Edition include 10 GB of data storage per org plus 20 MB per user license. Performance and Unlimited include 10 GB plus 120 MB per user. File storage is a separate allocation.

How do I check my Salesforce storage usage?

In Setup, search for Storage Usage. It shows how much data and file storage you're using and which objects take up the most space.

Should I buy more Salesforce storage or archive old data?

If most of your storage is old records nobody reports on, archive first. Buying storage makes sense when the data you need day to day genuinely outgrows your allocation.

Will archiving break my Salesforce reports?

It can if reports depend on historical records, which is why you agree on the retention rule first. Reports on data past the cutoff move to wherever the archive lives, like your data warehouse.

If you're looking at a storage warning and wondering whether to buy more space, I'm happy to take a look at your org with you first. Let's talk.