Data Sync Pro is licensed on three things: the Executables (rules) you configure, the Connections (Salesforce instances) you link, and your Daily Batch Limit. Executables are usually the figure that matters most when sizing — and because each Executable is a complete functional unit (one rule that delivers a whole job end to end), most Salesforce instances need far fewer than they expect.
01Executables
What an Executable is
A single, self-contained rule — one complete unit of work. Whatever the job, it's built from the same core stages every time:
What can one Executable do?
A lot. Each row below is a job a single Executable can do — which is why most teams need only a handful:
| Engine | What it lets you achieve |
|---|---|
| #Data List | Surface a live, editable list. Present a filtered, cross-object collection from a single SOQL query — pagination, column filters, dynamic filters, sorting, inline and mass edits, and row-level actions — metadata-aware and dropped onto any Lightning page with no custom component to build. Pair it with to run an action across the rows a user selects — what we call an Actionable Data List. |
| Run a multi-step operation on demand. Give users a one-click action — on a record page, or across selected rows of a Data List — that previews and lets them edit computed values before commit. | |
| #Batch | Apply any bulk action. Push a defined set of records through transformation and commit the result en masse — DMLs, emails, notifications, approvals, platform events, lead convert, data merge, and more — across millions of records, on demand or scheduled, cross-org included, chained beyond Salesforce's 100-job limit, with every run logged for retry or revert. |
| #Trigger | self-adaptive Calculate any field on save — no field cap. On a self-adaptive Trigger, any field can take a mapping formula computed on save: rollup summaries, assignment rules, any calculation. |
| self-adaptive Define all validations together — no field cap. Hold an object's entire validation logic in a single self-adaptive Trigger — one place to read and maintain, instead of scattered standalone rules. | |
| trigger action Act on other records when one changes. Cross-record DML, notifications, publishing platform events, and other side effects fired automatically on save. | |
| #Data Loader | Load a CSV without leaving Salesforce. Upload a file straight from your own org and process it inside the platform at scale — with the same mapping and transformation logic. Embed it in your own Lightning pages so users load data right where they work. |
02Connections
A saved, reusable link to a Salesforce org — either a sandbox of your current org or a separate Salesforce org. Executables point at a Connection by name, and many rules share one, so you size by the number of Salesforce instances you connect. Every Executable needs at least one Connection to run — most commonly pointing it at the current org.
03Daily Batch Limit
The most records that can be processed in a single day — counted over a UTC calendar day, midnight to midnight (00:00–00:00 UTC). Two engines count against it — #Batch and #Data Loader — so size it to your batch volume. A job already running always finishes; once the limit is reached, it's the next job that's blocked when it tries to start. This is a DSP-enforced limit — Salesforce's own platform governor limits still apply on top of it.