My Hours to Birst Integration
AI-first ETL from My Hours into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads My Hours into Birst
Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.
Ideal for networked, governed enterprise BI.
Endpoints
My Hours: Time tracking and billable hours for projects.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How My Hours entities map to Birst
| My Hours entity | Birst object | Notes |
|---|---|---|
| time logs | my_hours_time_logs | id PK · custom fields → flattened columns |
| projects | my_hours_projects | id PK · linked to my_hours_time_logs |
| tasks | my_hours_tasks | id PK · linked to my_hours_time_logs |
| clients | my_hours_clients | id PK · linked to my_hours_time_logs |
FAQ
How does Datrise handle My Hours's custom fields in Birst?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Birst types.
How does the My Hours to Birst sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.
Related pipelines
More destinations for My Hours
Early access
Connect My Hours to Birst 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.