Identify what actually changed before you act.
SmartSync compares structured datasets using configured business keys and comparison rules, then classifies records as new, changed, missing or unchanged.
It is part of the customer-wide DDF Plus capability layer and can be used across licensed DDF connectors where the relevant workflow supports comparison and delta-based processing.
Compare locally. Execute deliberately.
SmartSync can compare local files or structured outputs produced by licensed DDF workflows without requiring a DDF-hosted comparison service. Where a connector workflow is configured, the resulting delta can be used to focus approved execution.
- ✓ Detect new, changed, missing and unchanged records
- ✓ Match using simple or composite business keys
- ✓ Ignore agreed fields that should not drive change
- ✓ Produce repeatable delta outputs for review or downstream execution
- ✓ Support readback and reconciliation where the workflow requires it
Most recurring data work does not need everything processed again.
Teams often compare large extracts, spreadsheets or system outputs to work out what is genuinely different. Without a controlled comparison step, the alternative is repeated manual review or blindly replaying the whole dataset.
Manual comparison
Spreadsheet formulas, filters and visual checks consume time and are difficult to repeat consistently.
Full reloads
Reprocessing an entire source can create unnecessary API activity and make exceptions harder to isolate.
Unclear exceptions
Missing records, duplicate keys and unexpected differences can be difficult to separate from normal change.
Weak reconciliation
An API response alone does not always prove that the intended target state has been achieved.
How SmartSync works
SmartSync compares two structured datasets using configured keys and comparison rules, then produces a clear delta that can be reviewed, evidenced or used by a supported DDF workflow.
1. Provide the two states
Supply the agreed comparison inputs, such as previous and current files, source and target extracts, or intended and actual target state.
2. Define the comparison
Configure the matching key, including composite keys where needed, and identify fields that should be ignored.
3. Classify the delta
Identify records that are new, changed, missing or unchanged according to the configured rules.
4. Review or act
Retain the comparison output for review or use the agreed delta as input to the next controlled workflow step.
A delta you can inspect and use
SmartSync makes the comparison result explicit rather than hiding it inside a sync process.
New
Present in the new or intended state but not matched in the comparison baseline.
Changed
Matched by key, but with one or more configured comparison fields different.
Missing
Present in the comparison baseline but not matched in the new or target state.
Unchanged
Matched by key with no relevant difference under the configured comparison rules.
Business-readable comparison rules
The comparison is driven by explicit configuration rather than custom comparison code embedded in a one-off script.
Simple or composite keys
Match on one business identifier or a configured combination of fields where a single key is not enough.
Ignored columns
Exclude fields that should not trigger a meaningful change classification, such as agreed technical timestamps or system-managed values.
Repeatable outputs
Generate named comparison outputs that can be retained, reviewed and reused by later workflow steps.
Data-quality visibility
Surface duplicate-key and comparison issues that need attention before an automated action is trusted.
SmartSync has two important jobs
1. Focus execution on the delta
In a recurring Plus-enabled workflow, SmartSync can identify the records that require action so the approved process does not have to reprocess unchanged data.
2. Reconcile intended and actual state
Where the workflow requires verification, compare the approved intended target state with fresh target readback to identify anything still missing or different before treating the workflow as complete.
An API response is execution evidence, not necessarily proof that the intended target state has been achieved. SmartSync can be used with target readback to support controlled reconciliation and, where appropriate, a deliberate delta replay.
Where SmartSync fits
SmartSync is most useful where a supported workflow has a meaningful before-and-after or source-and-target comparison.
Recurring Planview updates
Identify which supported Planview records have actually changed before approved execution.
Migration verification
Compare approved intended data with fresh target readback to identify missing or unexpected differences.
ServiceNow workflows
Use configured comparison rules with supported ServiceFlow workflows where delta-based processing is appropriate.
Cross-system coordination
Prepare a controlled delta for workflows coordinated across licensed connectors using FlowBridge.
Data-quality review
Compare structured extracts to make exceptions and unexpected differences visible before action is taken.
Business-rule validation
Combine SmartSync with QueryLocal or CalcLocal where a Plus-enabled workflow needs preparation or calculated values before comparison.
Built for practical enterprise-scale comparisons
In one enterprise proof exercise, SmartSync assessed 8,752 records and separated business-relevant changes from technical-update noise. Performance varies by dataset size, structure and local environment.
8,752 records
Compared in a real enterprise proof exercise.
Business and technical change
Demonstrated the ability to distinguish meaningful business change from technical-update noise where configured.
Local execution
Comparison runs inside the customer-controlled environment.
SmartSync is included in DDF Plus
SmartSync is not licensed separately. DDF Plus is purchased once per customer and makes SmartSync, QueryLocal, CalcLocal and enhanced reconciliation capabilities available across licensed connectors where the relevant workflow supports them.
A customer with FoliosFlow Plus can use SmartSync in supported Planview workflows. If that customer later adds ServiceFlow, Plus is not purchased again. SmartSync becomes available to supported ServiceFlow workflows under the same customer-wide Plus capability layer.
Where would knowing the meaningful delta make the workflow safer?
Show us a recurring comparison, synchronisation, migration or reconciliation problem and we can assess whether SmartSync and DDF Plus fit the workflow.