DatriseAI-first ETL

MyCase to ClickHouse Integration

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

How Datrise loads MyCase into ClickHouse

Datrise syncs MyCase's cases, clients, leads, time entries, invoices, and documents 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

MyCase: Case management and client intake for law firms.

ClickHouse: Columnar OLAP engine for fast aggregations.

How MyCase entities map to ClickHouse

MyCase entityClickHouse objectNotes
casesmycase_casesid PK · custom fields → JSON or Map columns
clientsmycase_clientsid PK · linked to mycase_cases
leadsmycase_leadsid PK · linked to mycase_cases
time entriesmycase_time_entriesid PK · linked to mycase_cases

FAQ

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