Syntharil copies the records you choose from one Salesforce org into another — filtered per object, PII masked in transit, relationships intact — and refreshes just what changed, whenever you want.
Sandboxes drift out of date fast, and refreshing them the platform way means waiting on refresh windows and re-provisioning a whole org. Replication treats sandbox data as something you pull on demand: choose the objects, filter the rows, and copy them into an org you already control — then keep it fresh incrementally instead of starting over.
Authorize the source and target over OAuth. Credentials stay with Salesforce; tokens are encrypted at rest.
Pick the objects to copy and narrow each one with its own SOQL filter — a subset of Accounts, last quarter’s Opportunities, whatever the target needs.
The first run copies everything you selected. After that, refreshes move only what changed — on demand, not on a platform timetable.
Copy exactly the subset you need — each object gets its own WHERE clause instead of an all-or-nothing clone.
Lookups and master-detail references are remapped to the new IDs, self-referential and polymorphic (WhoId/WhatId) fields included, with objects inserted in dependency order.
Deterministic masking runs during the copy, so the target only ever receives masked values and cross-object references stay consistent.
CreatedDate and LastModifiedDate survive the copy, so date-driven reports and logic behave like production.
Files (ContentVersion), classic Attachments, and Documents come along with the records they belong to.
On delta refreshes, records deleted at the source are removed from the target — only ones this configuration created, never anything else.
Optionally align the target’s schema with the source before data lands, so custom fields exist where the data expects them.
Record types are matched between orgs by developer name, so records keep the right type on arrival.
A replication config runs in one of two strategies. Full copies the selected data from scratch every run. Hybrid does a full copy once, then switches to incremental delta refreshes: each run picks up records created, changed, or deleted since the last one, using per-object watermarks. That turns a sandbox refresh from a re-provisioning event into a quick, repeatable pull — run it before a testing cycle, after a big data load, or whenever staleness starts to bite.
Weighing it against a Full Copy Sandbox? See the full comparison → — and how masking works during the copy →
Connect both orgs over OAuth, pick the objects (and per-object SOQL filters) to copy, and run. Records land in the target with lookups remapped, insert order handled, and PII masked in transit.
Yes. Replication copies into an org you already own over the API, so you can refresh on demand — and Hybrid strategy makes each refresh incremental instead of a full re-copy.
Yes. Every object in the configuration takes its own SOQL filter, so you copy exactly the subset you need.
Yes. Lookup and master-detail references are remapped to the new target IDs — including self-referential and polymorphic fields — and objects are inserted in dependency order.
Yes. Deterministic PII masking runs in transit: email, phone, and SSN-type fields are auto-detected, and masked values stay consistent across objects.
Yes — Files (ContentVersion), classic Attachments, and Documents, scoped to the records being copied or org-wide.