DatriseAI-first ETL

Chargebee ClickHouse

AI-first ETL from Chargebee into ClickHouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Chargebee into ClickHouse

Datrise syncs Chargebee's subscriptions, invoices, customers, plans, and revenue events into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

Chargebee: Subscription billing and revenue operations platform.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Chargebee entities map to ClickHouse

Chargebee entityClickHouse objectNotes
subscriptionschargebee_subscriptionsid PK · custom fields → JSON or Map columns
invoiceschargebee_invoicesid PK · linked to chargebee_subscriptions
customerschargebee_customersid PK · linked to chargebee_subscriptions
planschargebee_plansid PK · linked to chargebee_subscriptions

FAQ

How does Datrise handle Chargebee's custom fields in ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

How does the Chargebee to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect Chargebee to ClickHouse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.