DatriseAI-first ETL

Hubplanner to Metabase Integration

AI-first ETL from Hubplanner into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Hubplanner into Metabase

Datrise syncs Hubplanner's bookings, resources, projects, clients, timesheets, and utilization rates into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Hubplanner: Resource planning and utilization for agencies.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Hubplanner entities map to Metabase

Hubplanner entityMetabase objectNotes
bookingshubplanner_bookingsid PK · custom fields → flattened columns for the question builder
resourceshubplanner_resourcesid PK · linked to hubplanner_bookings
projectshubplanner_projectsid PK · linked to hubplanner_bookings
clientshubplanner_clientsid PK · linked to hubplanner_bookings

FAQ

How does Datrise handle Hubplanner's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Hubplanner to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Hubplanner to Metabase 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.