Forge Load#

Forge Load runs managed data loads with a safety net: a snapshot is taken before every write, and any load can be rolled back with one click.

The shape of a load#

1. Upload a file (CSV, XLSX, XLS) or build the dataset from a SOQL query.
2. Map and edit. The grid is the source of truth — edit values inline, map columns to fields. Forge blocks you from running with unsaved edits.
3. Preview. See exactly what will change before anything is written.
4. Snapshot + execute. Forge snapshots the records it's about to touch, then writes.
5. Roll back if needed — to the snapshot, including recreating deleted rows.

Full CRUD, selectable API#

Load supports update, insert, upsert, and delete, and lets you pick the Salesforce API for the job — Bulk for volume, REST for small precise loads, Tooling for metadata.

Conflict-aware rollback#

Rollback is three-way aware: it restores the pre-image, but if a record changed again after your load, Forge surfaces the conflict instead of blindly clobbering. Deletes are reversible too — a rolled-back delete recreates the records and re-maps their ids.

Patterns#

Forge Patterns are parameterized, safety-gated load templates for common operations — Sandbox Email Invalidation, Bulk Owner Reassignment, Picklist Value Migration. Each compiles down to a managed load, so it inherits snapshot, verify, and rollback for free. A pattern refuses to run on an unsafely-broad selection.

Tip: Because every pattern and every SOQL-Studio write becomes a managed load, there's exactly one write path in the platform — and it's the snapshotted, reversible one.