DatriseAI-first ETL

Merge to Holistics Integration

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

How Datrise loads Merge into Holistics

Datrise syncs Merge's linked accounts, employees, candidates, contacts, invoices, and sync statuses 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

Merge: Unified API across HR, CRM, and accounting tools.

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

How Merge entities map to Holistics

Merge entityHolistics objectNotes
linked accountsmerge_linked_accountsid PK · custom fields → flattened columns for the modeling layer
employeesmerge_employeesid PK · linked to merge_linked_accounts
candidatesmerge_candidatesid PK · linked to merge_linked_accounts
contactsmerge_contactsid PK · linked to merge_linked_accounts

FAQ

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

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

Related pipelines

Early access

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