The promise
See it first. Take it back. Keep the receipt.
Three rules for safe Salesforce data changes. Every app we make follows them, and we follow them ourselves when we work in your org.
Why these three
Think about the worst day you’ve had in Salesforce. Not the slow days. The bad one.
Odds are it went like this. Something changed a lot of records at once: an import, a merge, a mass update, a Flow someone activated. Nobody saw beforehand what it would do. There was no clean way to reverse it. And when people asked what happened, piecing it together took longer than the fix.
Three things were missing. A look ahead. A way back. A record. That’s the whole idea.
Preview: see it first
Nothing important should happen to your data until you’ve seen what it will do.
In practice: Portage validates every row of an import and shows old and new values before anything saves. Slipway does a dry run of a lead conversion. Sluice shows the surviving record before a merge. Purser shows the real document before it’s filed.
A preview turns “I hope this is right” into “I can see this is right.”
Undo: take it back
A mistake you can reverse in a click is a small mistake. A mistake you can’t reverse is an incident.
In practice: Sluice takes a backup before every merge, so the merge can be undone. Slipway can undo a conversion, and tells you what will be deleted before it does. Wake restores an earlier value of a field. Sextant undoes a sync.
People who know they can take something back are more willing to do it. That’s how cleanup finally gets done.
Prove: keep the receipt
When someone asks who changed it, when, and from what, there should be an answer, and it shouldn’t take an afternoon.
In practice: every import has a job history. Every merge, sync and conversion is logged. Every generated document records the template version that made it. Wake keeps field history for the fields you choose, well past the native limits.
A record isn’t about blame. It’s what lets you say “here’s exactly what happened” and move on.
Where a rule doesn’t apply, we say so
Not every app has all three, and we won’t pretend otherwise.
Sounding only reads your data, so there’s nothing to undo. A clone made by Sistership is a new record, so “undo” means deleting the copy. Converting a lead into an existing contact in Sluice can’t be reversed, which is why it has its own permission and a warning.
Each app page has a Preview, Undo and Prove strip. Where one of them is “not needed” or “not possible,” that’s what it says.
Why it matters more now
For years, the one making bulk changes was a person, who could at least look worried before clicking. Now it might be an AI agent, which won’t.
An agent acts quickly, takes your data at face value and doesn’t get a bad feeling about a file. The three rules apply to it just as they do to a person: show what it’s about to do, be able to reverse it, keep a record of what it did. If you’re planning for agents, start with the data they’ll run on.
See it on your own data
Pick the job that worries you and we’ll walk through it together.