DatriseAI-first ETL

Totango Snowflake

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

How Datrise loads Totango into Snowflake

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

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

Snowflake: Cloud data warehouse with separated compute and storage.

How Totango entities map to Snowflake

Totango entitySnowflake objectNotes
contactstotango_contactsid PK · custom fields → VARIANT columns
accountstotango_accountsid PK · linked to totango_contacts
dealstotango_dealsid PK · linked to totango_contacts
activitiestotango_activitiesTIMESTAMP_TZ events

FAQ

How does Datrise handle Totango'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 Totango 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 Totango 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.