Sync performance and guard rails
This content is for Spring ’26. Switch to the latest version for up-to-date documentation.
Server and client logic avoid pulling large, irrelevant payloads-for example skipping some account-related objects when no account batch is syncing, improving duplicate detection across chunks, and reducing redundant commercial policy data. These guard rails keep sync times and storage use lower without changing how you work in the app day to day.
For practical habits (when to run full sync, connectivity, etc.), combine this with Manual synchronisation and your organisation’s field best-practice guide if provided.