My Hours to MySQL Integration

How Datrise loads My Hours into MySQL

Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

My Hours: Time tracking and billable hours for projects.

MySQL: Widely used OSS relational engine (InnoDB).

How My Hours entities map to MySQL

My Hours entity	MySQL object	Notes
time logs	`my_hours_time_logs`	id PK · custom fields → JSON 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 MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the My Hours to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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