Migrate from Touchdown to Nutshell

Touchdown Contacts map to Nutshell Leads if the contact is marketing-sourced or unqualified, and to Nutshell Contacts tied to an Account if the contact has a company association and sales activity. We determine the split using Touchdown's segment membership flags and lifecycle stage properties discovered during API exploration. The original Touchdown contact score and segment tags preserve in Nutshell custom fields on the corresponding object.

Touchdown Company records map to Nutshell Account. We resolve the Company-to-Account mapping during import by matching on domain name, which becomes the Account's website field and the dedupe key. Account is created before any Contact import so the lookup relationship is satisfied at Contact insert time. Touchdown's company-level custom properties map to Account custom fields in Nutshell's customFields structure.

Touchdown Deals map to Nutshell Tasks or Opportunity records depending on Nutshell tier and configuration. On Nutshell Starter and Pro, Deals map to Tasks attached to the relevant Account or Contact. On Nutshell Pro+ and Enterprise with the Sales Automation suite enabled, Deals map to Nutshell Opportunity records with stage, amount, and close date preserved. We configure the appropriate mapping during scoping based on the destination Nutshell plan.

Touchdown pipeline stages map to Nutshell Task status values or Opportunity stage values depending on the Deal-to-Object mapping chosen during scoping. Each stage probability percentage transfers to the corresponding Nutshell stage definition.

Touchdown campaign metadata (name, description, audience segment, start date, end date) transfers to a Nutshell Campaign record. Campaign logic, automation triggers, and personalization tokens do not migrate as structured code. We deliver a written inventory of every Touchdown campaign with its audience criteria, associated email templates, and recommended Nutshell equivalent (manual campaign rebuild or Nutshell Engagement suite configuration) for the customer's admin.

Touchdown audience segments map to Nutshell List records with member contacts enumerated. Segment filter logic (the criteria that define membership) does not migrate as an automated rule. We deliver a written inventory of every Touchdown segment with its filter definition and member count, so the customer's admin can rebuild segments as static Lists or dynamic filters in Nutshell.

Touchdown email template content and merge field names export as a written inventory with HTML source and token references. We do not import templates as live Nutshell Email Template records because template format compatibility between marketing automation CRMs and sales CRMs requires manual reformatting of merge token syntax. The customer's admin rebuilds templates in Nutshell using the exported content.

Touchdown engagement history (email opens, clicks, sends, call records, meeting logs) maps to Nutshell Activity records attached to the corresponding Lead, Contact, or Account. Activity timestamps and disposition values preserve. The Nutshell JSON-RPC API requires a valid rev value on every edit; we retrieve and pass the current rev before each activity insert to prevent conflicts.

Touchdown custom field schema is discovered via API exploration since it is not publicly documented. Each custom field maps to a named entry in Nutshell's customFields dictionary on the appropriate entity (Lead, Account, or Contact). Currency custom fields in Touchdown map to Nutshell's currency object format {currency: "USD", amount: "value"}. Text, date, and numeric custom fields map directly. We flag any Touchdown field type that has no equivalent Nutshell representation during scoping.

Touchdown Owner records map to Nutshell User accounts. We resolve owners by email match. Any Touchdown Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Touchdown owners map to inactive Nutshell users to preserve historical assignment.