Data mapping and anonymization
Restores can transform values as records load into the target org — masking sensitive data, rewriting org-specific values, or clearing fields. Nothing in your snapshot is ever modified; the rules apply only to what lands in the target.
Anonymize (per object)
In the scope builder, open an object's Anonymize dialog and add a rule per field. Each rule replaces the field's real value with:
- a generated value — pick a variable like
$Email, and every record gets a realistic random value; - a blank — clear the field entirely; or
- a custom value — one fixed literal for all records.
[SCREENSHOT REQUIRED: Anonymize dialog with field rules using generated variables]
Generated-value variables
Variables produce realistic, random values per record. Commonly used ones include:
| Variable | Example |
|---|---|
$Firstname / $Lastname | "Carolina" / "Kohler" |
$Email | "maritza@farrell.org" |
$Company | "Aufderhar LLC" |
$Address / $City / $Country | realistic address parts |
$Url / $Domain | random web addresses |
$Number | random digits — $Number_10 for 10 digits |
$Words | random words — $Words_2 for two |
$UUID | a random unique identifier |
$Today | current date — $Today_12 = +12 days, $Today_-10 = −10 days |
TODO: Confirm the complete, current list of variables shown in the anonymize dialog.
Data mapping (whole scope)
The toolbar's Data mapping dialog rewrites values across the entire scope with rules of the form:
Object · Field · Record Id · Old value → New value
Use * as a wildcard for any object, any record, or any current value. The new value can be a literal, a generated-value variable, or blank to clear the field.
Examples:
| Rule | Effect |
|---|---|
* · OwnerId · * · * → 005… | Reassign every restored record to one owner |
Account · Name · * · * → $Company | Random company name on every account |
Account · Tech_ID__c · * · azerty → qwerty | Replace one specific value wherever it appears |
Contact · Email · * · * → $Email | Random email on every contact |
[SCREENSHOT REQUIRED: Data mapping dialog with several rules and the wildcard column]
Ignore fields (per object)
Fields you add to an object's Ignore fields list are never written to the target — every other captured field is restored as-is. Typical candidates: formula/read-only fields, integration-managed fields, or values that must not cross environments.
Where you see it all again
The restore pre-flight shows a read-only Data mapping & field changes recap of every rule before you launch — one last check that the right transformations are in place.