Gainsight to ClickHouse Integration

How Datrise loads Gainsight into ClickHouse

Datrise syncs Gainsight's customers, health scores, playbooks, tasks, surveys, and usage metrics 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

Gainsight: Customer success health scoring and playbooks.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Gainsight entities map to ClickHouse

Gainsight entity	ClickHouse object	Notes
customers	`gainsight_customers`	id PK · custom fields → JSON or Map columns
health scores	`gainsight_health_scores`	id PK · linked to gainsight_customers
playbooks	`gainsight_playbooks`	id PK · linked to gainsight_customers
tasks	`gainsight_tasks`	id PK · linked to gainsight_customers

FAQ

How does Datrise handle Gainsight'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 Gainsight 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 Gainsight 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.