Migrate from Nutshell to Twenty CRM

Nutshell People records map directly to Twenty CRM Contacts. Standard fields (name, email, phone, address, title) transfer as typed fields. We map People to Contact using the contact API endpoint and resolve the parent Organization lookup by matching the Nutshell Company name to an Organization created in Twenty before the Contact migration. Any People without an associated Company in Nutshell create Organization-less Contacts that the customer can manually link post-migration.

Nutshell Companies map to Twenty CRM Organizations. Company name, domain, address, and industry fields transfer directly. Organization is created first in migration order so that the Organization-Contact lookup relationship is satisfied at Contact insert time. Custom fields on Companies migrate to Organization custom fields pre-created in Twenty's schema.

Nutshell Leads are distinct records separate from People, each with their own custom fields and lifecycle status. We merge Nutshell Leads into Twenty CRM Contacts, preserving the Lead-specific custom fields as custom fields on the Contact record. The original Lead status (New, Contacted, Qualified, Disqualified) is stored in a custom field nut_legacy_lead_status__c for audit and segmentation. This merge reduces record proliferation in Twenty's single Contact model.

Nutshell Activities (calls, emails, meetings, tasks) attach to People or Companies. We migrate these as Timeline entries in Twenty, linked to the corresponding Contact or Organization by resolved ID. Call duration, disposition, and meeting attendees transfer to custom fields on the Timeline entry. Activity timestamps are preserved to maintain the historical sequence.

Nutshell Pipelines map to Twenty CRM Opportunities. Each pipeline becomes a separate Opportunity type in Twenty with its own stage configuration. We extract pipeline stage names, order, and win/loss status during discovery and recreate them in Twenty's Opportunity settings before any Opportunity data loads.

Nutshell pipeline stages (Appointment Scheduled, Presentation, Proposal, Negotiation, Closed Won, Closed Lost) map to Twenty Opportunity stages. Stage probabilities migrate as percentage fields. Stage-specific automation triggers in Nutshell are documented but not migrated—Twenty's workflow configuration is a separate rebuild task.

Nutshell custom fields for Companies, People, and Leads are enumerated during discovery. We pre-create matching custom fields in Twenty's Organization, Contact, and Opportunity objects before migration begins. Field types (text, number, date, dropdown) are mapped to Twenty's equivalent field types. Validation rules and required-field settings require manual configuration in Twenty post-migration.

Nutshell tag taxonomy transfers to Twenty CRM tags on Contact and Organization records. Tags used for People and Companies export as a list on the respective record. Tag hierarchy, if any in Nutshell, is flattened during transfer since Twenty uses a flat tag model.

Nutshell Users who own records map to Twenty CRM Users. We resolve by email match. Users in Nutshell who do not have a corresponding account in Twenty's destination instance go to a reconciliation queue for the customer to provision before record migration resumes.

Nutshell exposes attachment metadata and filenames but not binary blobs via API. We export attachment filenames, URLs, and record associations. The actual files cannot be automatically downloaded and re-uploaded. We provide a manifest of all attachment references so the customer's admin can manually re-attach files post-migration.