Syntharil extracts the records you choose — with their full parent-to-child families — into encrypted object storage, then optionally purges them from Salesforce with verified, clearly-flagged guardrails.
Salesforce data storage is some of the most expensive disk you can buy, and old cases, closed opportunities, and years-old logs sit on it forever. Archiving moves cold records out of the org into storage you can afford — without losing them, and without deleting anything before it is safely extracted and verified.
Define the records to archive and preview exactly what a run would touch — object by object, with counts — before anything happens.
Records and their related families are extracted and written to encrypted object storage. Nothing is removed at this stage.
After the archive is verified by read-back, remove the records from Salesforce — soft (recycle bin) or explicitly-flagged hard purge.
Archiving a record takes its related children along, so the archive holds a complete, coherent picture — not orphaned rows.
Archive the union of several object families in one configuration; empty criteria means all records of that object.
Each run is encrypted with a key unique to your team; storage only ever holds ciphertext.
Archives decrypt in-app on download, only for authenticated members of your team.
Per-object and total row caps keep a run inside the blast radius you intended.
Purge only runs after the archive is verified by read-back — soft purge keeps records recoverable in the recycle bin for about 15 days; hard purge is explicit and clearly flagged as irreversible.
Every archiving configuration runs in two phases. Plan is a dry run: it resolves your criteria against the org and reports what would be archived, object by object. Apply performs the extraction to encrypted storage — and only if you enabled purge, and only after the archived data has been read back and verified, does anything get removed from Salesforce. Soft purge sends records to the recycle bin (recoverable for about 15 days); hard purge frees storage immediately and is flagged for what it is: irreversible.
Need the opposite — getting data into an org? See replication → or the full platform →
Archive cold records — old cases, closed opportunities, historical logs — to encrypted external storage, then purge them from the org. Storage in Salesforce is premium-priced; archived storage is not.
Yes. Each run is encrypted with a per-team key before it reaches storage, which only ever holds ciphertext. Downloads decrypt in-app for authenticated team members only.
Yes. The Plan phase is a dry run that reports exactly which records and how many would be affected, before anything is extracted or removed.
Archiving follows parent-to-child relationships, so a record’s family is extracted together and the archive stays coherent.
Purge only runs after the archive is verified by read-back. Soft purge keeps records in the recycle bin for about 15 days; hard purge is separate, explicit, and clearly flagged as irreversible.
Download it from the app — archives are decrypted on download for authenticated members of your team, as files you keep wherever you like.