How it works
After an initial full backfill, the integration asks the source for changes using a modified-since timestamp, a change cursor, a webhook or a change log. Only new, updated and deleted records move. This cuts API calls and latency, but it depends on the source reporting changes reliably, including deletions, which many APIs handle poorly.
Example
A first sync copies 80,000 historical invoices. Each hourly run after that moves the 40 or so invoices that were created, edited or voided in the last hour.
In integrations
Unify Sync is designed for incremental sync with per-object schedules and change detection where a platform lacks good change feeds. Changes on the Unify Graph can trigger webhooks, and sync history is visible in Unify Monitor. Ask how each source reports deletions. Many APIs omit deleted records from change queries, so an incremental sync can keep stale records forever without a periodic full comparison.