DatriseAI-first ETL

Totango Metabase

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

How Datrise loads Totango into Metabase

Datrise syncs Totango's contacts, accounts, deals, activities, and lifecycle events 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

Totango: Customer success platform for health scores, playbooks, and renewals.

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

How Totango entities map to Metabase

Totango entityMetabase objectNotes
contactstotango_contactsid PK · custom fields → flattened columns for the question builder
accountstotango_accountsid PK · linked to totango_contacts
dealstotango_dealsid PK · linked to totango_contacts
activitiestotango_activitiestemporal columns for trends events

FAQ

How does Datrise handle Totango'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 Totango to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Totango 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.