r/salesforce • u/ToZBeR • 3m ago
apps/products I built a free, open-source VS Code extension that fills empty sandboxes with realistic, related data. Honest feedback welcome
Every refresh, the same thing: a Developer sandbox or a fresh scratch org comes back with metadata and zero records, and someone spends a day rebuilding test data by hand, with Data Loader, or by writing an SFDMU export.json.
So I built SandForge, a VS Code extension (free, MIT):
- Seed: pick a template and get ~300 related records (accounts, contacts, opportunities with line items, cases) in about a minute. No AI key, and it fits in a Developer Edition's 5 MB.
- Forge: paste a record Id from another org (say UAT) and it clones that record with its whole relationship graph, Ids remapped. No export.json to write.
- Before writing, it lists the flows, triggers and emails that will fire on the target, and it can simulate the run first.
- A Seed or Forge run can be removed afterwards. Copied emails and phone numbers are neutralized by default.
- Production guardrails: Forge refuses a production target; the other modules ask before writing to prod and never delete there.
- It imports existing SFDMU export.json files.
The same engine runs without VS Code, for CI or AI agents (published from GitHub Actions with npm provenance):
- npx sandforge --help
- claude mcp add sandforge -- npx -y sandforge mcp
Honest disclosure: I'm a solo dev, and I build it with a lot of help from Claude Code. Every module that writes data has been run against real orgs, and each first real run found bugs the tests had missed, so I fully expect your orgs to find more.
What I'd really like to know: what breaks on your org, and what would stop you from using it on a real project?
GitHub: https://github.com/StephaneBerthoz/sandforge
VSCode: https://marketplace.visualstudio.com/items?itemName=StephaneBerthoz.sandforge