Salesforce data archiving moves rarely-accessed records to separate storage for long-term keeping. Unlike backups that protect active data for quick recovery, archives serve as your historical record, housing information you rarely need but must keep.
The pressure to archive builds quietly. As your org grows, records accumulate faster than anyone deletes them, and three costs compound at once: storage charges climb, reports and queries slow down as objects swell with years of closed records, and compliance risk grows because nobody can say with confidence what is being retained or why.
This guide covers when to archive rather than delete, how to build a Salesforce data archiving strategy, the best practices that keep it running, and how to optimize an archive once it exists.
When Should You Archive Data Instead of Keeping It Live?
The split between active and inactive data determines what belongs in production versus archives:
- Active data: Frequently accessed information essential for daily operations.
- Inactive data: Historical information rarely accessed but still valuable for reference or needed for compliance.
Archive data when:
- Nobody has touched it in 12+ months.
- Projects or cases have finished.
- Users have left or accounts closed.
- Records are no longer needed for daily operations or reporting.
In Salesforce the archive candidates are predictable: closed opportunities past your reporting window, resolved cases beyond the period support actually reviews, completed tasks and logged activities (which accumulate faster than anything else, since every email, call, and meeting creates a record), converted leads, old campaign members, and field history and integration logs, which most teams never look at but which quietly consume more storage than the records they describe.
Storage is where this becomes concrete. Most Salesforce editions start with 10 GB of data storage per org plus roughly 20 MB per user license, with file storage allocated separately. Data storage is charged per record at a flat rate of about 2 KB regardless of how many fields that record holds, so a lean custom object with three fields costs the same per row as an Account with two hundred. That flat rate is why activity and log objects dominate storage consumption: the volume, not the width, is what fills the pool.
The performance effect is separate from the storage effect and often matters more. Large objects slow reports, list views, and SOQL queries, and past roughly a million records you meet selectivity problems where filters that once returned instantly begin timing out. Archiving reduces the row count the query optimizer works through, which is why teams often notice reports speeding up before the storage bill drops.
Check Setup, then Storage Usage, before assuming anything. It shows both pools, the percentage consumed, and the heaviest objects and users, which is usually enough to find your first archive candidate in about ten minutes.
Consider a manufacturer that must keep quality control data for regulatory reasons. Current production data needs immediate access, but five-year-old test results can move to archives, reducing database load while staying available for audits or litigation.
Note that different industries have different retention requirements:
- HIPAA requires covered entities to retain HIPAA documentation, such as policies, risk assessments, and audit logs, for six years. It sets no retention period for medical records themselves; that is state law, and it varies considerably. See our guide to healthcare data archiving.
- Financial institutions under SOX must keep certain audit and review records for seven years.
- GDPR requires organizations to store personal data only as long as necessary for its intended purpose.
Salesforce Data Archiving Strategy
An archiving strategy is the decision layer above the tooling. Without it, teams archive whatever object hurts this quarter, then discover they cannot explain the retention logic to an auditor. Four decisions make up the strategy, best made in this order.
Identify archive candidates. Start from Storage Usage rather than intuition and rank objects by consumption. For each one, establish whether the records are genuinely inactive: last modified date, related open records, and whether any report, dashboard, or integration still reads them. That last check is the one teams skip, and it is what breaks a dashboard the week after a run.
Define retention policies per object. Every object gets a retention period, an owner, and a stated reason: a regulation, a contractual obligation, or a documented business need. "As long as necessary" is not a policy because automation cannot enforce it. Translate the requirement into a number of days so a scheduled job can act on it.
Select the storage destination. Big Objects keep archived records inside Salesforce and remain queryable without consuming standard object storage, which suits data you must retain and occasionally query. External storage costs less and scales further, but retrieval runs through an integration. The right answer usually differs per object rather than per org.
Establish governance. Name who approves a retention policy, who can trigger a restore, and how often policies get reviewed. Archiving fails as a program rather than as a technical exercise, and it fails when nobody owns the review cadence.
One distinction deserves separating out: archiving is not deletion. Archived records remain retrievable; deletion is irreversible once the Recycle Bin empties. Teams that conflate the two either delete records they had to keep or archive records they had to destroy under a data minimization obligation.
What Should a Data Archival Strategy Include?
The four components below work as a chain. Retention policies decide what moves and when, storage infrastructure determines where it lands and what retrieval costs, indexing determines whether you can find it again, and access control determines who may see it. Weakness in one undermines the rest: a well-indexed archive with no retention policy just relocates the problem, and a sound policy with poor indexing produces an archive nobody can search at audit.
1. Clear Data Retention Policies
Develop retention rules based on data categories and business functions. Your policies should spell out:
- Which data categories get archived.
- When archiving happens (time-based or event-based triggers).
- How long different data types stay retained.
Match retention timelines with compliance requirements. For example, FINRA Rule 4511 requires brokers to keep certain records for at least six years, while IRS regulations demand seven years for tax documents.
2. The Right Storage Infrastructure
Your storage choice significantly affects long-term success. Consider:
- Cloud-based archives that scale easily and include built-in redundancy.
- Salesforce Big Objects, which keep archived records on-platform and queryable.
- Hybrid approaches that balance compliance requirements with cost optimization.
Judge options based on their scalability, cost-effectiveness, and retrieval speed.
3. Smart Indexing and Classification
Data classification before archiving allows you to quickly find records when needed:
- Tag records with metadata. Apply labels like record type, sensitivity level, department, or retention period.
- Use classification schemas. Group records by business logic such as object type, compliance category, or project so teams can retrieve what they need without scanning entire datasets.
- Enable audit tracking. Every classification and archive action should generate an audit log to create a verifiable chain of custody for internal reviews or regulatory audits.
- Control access to classification settings. Role-based access ensures only authorized users can modify tagging or retrieve sensitive records.
- Label regulated data early. Flag records that fall under GDPR, HIPAA, or SOX as part of the backup or archiving workflow.
4. Built-In Security and Access Control
Archived data often contains sensitive information needing strong privacy and security protection. Make sure to use encryption both in transit and at rest, apply role-based access control to limit authorized personnel, and implement tamper-proof storage for regulatory compliance.
Advanced options like customer-managed encryption keys give organizations extra control over security.
Salesforce Data Archiving Best Practices
The practices below are what separate an archive that keeps working from one that quietly stops. Each addresses a failure mode teams hit in the first year, and the checklist groups them by the phase of the archiving cycle they apply to.
How Can You Make Data Archival Low-Maintenance?
The ongoing cost of archiving is mostly decision cost rather than compute cost: someone deciding what to move, confirming it is safe, and remembering to do it again next quarter. Automation removes the recurring manual work, and governance removes the recurring decisions by settling them once in a policy. What remains is exception handling, which is a far smaller job.
Automate It Wherever You Can
Set up automated archival processes based on predefined triggers:
- Time-based archiving for data reaching specific age thresholds.
- Event-based archiving when projects close or employees leave.
- Capacity-based archiving when storage reaches certain levels.
Keep Retrieval Simple and Reliable
An archive only delivers value if retrieval is fast, accurate, and dependable.
Granular recovery capabilities are essential because they let you restore specific records or even individual fields without rolling back entire archives. That minimizes disruption and matters most during audits, investigations, or legal discovery.
Point-in-time recovery adds another layer of flexibility. It lets you view data as it existed on a specific date, which is often required in regulatory inquiries or litigation. Legal and compliance teams rely on it to establish timelines and confirm data authenticity.
Verification turns those capabilities into something you can rely on. Test restores quarterly at minimum, and after any major org change, Salesforce release, or configuration update, since those are the moments retrieval paths break. Make each test a real restore of a real record rather than a status check, and time it: a restore that succeeds after six hours may still fail your audit-response commitment.
Verify the archive itself, not just the retrieval path. Confirm record counts reconcile between source and archive after each run, spot-check field-level completeness, and confirm relationships survived.
Govern who can retrieve. Restoring archived data is a privileged action and should not sit with everyone who can read the original records. Restrict restore rights to named administrators or a compliance function, require a recorded business justification, and review the access list on the same cadence as your retention policies. Field-level security should continue to apply to archived records.
Review and Refine Over Time
Archival strategies are not static. As your organization grows, regulations shift, and systems evolve, archive policies must be revisited.
Establish a review cadence aligned with your compliance audits, internal risk assessments, and platform upgrade cycles.
Changes to Salesforce objects, integrations, or metadata can quietly introduce blind spots into archive jobs or restore logic. Reviewing configurations after major platform updates or org restructuring prevents gaps in protection.
Gather feedback from users involved in restores too. If they consistently struggle to find data or complete a restore, your indexing or recovery workflows need revising.
Salesforce Data Archival Optimization
Optimization is what happens after the archive works. The goal shifts from moving data to making the archive cheaper, faster, and smaller over time, and each lever below runs on evidence you only have once records have been sitting in the archive for a while.
Review efficiency quarterly against four numbers: storage consumed before and after each run, average restore time, the percentage of records inside their retention window, and the count of failed or partial jobs. Those four tell you whether the archive is improving or drifting.
What Problems Do Teams Run Into and How Can You Avoid Them?
Even carefully planned archiving strategies face challenges. The table below summarizes the most common ones and how to mitigate each, followed by the detail.
Data Sprawl Across Multiple Systems
Organizations struggle when data is scattered across platforms. Start with a thorough data inventory. Create a centralized catalog tracking data locations and types, and consider tools that integrate with multiple sources for unified archival management.
Inadequate Classification and Difficult Retrieval
Poor classification leads to retrieval headaches, with employees wasting time hunting for information they need.
If you do not have one already, create a comprehensive classification scheme before archiving. Use consistent metadata tagging and add automated classification tools. Test your retrieval processes regularly with real-world scenarios, and keep manual steps to a minimum so the process is repeatable when time is short.
Recovery Time in Time-Sensitive Situations
When compliance reviews, audits, or legal discovery require immediate access, delays are expensive. Set a target retrieval time, measure against it, and design the archive around that commitment rather than discovering it mid-request.
Integration Challenges with Legacy Systems
Older systems create major hurdles and extend archival project timelines.
Early in planning, assess compatibility between your archiving solution and the systems you use. Consider middleware to bridge gaps, and evaluate whether updating legacy systems is more cost-effective long-term than complex integration work.
Scalability Concerns
As data volumes grow, archival systems struggle to keep up. Use cloud-based or easily expandable infrastructure, and confirm your approach still works at ten times current volume before committing.
Start Improving Your Data Archival Strategy
The recommendations in this guide implement in a clear sequence. Start with Storage Usage to establish a baseline and identify your highest-consumption objects. Set a retention period, an owner, and a documented reason for each one. Choose a destination per object, Big Objects for records you must keep queryable on-platform and external storage for volume. Validate the selection with the business owner and run a small first batch. Automate the cadence once a manual run has proved safe. Then test a restore, and keep testing it quarterly. For the compliance and cost side of that sequence, see our guide to balancing cost and compliance in your archiving strategy.
Good archiving balances compliance, cost-efficiency, and accessibility. It does all three only if somebody still owns the archive a year later.
Flosum, an end-to-end enterprise DevSecOps platform purpose-built for Salesforce, supports this through Backup and Archive, which is cloud-based and purpose-built for Salesforce. It captures only new, modified, or deleted data, which keeps archive growth proportional to actual change rather than total volume, and supports granular restores of individual records or fields, scheduled archive jobs, retention automation, and audit trails covering every archive, restore, and purge.
Because the interface runs inside Salesforce, users can view, compare versions, and retrieve archived items without learning another system or raising a ticket, and field-level security still applies, so they see only what they are entitled to see.
Book a discovery call to see how Flosum handles Salesforce data archiving at enterprise scale.
Frequently Asked Questions (FAQ)
Thank you for subscribing
