Lazarette, by GTM Cloud · Clean · Pre-release

Archive old Salesforce records without deleting them blind

Lazarette is a Salesforce data archiving tool. It archives old records on a policy you set, shows what a run would affect before it runs, keeps archived records readable on the page where people look, and brings them back when you ask.

Status: Pre-release. Built, install-tested and uninstall-tested, and not publicly listed yet. Join the pilot and we size the first policy with you.

You know this one

The storage warning email arrives again. You forward it up the chain with “we should look at this.” A month later it comes back with the same words.

You know where the space went. Closed cases from years ago, completed tasks, lost opportunities nobody has opened since the quarter they closed. Deleting them would take an afternoon. It would also clear lookups on other records and take child records with it, and after 15 days it can’t be taken back.

So nobody signs off. The warning email keeps arriving.

Salesforce data archiving that shows its side effects first

Lazarette moves old records out of data storage on a policy you set. A policy names the object, the age and the conditions, which child records travel with it, and how many records one run may take. A new policy starts as a dry run and stays one until you say otherwise.

Before a run, a preview lists the records, their children, the storage it would release and every lookup it would clear. Archived records stay readable, read-only, on the parent record’s page and in a search tab. Restore brings them back. A second policy type, Slim emails, keeps the case and its emails and gives back the storage the HTML bodies took.

A lazarette is the storage locker below deck, for gear you need to keep but don’t want to trip over. Same idea, for records.

See it first. Take it back. Keep the receipt.

PreviewUndoProve
Every run is previewed: records, children, storage released, and the lookups that would be cleared.Restore returns the original record inside the recycle-bin window, and recreates it after.A log of every run and every record, and a retention period you set.

What you get

See the side effects first

The preview counts records and children, estimates the storage released, and lists every lookup that would be cleared. A run that would lose child records refuses to start.

Copy, verify, then delete

Every record is written to the archive, then read back and compared, before it’s deleted. A record that fails verification stays where it is.

Still there when someone asks

Archived records appear on the parent’s page, as “Archived cases for this account”, and in a search tab. They’re read-only, and field access follows each person’s current permissions.

Restore is the undo

Inside the 15-day recycle-bin window, restore returns the original record, Id and all. After it, the record and its children are recreated and the references that pointed at it are re-pointed.

Slim emails

An email costs storage by its size, and the HTML body is usually the larger part. A Slim emails policy replaces old emails on closed cases with copies that keep the text and drop the HTML. The case, its emails and its history stay. The preview reads a real sample and says what it would save, and a run can be undone while the originals are in the recycle bin.

Retention and legal hold

Purge the archive after the period you set. A record on legal hold is skipped by archiving and by purge alike.

How it works

  1. Read the Health Check. See which objects use the most storage and what your org allows.
  2. Write a policy. Start from a starter: closed cases, completed tasks, lost opportunities.
  3. Preview and dry-run. Read the impact report. Fix what it finds, or narrow the policy.
  4. Run it. Take it out of dry run, choose when it runs (daily, a weekday, a day of the month, or once on a date), and add the archive list to the page.

Two readers, two reasons

If you’re the admin

You write a policy from a starter, read the impact report, and leave it as a dry run until you’re satisfied. Runs are bounded, resumable and scheduled.

If you’re the one signing off

Lazarette takes old records out of data storage without throwing them away. The team can still read an old case from the account, legal can place a hold, and you keep a retention period you can state.

Today, and with Lazarette

TodayWith Lazarette
Storage warnings and no safe moveA policy that runs on a schedule, in bounded batches
A mass delete nobody will sign offA preview of exactly what a run affects
Lookups blanked as a surpriseEvery record verified before it is deleted
“We deleted that years ago”Archived records one click from the account

Where it’s strong, and what to know first

We’d rather you find the limits here than after the pilot starts.

Where Lazarette is strong

  • A preview that lists side effects: cleared lookups, child records, attached files
  • Every record verified before it’s deleted. An unverified record is never deleted.
  • Archived records stay readable on the parent’s record page and in search
  • Restore, with its own preview of what will be recreated and re-pointed
  • Slim emails, to give back the storage the HTML bodies took
  • Retention purge and legal hold built in
  • Everything stays inside your Salesforce org

Good to know before you install

  • Lazarette isn’t a backup. It holds only what a policy archived, and it doesn’t protect against a bad deployment or a mass update.
  • After the recycle-bin window, a restored record has a new Id. Created date and created by are restored only where your org allows audit fields to be set.
  • Archived records can’t be used in reports, list views or automation.
  • Field history isn’t archived with the record, and files stay where they are in version 1.
  • The archive uses your org’s own storage allowances. The app’s Health Check shows how much room there is.
  • Slimmed emails read as plain text: no formatting, tables, inline images or clickable signature. Run a preview first.
  • It is pre-release: built and install-tested, with no public listing yet. Turn on Email-to-Case before you install; the package refers to Email Messages.

Questions people ask

What happens to records that point at an archived record?

Salesforce clears a lookup when its target is deleted. Lazarette’s preview lists every such lookup before you run, the archive records them, and restore puts them back.

Can people still see archived records?

Yes. They’re read-only, in a list on the parent record’s page and a search tab, for people with the View Archived permission who can read the parent. Field access follows their current field permissions.

What if a run is interrupted?

It resumes. A record is deleted only after its copy has been read back and compared, so an interruption can’t leave a record deleted and unarchived.

Does our data leave Salesforce?

No. The archive lives in your org, as records you can read there, and nothing is sent anywhere. That’s how it is built, not a setting.

How do I reduce Salesforce data storage?

Lazarette takes old records, such as closed cases, completed tasks or lost opportunities, out of data storage on a policy and keeps them readable. A new policy starts as a dry run, so you read the impact report first.

Is archiving Salesforce records the same as a backup?

No. Lazarette holds only what a policy archived, and it doesn’t protect against a bad deployment or a mass update. It’s a place for old records you still need to read, not a way to recover from a mistake.

Works well with

Lazarette is part of the Clean stage of the lead-to-renewal map. Not sure which object is filling your storage? A Data Health Check is a good start. Every app installs by itself. None needs another.

Built on the platform

  • Native to Salesforce. The archive lives in your org, and nothing is sent anywhere.
  • Never deletes an unverified record. There is no setting that turns this off.
  • Says what can’t be restored exactly, before the first run and not after.
  • Four permission sets: Admin, Operator, Viewer and Read Only.

Name the object that fills your storage

Lazarette is pre-release. Join the pilot: we size the first policy on your own numbers, and you help shape version 1.