Migrate from InTouch to Nutshell

InTouch contacts with confirmed company relationships map directly to Nutshell People. The primary company association becomes the Nutshell Company lookup; any secondary InTouch companies surface as account-contact relationship records in Nutshell for reference. These secondary links are stored as account-contact relationship records, giving you visibility into all associated companies on each contact in Nutshell.

InTouch contacts that have no associated company or carry a lifecycle_stage of 'Subscriber' or 'Lead' route to Nutshell Leads. Your team decides whether to import all contacts as People or use the Lead/Person split based on your Nutshell plan configuration.

InTouch companies map 1:1 to Nutshell Company records. Company hierarchies (parent/child) are preserved using Nutshell's parent-company field. Multi-company contacts collapse to one primary CompanyId plus secondary relationship records. During migration, the parent-company link is set for each Nutshell Company record, preserving the original hierarchy. Secondary contact associations are linked via account-contact records, allowing a full view of related accounts.

InTouch deals map to Nutshell Deals with pipeline and stage mapping. Each InTouch deal pipeline becomes a Nutshell pipeline view. Deal-stage values are mapped value-by-value to the corresponding Nutshell pipeline stages. All deal custom fields are transferred as Nutshell Deal custom fields, preserving any specific pipeline-specific logic.

Nutshell has no native lifecycle-stage field. InTouch's lifecycle_stage property (Subscriber, Lead, MQL, SQL, Customer, Evangelist) migrates as a custom pick-list field on both Person and Lead records. Stage-transition history is preserved as a custom audit text field. After migration, you can use this custom field to segment reports, trigger automations, or guide sales reps through the buyer journey.

InTouch engagement scoring or contact rating values migrate as a custom number field on Person/Lead. Nutshell does not have a native scoring mechanism — this field is preserved for reporting continuity and can be used to drive manual prioritization. You can build views or reports that sort contacts by this score, helping reps focus on high-value prospects.

InTouch activity records (calls, emails, meetings, notes) map to Nutshell Activities with original timestamps and owner assignments preserved. The activity type maps to Nutshell's activity kind field (Call, Email, Meeting, Note). Any attachments or inline images associated with activities are preserved as file links in Nutshell, maintaining a complete record of interactions.

InTouch custom contact properties become Nutshell custom fields on the Person and Lead tabs. Field type is inferred from InTouch's data type (text, number, date, pick-list) and recreated accordingly. Required-field enforcement is disabled during import, then re-enabled post-migration. After import, you can adjust field settings, set default values, or add validation rules to match your workflow requirements.

InTouch custom company fields map to Nutshell Company custom fields. Field types are preserved. Multi-select pick-list values are flattened to comma-separated strings or mapped to Nutshell's multi-value custom field if the Nutshell plan supports it. You can review the mapped fields after migration to ensure pick-list values align with your reporting categories.

InTouch custom deal properties migrate to Nutshell Deal custom fields. Custom fields scoped to specific InTouch pipelines map to the corresponding Nutshell pipeline. Deal-level custom fields are not scoped by pipeline in Nutshell, so all deals inherit the same field definitions.

InTouch file attachments on contacts, companies, or deals are downloaded and re-uploaded as Nutshell file attachments linked to the corresponding record. File size limits apply (Nutshell supports standard cloud storage limits). Inline images in notes are handled separately. If any files exceed Nutshell's size cap, they are flagged for manual upload, ensuring no data is lost during the migration.

InTouch owner IDs are resolved by email match against Nutshell Users. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts first or assigns records to a fallback owner. No record lands without a valid Nutshell user or default owner assignment.