DatriseAI-first ETL

Metabase to Yellowfin Integration

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

How Datrise loads Metabase into Yellowfin

Datrise syncs Metabase's questions, dashboards, collections, cards, users, and query executions into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Metabase: Self-service BI over existing databases.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Metabase entities map to Yellowfin

Metabase entityYellowfin objectNotes
questionsmetabase_questionsid PK · custom fields → flattened columns
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 Yellowfin?

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

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

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

Related pipelines

Early access

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