Docs
You are viewing:
Product Catalog 2.0
Automatic Exports is in early access. Request access to enable this feature for your site.
Chargebee supports Incremental Sync, enabling you to export only the changes (create, update, delete) that occurred since the last successful export. Incremental Sync supports efficient Change Data Capture (CDC) workflows and reduces data processing and transfer costs by eliminating redundant full exports.
change_type
= read
.change_type
: Indicates the type of change (create
, update
, delete
, read
) and can be used to load data into the warehouse accordingly.record_extracted_at
: Timestamp when the updated data became available in Chargebee’s data lakehouse.record_exported_at
: Timestamp when the data was exported to the configured destination.incremental_sync
folder.The data is available in year, month, day, and hour-level partitions. The hour corresponds to the UTC hour when the export was scheduled. For example:
s3://<your-bucket>/<your-subfolder>/<your-domain>/incremental_sync/data/invoices/year=2025/month=08/day=15/hour=03
Use the change_type
field to determine the appropriate operation to perform in the destination system (for example, insert, update, or delete).
change_type
= delete
.record_extracted_at
to sort the records.s3://<your-bucket>/<your-subfolder>/<your-domain>/incremental_sync/schema/<dataset-name>.json
Chargebee’s incremental sync tracks data changes over time, enabling downstream systems to maintain accurate, up-to-date datasets.
The first export provides a snapshot of all existing records.
For example:
id | first_name | last_name | change_type | record_extracted_at | record_exported_at |
---|---|---|---|---|---|
1 | John | Doe | read | 2025-08-18T00:00:00Z | 2025-08-18T03:00:00Z |
2 | Alice | Brown | read | 2025-08-18T00:00:00Z | 2025-08-18T03:00:00Z |
3 | Carlos | Rivera | read | 2025-08-18T00:00:00Z | 2025-08-18T03:00:00Z |
change_type
= read
indicates a snapshot record. The first export for every table is always a snapshot of the dataset.
Subsequent exports provide incremental updates over the previous export.
Continuing the previous example, assume the following changes occur:
The following table shows how the records appear in the next export:
id | first_name | last_name | change_type | record_extracted_at | record_exported_at |
---|---|---|---|---|---|
1 | John | Smith | update | 2025-08-18T06:45:00Z | 2025-08-18T08:00:00Z |
2 | Alice | Brown | delete | 2025-08-18T07:10:00Z | 2025-08-18T08:00:00Z |
3 | Carlos | Young | delete | 2025-08-18T07:11:00Z | 2025-08-18T08:00:00Z |
The following table illustrates how different scenarios are handled within Incremental Sync:
Change Type | Behavior |
---|---|
Column added | A snapshot is triggered automatically to populate historical data with the new column. All records will have |
Column removed | The column is excluded from future exports. |
Table added | A snapshot is initiated for the new table as part of historical backfilling.
All records will have |
Table removed | The table is no longer exported. |
Pipeline Failure or Delays | The next successful sync will include all data from the skipped export batches, ensuring no data is lost. If the failure takes a long time to resolve, the system automatically triggers a one-time snapshot with |
Was this article helpful?