Close → Birst
AI-first ETL from Close into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads Close into Birst
Datrise syncs Close's leads, opportunities, calls, SMS events, and sequence performance into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.
Ideal for networked, governed enterprise BI.
Endpoints
Close: Inside-sales CRM with calling and sequences.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How Close entities map to Birst
| Close entity | Birst object | Notes |
|---|---|---|
| leads | close_leads | id PK · custom fields → flattened columns |
| opportunities | close_opportunities | id PK · linked to close_leads |
| calls | close_calls | id PK · linked to close_leads |
| SMS events | close_sms_events | date/time dimensions events |
FAQ
How does Datrise handle Close's custom fields in Birst?
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 Birst types.
How does the Close to Birst sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.
Related pipelines
More destinations for Close
Early access
Connect Close to Birst 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.