DatriseAI-first ETL

Close Snowflake

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

How Datrise loads Close into Snowflake

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

Sync is incremental: Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size, so re-runs update only what changed. Automatic micro-partitioning, with optional clustering keys on high-cardinality ids. Snowflake upper-cases unquoted identifiers, so Datrise standardizes on lower-case quoted names to keep column references stable.

Ideal for central analytics warehouses feeding BI and AI workloads.

Endpoints

Close: Inside-sales CRM with calling and sequences.

Snowflake: Cloud data warehouse with separated compute and storage.

How Close entities map to Snowflake

Close entitySnowflake objectNotes
leadsclose_leadsid PK · custom fields → VARIANT columns
opportunitiesclose_opportunitiesid PK · linked to close_leads
callsclose_callsid PK · linked to close_leads
SMS eventsclose_sms_eventsTIMESTAMP_TZ events

FAQ

How does Datrise handle Close's custom fields in Snowflake?

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

How does the Close to Snowflake sync stay up to date?

It runs incrementally — Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size.

Related pipelines

Early access

Connect Close to Snowflake 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.