DatriseAI-first ETL

Metabase to Holistics Integration

AI-first ETL from Metabase into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Metabase into Holistics

Datrise syncs Metabase's questions, dashboards, collections, cards, users, and query executions into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Metabase: Self-service BI over existing databases.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Metabase entities map to Holistics

Metabase entityHolistics objectNotes
questionsmetabase_questionsid PK · custom fields → flattened columns for the modeling layer
dashboardsmetabase_dashboardsid PK · linked to metabase_questions
collectionsmetabase_collectionsid PK · linked to metabase_questions
cardsmetabase_cardsid PK · linked to metabase_questions

FAQ

How does Datrise handle Metabase's custom fields in Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the Metabase to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect Metabase to Holistics 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.