Two-way sync
Changes in Kustomer or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Keep Kustomer and Nutshell in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Companies, Custom Objects (Klasses), Users, Teams in Kustomer with Leads, People, Companies, Activities in Nutshell in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
Deal stage and value on shared accounts stay visible from either CRM.
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
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.
| Kustomer objects | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| Companies Organization records group customers and map to CRM accounts. | Companies Account records that group people and leads for account-level syncs | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Users Agent records map conversation ownership to people in other systems. | Users Rep records used to resolve ownership when syncing assignments | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tags Labels on conversations and customers sync for categorization and analytics. | Tags Segmentation labels mapped to lists or filters in downstream tools | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Notes Internal annotations carry context alongside synced conversations. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Teams Team assignments support routing parity and reporting. | Products Line items attached to leads, used to sync sold products into billing | Teams is specific to Kustomer and Products to Nutshell — each maps to any object or custom field on the other side. | |
| Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Customers is specific to Kustomer and Leads to Nutshell — 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.
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Nutshell through its API, with automatic retries and rate-limit backoff.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Kustomer through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kustomer–Nutshell connection.
Changes in Kustomer or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Kustomer or Nutshell data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Kustomer or Nutshell record.
Track your Kustomer ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Kustomer and Nutshell.
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 Kustomer and Nutshell 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 Kustomer and Nutshell 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 Kustomer and Nutshell: authenticate both systems, choose the objects to sync (such as Kustomer's Companies and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Stacksync manages authentication, retries, and rate limits on both sides.
Kustomer: API keys are issued as role-scoped bearer tokens, so integration access can be limited to the specific object types a sync touches. Nutshell: The deal object is called a Lead in Nutshell, and it links to separate People and Company records rather than replacing them. Stacksync's field mapping accounts for these differences between Kustomer and Nutshell without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Kustomer and Nutshell records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Kustomer and Nutshell connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Kustomer–Nutshell integration in-house.
Yes — Stacksync ships production-grade connectors for both Kustomer and Nutshell. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 334 integrations available for Kustomer and Nutshell.