FilePreserve

Buying Salesforce archiving, in six questions.

What archiving means, the gaps teams run into, and the questions to ask any vendor, including where FilePreserve fits and where it does not.

Written for compliance and Salesforce admin teams evaluating archive tools. Reviewed October 14, 2026.

Vendor questions
Ask every vendor

From the comparison table below.

  • Q1
    Where do the files live?
  • Q2
    Can a merge reach archived files with no manual restore?
  • Q3
    Is cross-record merge included?
  • Q4
    Is legal hold re-checked at deletion time?
  • Q5
    What is the written price, and what does it assume?
  • Q6
    Which certifications, with current reports?
6 questions
Answers in the table below

What is Salesforce data archiving?

Salesforce data archiving means moving older records or files off Salesforce's own storage allocation to lower-cost external storage, on a retention schedule, while keeping them retrievable for as long as they are needed. The usual reasons are compliance, audit response or storage cost.

It is a different problem from backup. A backup is a point-in-time snapshot of your whole org, meant for disaster recovery. Archiving is selective and ongoing: specific records or files, moved deliberately based on age or a retention policy, and retrieved individually rather than restored wholesale. A tool built for one does not automatically solve the other.

In a compliance setting, archiving is usually paired with two more requirements: a retention policy (how long a record must be kept and what happens afterward) and legal hold (a flag that overrides retention and blocks deletion for as long as litigation or an investigation needs it).

Common challenges with Salesforce data archiving

Most of these do not show up during evaluation. They show up the first time someone needs an archived file back, often mid-audit.

  • Storage costs grow with the org. Salesforce file storage is a metered allocation, and attachments accumulate indefinitely without an active archiving discipline.
  • Archived files can become hard to reach. Some archive tools move a file to their own storage in a way your other Salesforce tools cannot see. Getting it back can mean logging in to the archive tool's own console and restoring it first.
  • Merge and export tools often assume files are live. Tools that assemble documents from a record and its related records generally expect every file to still be in Salesforce. Once a file is archived elsewhere, they may not be able to include it.
  • Compliance requests span several related lists. An FDA CAPA or complaint response, or a CMS RADV request, rarely maps to one record's own attachments. It usually needs everything tied to a case, member or claim, assembled into one packet.
  • Legal hold has to be enforced, not just configured. A checkbox that says "on hold" only helps if every deletion path re-checks it at the moment of deletion.

How to archive data in Salesforce

  1. Find what drives storage cost and compliance exposure. Which objects hold most of your file storage, and which of those would a regulator or auditor realistically ask about?
  2. Decide retention per object or use case, not one org-wide policy. A CAPA record's retention requirement is rarely the same as a routine sales attachment's.
  3. Pick where archived files will live. Salesforce Big Objects are designed for large volumes of record data rather than file content, so check Salesforce's current documentation before relying on them for files. A common pattern is external storage, for example an S3 bucket with Object Lock enabled.
  4. Decide your retrieval path before you commit to a tool. Ask directly: once a file is archived, can it be pulled back into the merge or export workflow you already use without a manual restore first? This is the question most evaluations skip.
  5. Confirm how legal hold works. A hold should override every disposal setting, and every deletion, scheduled or manual, should re-check hold status when it runs.
  6. Test retrieval under audit-like conditions before go-live. Simulate a "produce this record's complete documentation, now" request before the first real one arrives.

Comparing your options

Archive and backup vendors differ in pricing models and in how retrieval works, and most do not publish full pricing. This guide does not quote other vendors' prices. Get written quotes, and use the questions below to compare like with like.

What to compareFilePreserveAny other archive tool
Price$499 a month, flat per org, unlimited users. Planned price; not yet purchasable.Ask for a written quote and what it assumes (seats, storage, objects).
Where files liveAn S3 bucket in your own AWS accountAsk whether files sit in your account or the vendor's.
Retrieval after archivingArchived files are detected and pulled back in when you select them for a mergeAsk whether a person must restore a file by hand before it can be merged or exported.
Cross-record mergeBuilt in: one PDF from any related list on the records you pickAsk whether it is included or needs a second tool.
Legal holdOverrides every disposal setting and is re-checked at deletion timeAsk how a hold is enforced at the moment of deletion.
CertificationsNone claimed. FilePreserve is not SOC 2 or HIPAA certified.Ask for current reports and what they cover.

Vendors in this space include DataArchiva, Odaseva, GRAX, XfilesPro and Own. Salesforce announced the Own deal in September 2024 and completed the acquisition on November 18, 2024 (Salesforce press release). FilePreserve is not trying to match these platforms on archiving depth, storage scale or certification breadth. The gap it targets is narrower: a built-in cross-record merge with automatic file restore, so archiving and retrieval are one system.

Best practices checklist

  • Inventory what drives storage costs before picking a tool. Do not archive by default without knowing what is using the space.
  • Set retention per object or use case, not one org-wide policy.
  • Before committing, confirm the tool can retrieve an archived file without a manual restore step, inside the merge or export tool you already use.
  • Test retrieval under audit-like conditions before go-live, not after the first real request.
  • Make sure legal hold overrides retention and disposal settings, and is re-checked at the moment of every deletion.
  • Know where the files actually live, in your own cloud account or a vendor's, and what that means for your compliance posture.
  • Budget for the evaluation cycle a compliance buying committee runs. This category is rarely a same-day decision.

Frequently asked questions

Is Salesforce archiving the same as backup?

No. Backup is a point-in-time snapshot of your whole org for disaster recovery. Archiving is selective and ongoing, moving specific records or files based on age or retention policy and retrieving them individually.

Can Salesforce's own archiving products handle this?

It depends on which objects and file types you need to cover, and whether the product offers per-job retention, legal hold and cross-record merge. Ask Salesforce, or any vendor, to show each of those in a demo.

Does archiving files break existing document-merge tools?

It can. If an archive tool moves files somewhere your Salesforce tools cannot read, a merge may skip them until someone restores them through the archive tool's own console. Ask any vendor how retrieval works before you commit.

How is FilePreserve different?

It combines archiving, cross-related-record merge and automatic file restore in one system, so a file being archived does not change how you retrieve it for an audit-ready export. See how it works and the pricing page.

See it on your own org.

Join the waitlist and run your own archive and retrieve test before the listing is public.