DatriseAI-first ETL

HighLevel DuckDB

AI-first ETL from HighLevel into DuckDB. Governed entities, incremental sync, typed landing tables.

How Datrise loads HighLevel into DuckDB

Datrise syncs HighLevel's agency CRM records, funnels, opportunities, and messaging workflows 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

HighLevel: Agency-focused CRM for leads, funnels, and customer messaging.

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

How HighLevel entities map to DuckDB

HighLevel entityDuckDB objectNotes
agency CRM recordshighlevel_agency_crm_recordsid PK · custom fields → JSON or STRUCT columns
funnelshighlevel_funnelsid PK · linked to highlevel_agency_crm_records
opportunitieshighlevel_opportunitiesid PK · linked to highlevel_agency_crm_records
messaging workflowshighlevel_messaging_workflowsid PK · linked to highlevel_agency_crm_records

FAQ

How does Datrise handle HighLevel'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 HighLevel 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 HighLevel 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.