DatriseAI-first ETL

Hubplanner to GoodData Integration

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

How Datrise loads Hubplanner into GoodData

Datrise syncs Hubplanner's bookings, resources, projects, clients, timesheets, and utilization rates into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

Hubplanner: Resource planning and utilization for agencies.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Hubplanner entities map to GoodData

Hubplanner entityGoodData objectNotes
bookingshubplanner_bookingsid PK · custom fields → flattened columns
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 GoodData?

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 GoodData types.

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

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

Related pipelines

Early access

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