FilePreserve archives Salesforce files by copying each file to an Amazon S3 bucket in your own AWS account, verifying the copy with a checksum, and replacing the file in Salesforce with a small text marker. Your record data is not archived or changed, and no FilePreserve server sits in the middle.
What gets archived
An admin defines an Archive Job: a source object, filter criteria (AND, OR or custom logic, the same shape as a Salesforce list view filter), a retention period and a schedule. FilePreserve archives the files attached to matching records, and, if the admin turns it on, files on related records. It never archives, moves or deletes the record's own field data. That boundary is deliberate.
What happens to each file
- The file is written to an Amazon S3 bucket that you create and own, using Salesforce's native AWS Signature Version 4 Named Credential.
- FilePreserve verifies the stored copy with a checksum.
- The file in Salesforce is replaced with a small text marker, so it stops using Salesforce file storage. The real bytes live only in your S3 bucket until someone needs them.
- An archive index record in your org keeps the checksum, storage location, and legal hold and retention state.
Where the data lives
Record data stays in your Salesforce org. Archived file bytes live in your own AWS account. FilePreserve's publisher does not host, receive or store your files, and there is no FilePreserve-owned server or database in the data path. The one storage backend that is supported and tested today is Amazon S3.
What you pay for storage
Your S3 bucket is billed to you directly by AWS at AWS's standard rates. FilePreserve's listed price is separate and includes no storage fee.
Related
This guide describes how FilePreserve works and is not legal or compliance advice. Reviewed against the FilePreserve product documentation. Have a question? hello@filepreserve.com.