Deputy → Holistics
AI-first ETL from Deputy into Holistics. Governed entities, incremental sync, typed landing tables.
How Datrise loads Deputy into Holistics
Datrise syncs Deputy's records, events, and configuration objects 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
Deputy: SaaS or API data source for analytics and warehouse sync.
Holistics: Self-service BI with modeling layers and scheduled report delivery.
How Deputy entities map to Holistics
| Deputy entity | Holistics object | Notes |
|---|---|---|
| records | deputy_records | id PK · custom fields → flattened columns for the modeling layer |
| events | deputy_events | date/time dimensions events |
| configuration objects | deputy_configuration_objects | id PK · linked to deputy_records |
FAQ
How does Datrise handle Deputy'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 Deputy to Holistics sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the modeled tables.
Related pipelines
More destinations for Deputy
Early access
Connect Deputy 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.