SandForge fills a sandbox, a scratch org or a Developer Edition org with realistic data: generated from a template, with no AI key, or cloned from a real record of another org, with production guardrails.
Free and MIT-licensed · no account · VS Code 1.95+ and the Salesforce CLI
Copy and everything around it from uat into .
Forge walks the relationship graph from one record, breadth first, then writes what it found into another org, parents before children, remapping every lookup on the way. No export.json to hand-write, no field mapping to keep in step with the schema.
Sample orgs and records. Everything here runs in your browser; no org is contacted.
Seed
A new Developer Edition, a Trailhead playground or a fresh scratch org is all you need. Seed fills it with realistic records linked to one another, from a built-in template. No second org, no AI key, no field rule to write.
CRM StarterStart here
dev-ed · Developer Edition
0.00/ 5 MB of data storage
Sample org and values. Everything here runs in your browser.
In VS Code
The demos on this page are drawn for it. These are the extension's own panels.
Counted from the repository and its changelog on 24 October 2026.
Safety, on by default
Nothing to switch on, nothing to remember. A Forge run can be simulated, rehearsed and read before it writes, and taken back after.
Forge and a Frozen Dataset load refuse a production org as a target. Checkpoints refuses one outright, even to read. Seed, Sync, Autopilot and DataOps ask before every write there, and DELETE is blocked outright.
SandboxScratch orgDeveloper EditionProduction
Takes every record through the write stage and writes nothing. Its results say how many records a real run would insert and how many gaps it found against the target.
The target itself judges the rows, in calls it rolls back whole: every row when the run creates 200 or fewer, otherwise one row for each object, record type and set of filled fields.
Flows, processes, workflow rules, Apex triggers, assignment and duplicate rules: what the target runs on the records a run writes, with what sends an email or a text marked. A real run asks you to confirm what fires before it writes.
Remove the records this run created: children before their parents, into the target's recycle bin. Records the target already held are kept, and so is a record changed since the run unless you include it.
Each decision of the Production Guard is recorded with the run it concerns, in Reports → Audit Trail, beside the data lineage of the records each run carried.
Every email address is written under .invalid, the top-level domain that never resolves, as Salesforce does to the users of a refreshed sandbox. Every phone number becomes a fictional one, in its own layout. The target's automation reaches no one.
CheckpointsNew in 1.66.0
Before a test session, a demo or a training, take a checkpoint of the org. Afterwards, Rewind returns its data to that moment, whoever changed it since: you, your testers, flows or integrations.
Sample org and records. Everything here runs in your browser.
sandforge-checkpoint rewinds a CI scratch org between two test suites, without a new scratch org.Modules
One WebView UI in VS Code, no Command Palette required. Nine of them also run from the command line. Pick a name.
The org needs : use Seed.
From SFDMU or Data Loader
Paste a record Id: discovery walks the relationship graph for you, and lookups are remapped on write. Records move org to org over the API, with no mandatory CSV round-trip.
Forge reads the graph from the org itself.
Command line and CI
Eleven scripts run from a checkout of the repository with Node.js 24 and pnpm 11, without VS Code or the extension. Each lists its flags with --help, prints its JSON alone on stdout with --json, and refuses to write to a production org.
Pipelines included for GitHub Actions, GitLab CI, Azure Pipelines and Jenkins.
Only to the orgs you connect, until you turn the AI Assistant on (it is off by default) and store your own key, which stays in VS Code Secret Storage. From then on, its features send what they need to Anthropic, and a failed run's error message goes too, unless sandforge.ai.errorResolution is off. Telemetry is off by default and, turned on, only writes error reports to a local log.
To read, yes, except with Checkpoints, which refuses a production org outright. Forge and a Frozen Dataset load never write to one. The writes of Seed, Sync, Autopilot and DataOps go through the Production Guard: a confirmation before each, and DELETE is blocked outright.
For moving data between orgs from your editor, yes, and without the config file. SFDMU keeps the edge for headless CI, where it is a binary you install: SandForge's command-line scripts run from a checkout of the repository.
Any org authenticated in the Salesforce CLI (sf), imported in one click.
Yes. MIT licensed, no account, no paid tier.
Forge, Seed (its templates, its wizard, CSV Upload and Clone from Org), Sync and Frozen Dataset each take back what a run created. Autopilot cannot, but a checkpoint taken before any run, on a sandbox, a scratch org or a Developer Edition, rewinds the org to it, and the rewind itself can be undone.
Install
Open VS Code, go to Extensions, search for SandForge and click Install. Or open Quick Open with Ctrl+P and paste this line.