When Do You Use Change Data Capture?

1. Day 0 copy of the entire data set to the external system
2. Continuous synchronization of new and updated data to the external system
3. Reconciliation of duplicate data between the two systems

Change Data Capture is the continuous synchronization part of replication (step 2). It publishes the deltas of Salesforce data, for new and changed records. Change Data Capture requires an integration app for receiving events and performing updates in the external system.

For example, you have a human resource (HR) system with copies of employee custom object records from Salesforce. You can synchronize the employee records in the HR system by receiving change events. You can then process the corresponding insert, update, delete, or undelete operations in the HR system. Because the changes are received in near real time, the data in your HR system stays up to date.

Use change events to:

• Receive notifications of Salesforce record changes, including create, update, delete, and undelete operations.
• Capture field changes for all records.
• Get broad access to all data regardless of sharing rules.
• Get information about the change in the event header, such as the origin of the change, which allows ignoring changes that your client generates.
• Perform data updates using transaction boundaries.
• Use a versioned event schema.
• Subscribe to mass changes in a scalable way.
• Get access to retained events for up to three days.