Nutshell → Domo
AI-first ETL from Nutshell into Domo. Governed entities, incremental sync, typed landing tables.
How Datrise loads Nutshell into Domo
Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.
Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.
Ideal for all-in-one cloud BI with built-in ETL.
Endpoints
Nutshell: Sales CRM for teams that need simple reporting and pipeline velocity.
Domo: Cloud BI platform combining data integration and executive dashboards.
How Nutshell entities map to Domo
| Nutshell entity | Domo object | Notes |
|---|---|---|
| pipeline records | nutshell_pipeline_records | id PK · custom fields → flattened columns for Magic ETL |
| activity history | nutshell_activity_history | date/time columns 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 Domo?
Flexible values are stored as flattened columns for Magic ETL, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Domo types.
How does the Nutshell to Domo sync stay up to date?
It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.
Related pipelines
More destinations for Nutshell
Early access
Connect Nutshell to Domo 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.