HubSpot Service Hub to DuckDB Integration

How Datrise loads HubSpot Service Hub into DuckDB

Datrise syncs HubSpot Service Hub's tickets, contacts, companies, conversations, knowledge base articles, and feedback submissions into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

HubSpot Service Hub: Ticketing and knowledge base on the HubSpot CRM record.

DuckDB: In-process analytics database for fast local OLAP.

How HubSpot Service Hub entities map to DuckDB

HubSpot Service Hub entity	DuckDB object	Notes
tickets	`hubspot_service_tickets`	id PK · custom fields → JSON or STRUCT columns
contacts	`hubspot_service_contacts`	id PK · linked to hubspot_service_tickets
companies	`hubspot_service_companies`	id PK · linked to hubspot_service_tickets
conversations	`hubspot_service_conversations`	id PK · linked to hubspot_service_tickets

FAQ

How does Datrise handle HubSpot Service Hub's custom fields in DuckDB?

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

How does the HubSpot Service Hub to DuckDB sync stay up to date?

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

Connect HubSpot Service Hub to DuckDB 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.