DatriseAI-first ETL

Delighted Holistics

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

How Datrise loads Delighted into Holistics

Datrise syncs Delighted's surveys, responses, scores, and follow-up workflows 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

Delighted: NPS and micro-survey feedback platform.

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

How Delighted entities map to Holistics

Delighted entityHolistics objectNotes
surveysdelighted_surveysid PK · custom fields → flattened columns for the modeling layer
responsesdelighted_responsesid PK · linked to delighted_surveys
scoresdelighted_scoresid PK · linked to delighted_surveys
follow-up workflowsdelighted_follow_up_workflowsid PK · linked to delighted_surveys

FAQ

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

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

Related pipelines

Early access

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