DatriseAI-first ETL

Metabase to ThoughtSpot Integration

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

How Datrise loads Metabase into ThoughtSpot

Datrise syncs Metabase's questions, dashboards, collections, cards, users, and query executions into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

Metabase: Self-service BI over existing databases.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How Metabase entities map to ThoughtSpot

Metabase entityThoughtSpot objectNotes
questionsmetabase_questionsid PK · custom fields → flattened columns for searchable fields
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 ThoughtSpot?

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

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

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

Related pipelines

Early access

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