DatriseAI-first ETL

Close Databricks SQL Warehouse

AI-first ETL from Close into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Close into Databricks SQL Warehouse

Datrise syncs Close's leads, opportunities, calls, SMS events, and sequence performance into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.

Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.

Ideal for lakehouse analytics and ML feature tables on Databricks.

Endpoints

Close: Inside-sales CRM with calling and sequences.

Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.

How Close entities map to Databricks SQL Warehouse

Close entityDatabricks SQL Warehouse objectNotes
leadsclose_leadsid PK · custom fields → VARIANT or STRUCT columns
opportunitiesclose_opportunitiesid PK · linked to close_leads
callsclose_callsid PK · linked to close_leads
SMS eventsclose_sms_eventsTIMESTAMP events

FAQ

How does Datrise handle Close's custom fields in Databricks SQL Warehouse?

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

How does the Close to Databricks SQL Warehouse sync stay up to date?

It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.

Related pipelines

Early access

Connect Close to Databricks SQL Warehouse 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.