DatriseAI-first ETL

My Hours to Holistics Integration

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

How Datrise loads My Hours into Holistics

Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates 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

My Hours: Time tracking and billable hours for projects.

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

How My Hours entities map to Holistics

My Hours entityHolistics objectNotes
time logsmy_hours_time_logsid PK · custom fields → flattened columns for the modeling layer
projectsmy_hours_projectsid PK · linked to my_hours_time_logs
tasksmy_hours_tasksid PK · linked to my_hours_time_logs
clientsmy_hours_clientsid PK · linked to my_hours_time_logs

FAQ

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

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

Related pipelines

Early access

Connect My Hours 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.