Migrate from Wintouch CRM to Nutshell

Wintouch Contact records map directly to Nutshell Person objects. Standard fields (name, email, phone, address, title) map cleanly to Nutshell's Person schema. We normalize any legacy AS/400 date formatting (YYYYMMDD or packed-decimal dates) to ISO 8601 before insertion. Owner assignment (sales rep) maps to Nutshell's user_id field via email match reconciliation. Custom fields on Contact are mapped individually during discovery — each Wintouch custom field is typed (text, dropdown, date, currency) and created in Nutshell as an equivalent typed custom field before the Person import batch runs.

Wintouch Account records (B2B and B2C types) map to Nutshell Company. Wintouch supports multiple contacts and multiple addresses per Account; we flatten these into Nutshell Company primary address fields and link additional address records via Nutshell's activity log. Account type (B2B vs B2C) is preserved in a custom field. For Accounts with no associated Contacts, we create Company records with a flag for follow-up linking after the Contact import phase completes.

Wintouch custom fields proliferate per object (Contacts, Accounts, Activities, Leads). During discovery, we audit the full custom field inventory, identify field types (free text, dropdown, date, currency, numeric), and create equivalent typed custom fields in Nutshell before any data import begins. Dropdown fields in Wintouch with enumerated values become Nutshell Dropdown fields with the same option list. Fields with no corresponding Nutshell destination object are archived in a migration data dictionary rather than silently dropped.

Wintouch Lead records map to Nutshell Lead objects. Lead-to-contact conversion logic in Wintouch is application-layer workflow and is not exportable as data; we preserve the Wintouch lead_status and lead_source values as custom fields on the Nutshell Lead record for audit and reporting continuity. Any auto-assignment workflows in Wintouch are documented in the automation inventory delivered to the customer for rebuild in Nutshell.

Wintouch Deal records map to Nutshell Deal objects. Pipeline stages are customizable per Wintouch organization; we map each Wintouch stage name and ordering explicitly to Nutshell Deal stages during configuration. Historical deal stage history is preserved as a date-stamped custom field or activity note. We configure Nutshell Deal stages and any custom Deal fields before migration begins so that the stage mapping is resolved at insert time.

Wintouch Activity records (completed tasks, scheduled work, meeting logs) map to Nutshell Activity records. Activity date formats and user assignment (owner) are normalized during the transform phase. Completed vs. open activity filtering is agreed upon with the customer before migration. Any additional fields added to the Activity screen in newer Wintouch versions are treated as custom fields and mapped via the custom field configuration step.

Wintouch Task records map to Nutshell Task objects. Task assignment is resolved by matching the Wintouch owner email to a Nutshell user record. Completed vs. open task filtering is applied based on the agreed migration scope (typically open tasks and tasks from the past 12-24 months). Task subject, due date, and status migrate directly.

File attachments stored within Wintouch are not covered by a documented bulk export endpoint. We extract available attachments via accessible file paths in the Wintouch environment and map them to the corresponding Nutshell Person, Company, or Deal record as linked file attachments or activity notes. Attachments that cannot be resolved to a destination record are archived with a file manifest and record ID mapping so the customer can manually relink them post-migration.