Third-Party System -> Account Data Sync History

Supports multiple methods for synchronizing historical data: by time range, by source data ID, by custom conditions, or by CRM data scope (only for full-reload scenarios), meeting different data-reload needs.

Tasks run per object and depend on integration flow configuration. If an object has multiple enabled integration flows, all those flows will execute the task; you can view them in the “Associated Integration Flows” column.

Task execution logic by object: the system pulls data into a staging table, then triggers the different integration flows from the staging table.

Batch Sync by Time Range

• You can select multiple time ranges as needed; the system creates separate tasks in the configured order and executes them sequentially.
• You can set the time slice; the default is 24 hours. Increase the slice if the Account data volume is large.

Re-sync by CRM Data Scope

Problem scenario: For data that already has mappings in the staging table (for example, data previously loaded but later requirements changed and you need to reload certain records), the system can match CRM records to their corresponding external-system IDs and re-sync those external records to CRM. Typical use cases include filling in fields that were missed in previous syncs.

Execution logic: CRM record ID -> lookup corresponding external data ID in the staging table -> re-sync those external records into CRM.