Nutshell → Birst
AI-first ETL from Nutshell into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads Nutshell into Birst
Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics 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
Nutshell: Sales CRM for teams that need simple reporting and pipeline velocity.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How Nutshell entities map to Birst
| Nutshell entity | Birst object | Notes |
|---|---|---|
| pipeline records | nutshell_pipeline_records | id PK · custom fields → flattened columns |
| activity history | nutshell_activity_history | date/time dimensions events |
| conversion-focused sales metrics | nutshell_conversion_focused_sales_metrics | id PK · linked to nutshell_pipeline_records |
FAQ
How does Datrise handle Nutshell'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 Nutshell 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 Nutshell
Early access
Connect Nutshell 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.