DatriseAI-first ETL

Metabase to Snowflake Integration

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

How Datrise loads Metabase into Snowflake

Datrise syncs Metabase's questions, dashboards, collections, cards, users, and query executions into Snowflake as a typed table per source entity. Flexible or custom fields land in VARIANT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP_TZ.

Sync is incremental: Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size, so re-runs update only what changed. Automatic micro-partitioning, with optional clustering keys on high-cardinality ids. Snowflake upper-cases unquoted identifiers, so Datrise standardizes on lower-case quoted names to keep column references stable.

Ideal for central analytics warehouses feeding BI and AI workloads.

Endpoints

Metabase: Self-service BI over existing databases.

Snowflake: Cloud data warehouse with separated compute and storage.

How Metabase entities map to Snowflake

Metabase entitySnowflake objectNotes
questionsmetabase_questionsid PK · custom fields → VARIANT 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 Snowflake?

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

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

It runs incrementally — Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size.

Related pipelines

Early access

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