DatriseAI-first ETL

Amplitude Holistics

AI-first ETL from Amplitude into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Amplitude into Holistics

Datrise syncs Amplitude's product events, user properties, funnels, cohorts, and retention curves into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Amplitude: Product analytics source for events, funnels, and cohorts.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Amplitude entities map to Holistics

Amplitude entityHolistics objectNotes
product eventsamplitude_product_eventsdate/time dimensions events
user propertiesamplitude_user_propertiesid PK · linked to amplitude_product_events
funnelsamplitude_funnelsid PK · linked to amplitude_product_events
cohortsamplitude_cohortsid PK · linked to amplitude_product_events

FAQ

How does Datrise handle Amplitude's custom fields in Holistics?

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

How does the Amplitude to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect Amplitude to Holistics 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.