How Incremental Sync Works
After the initial full sync, Data Mission Sync uses incremental synchronization to efficiently transfer only the records that have changed since the last sync. This dramatically reduces sync time and API usage.
For most Dataverse tables, incremental sync uses the native Change Tracking API:
1. First sync: Data Mission Sync requests all records plus a delta link (a token that represents the current state)
2. Subsequent syncs: Data Mission Sync calls the delta link to retrieve only new, updated, and deleted records
3. The delta link is updated after each successful sync
Delta Link Processing
The Change Tracking API returns three types of changes:
| Change Type | Description |
| Insert | New records created since the last sync. These are added to your target database. |
| Update | Existing records that have been modified. The entire record is retrieved and the target is updated. |
| Delete | Records that have been deleted in Dataverse. Handled according to your Delete Mode setting (Soft or Hard delete). |
| 💡 Note: Some special tables like the Audit table do not support Change Tracking and use a timestamp-based watermark instead. See Audit Log Handling for details. | |