Two-way sync
Changes in Nutshell or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Keep Nutshell and Twenty CRM 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 Notes, Products, Tags, Users in Nutshell with Workspace Members, People, Companies, Opportunities in Twenty CRM 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.
| Nutshell objects | Twenty CRM objects | |
|---|---|---|
| People Individual contacts, kept consistent with marketing and outreach tools | Opportunities Deal records tracked through pipeline stages, synced for forecasting. | |
| Companies Account records that group people and leads for account-level syncs | Tasks To-dos linked to people, companies, or deals. | |
| Activities Logged calls, meetings, and emails used for engagement reporting | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | |
| Tasks Rep to-dos mirrored into external work-management or reporting systems | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | |
| Notes Free-text history attached to leads and contacts, replicated for a full timeline | Attachments Files linked to records. | |
| Products Line items attached to leads, used to sync sold products into billing | Workspace Members User accounts used for record ownership and assignment mapping. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Twenty CRM connection.
Changes in Nutshell or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Nutshell or Twenty CRM 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 Twenty CRM record.
Track your Nutshell ⇄ Twenty CRM sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Nutshell and Twenty CRM.
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 Twenty CRM 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 Twenty CRM 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 Twenty CRM: 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 Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Nutshell side: Notes, Products, Tags, Users, plus custom fields where Nutshell exposes them. On the Twenty CRM side: Workspace Members, People, Companies, Opportunities. 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 Twenty CRM: Where both track pipeline: deal visibility across systems; Post-acquisition consolidation; Migration with a parallel run. Deal stage and value on shared accounts stay visible from either CRM.
Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Twenty CRM: GraphQL and REST APIs. Authentication: API key. 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 386 integrations available for Nutshell and Twenty CRM.