Nutshell → Metabase
AI-first ETL from Nutshell into Metabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Nutshell into Metabase
Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.
Ideal for self-serve questions and dashboards for whole teams.
Endpoints
Nutshell: Sales CRM for teams that need simple reporting and pipeline velocity.
Metabase: Open-source analytics with questions, dashboards, and embedded insights.
How Nutshell entities map to Metabase
| Nutshell entity | Metabase object | Notes |
|---|---|---|
| pipeline records | nutshell_pipeline_records | id PK · custom fields → flattened columns for the question builder |
| activity history | nutshell_activity_history | temporal columns for trends 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 Metabase?
Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.
How does the Nutshell to Metabase sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Nutshell
Early access
Connect Nutshell to Metabase 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.