DatriseAI-first ETL

Metabase to Metabase Integration

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

How Datrise loads Metabase into Metabase

Datrise syncs Metabase's questions, dashboards, collections, cards, users, and query executions into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Metabase: Self-service BI over existing databases.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Metabase entities map to Metabase

Metabase entityMetabase objectNotes
questionsmetabase_questionsid PK · custom fields → flattened columns for the question builder
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 Metabase?

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

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

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

Related pipelines

Early access

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