Migrate from Touchpoint MX to Nutshell

Touchpoint MX Contacts map directly to Nutshell People records. Standard fields (name, email, phone, address) migrate 1:1. Any custom field values set on Touchpoint MX Contacts are mapped to Nutshell's custom fields on People, with field types matched (text, number, date, dropdown). We detect all active custom fields during scoping, including any Manager-only or Attendee-only fields, and map them with the most permissive visibility setting in Nutshell.

Touchpoint MX Channel assignments (Email, SMS, Voice) are stored per Contact. We create a multi-select or checkbox custom field set in Nutshell to capture which channels are active for each Person. If Nutshell's communication preference fields already exist, we map directly; otherwise we provision them during schema setup. Channel delivery metadata (opt-in date, last used channel) migrates as additional custom fields.

Touchpoint MX Journey Maps have a custom stage taxonomy unique to each organization. Nutshell does not have a native journey concept. We flatten each Journey Map into a combination of Nutshell pipeline stages (for deal-driven records) and a custom text or picklist field journey_stage__c on the Person record to preserve the original stage label. We produce a stage mapping table during scoping for customer approval before migration begins, to prevent Contacts landing with incorrect stage labels.

Touchpoint MX Satisfaction Scores (numeric ratings tied to Contacts) migrate to a custom number field on the Nutshell Person record. Score values, timestamps, and the related interaction context migrate as separate custom fields (satisfaction_score__c, satisfaction_date__c, satisfaction_context__c). If multiple satisfaction records exist per Contact, we preserve the most recent score as the primary value and flag the historical series for manual review in Nutshell.

Touchpoint MX Feedback Records (structured entries with text, date, and related Contact) migrate as Nutshell Notes attached to the corresponding Person record. The Feedback date becomes the Note date; the full Feedback text becomes the Note body. If the customer has Feedback categorized by type (complaint, NPS response, survey), we add a Note tag or custom field to preserve the category. Large volumes of Feedback Records (over 5,000) are chunked to avoid API timeout.

Touchpoint MX Message Templates (reusable outbound content with subject lines and personalization tokens) do not have a direct equivalent in Nutshell's data model. We export Template content, subject lines, and token placeholders as a structured CSV document. The customer uses this as a reference to recreate templates in Nutshell's email templates or a connected email tool (e.g., a marketing automation integration). This is not a data migration deliverable; it is a configuration reference.

Touchpoint MX User accounts are mapped by email address to Nutshell User records. We extract the full user list and map Owner assignments on Contacts, Journey Records, and Feedback to the corresponding Nutshell User. Any Touchpoint MX User without a matching Nutshell User email is flagged for the customer to provision before record import resumes.

File attachments associated with Touchpoint MX Contacts or Feedback Records are exported and re-linked to the corresponding Nutshell Person record as attachments. We flag any attachment exceeding 10 MB for chunked migration to avoid timeout. Very large attachment volumes (over 1,000 files) require a separate file migration pass after the primary data migration completes.