Two-way sync
Changes in Nutshell or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Nutshell and Starburst Enterprise in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Activities, Tasks, Notes, Products from Nutshell land in Starburst Enterprise as live tables, updated within seconds, and columns computed in Starburst Enterprise write back to fields in Nutshell. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Deduplication and normalization done in Starburst Enterprise can be written back, so warehouse-side cleanup actually fixes the CRM.
Accounts, contacts, and activity from Nutshell are queryable in Starburst Enterprise moments after they change, so dashboards stop lagging the reality they describe.
Lead scores, churn risk, or usage segments computed in Starburst Enterprise appear as fields in Nutshell, where the people working accounts actually see them.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Nutshell objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| People Individual contacts, kept consistent with marketing and outreach tools | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | People is specific to Nutshell and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Companies Account records that group people and leads for account-level syncs | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Companies is specific to Nutshell and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Activities Logged calls, meetings, and emails used for engagement reporting | Tables Queryable relations; writes pass through to sources whose connectors support them. | Activities is specific to Nutshell and Tables to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Tasks Rep to-dos mirrored into external work-management or reporting systems | Views Engine-level SQL views used to shape federated data before syncing it out. | Tasks is specific to Nutshell and Views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Notes Free-text history attached to leads and contacts, replicated for a full timeline | Materialized views Precomputed results that make repeated sync reads cheaper. | Notes is specific to Nutshell and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Products Line items attached to leads, used to sync sold products into billing | Columns Typed per the Trino type system, mapped from each source's native types. | Products is specific to Nutshell and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is written to Nutshell through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Starburst Enterprise connection.
Changes in Nutshell or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Nutshell or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Nutshell or Starburst Enterprise record.
Track your Nutshell ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Nutshell and Starburst Enterprise.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Nutshell and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Nutshell and Starburst Enterprise objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Nutshell's People and Companies), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Nutshell: Webhook subscriptions for record events, with polling as fallback. On Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Nutshell side: Activities, Tasks, Notes, Products, plus custom fields where Nutshell exposes them. On the Starburst Enterprise side: Schemas, Tables, Views, Materialized views. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Nutshell and Starburst Enterprise: Cleanup that sticks; CRM analytics on live data; Scores and segments back on the record. Deduplication and normalization done in Starburst Enterprise can be written back, so warehouse-side cleanup actually fixes the CRM.
Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 352 integrations available for Nutshell and Starburst Enterprise.