Migrate from Variable Soft CRM to Nutshell

VSCRM Lead records map to Nutshell Person records. The source, status, and owner assignment from VSCRM migrate as Person fields and a custom owner lookup. VSCRM does not publish a field schema, so we discover field names from the customer's export file during the discovery pass and map each to a Nutshell Person attribute or custom field. Any Person records with the same email address merge under Nutshell's deduplication logic.

VSCRM Contact records map to Nutshell Person records. The primary company association from VSCRM links to the corresponding Nutshell Company record via the person_company_link relationship. Lifecycle stage or contact status from VSCRM maps to a custom Person field since Nutshell does not have a native lifecycle stage property. Duplicate contacts identified during the extraction pass are flagged for the customer's review before import.

VSCRM Company records map to Nutshell Company records. The company name, domain, address, phone, and industry fields migrate directly where present in the export. VSCRM companies act as parent containers for associated Contacts and Deals, so we create the Company record first during each import phase to satisfy the lookup dependency before importing linked Contacts and Deals.

VSCRM Deal records map to Nutshell Deal records. Deal value, expected close date, owner, and pipeline stage from VSCRM migrate to the equivalent Nutshell Deal fields. The VSCRM pipeline name maps to a Nutshell Pipeline, and the VSCRM stage label maps to a Nutshell Stage within that pipeline. We recreate the stage sequence from VSCRM in Nutshell before Deal import begins, including empty stages that act as pipeline containers.

VSCRM's multiple named pipelines with custom stages map to Nutshell Pipelines, each containing Nutshell Stages in the same sequence order. Stage names and relative position transfer; probability percentages transfer as a custom field if the customer uses them for forecasting. Stages with no associated Deals are recreated as empty containers so the pipeline structure is complete in Nutshell.

VSCRM activity records (calls, emails, tasks) map to Nutshell Task records. The activity type, timestamp, linked entity (Contact, Deal), and content or notes migrate as a Task with the appropriate TaskType and linked Person or Deal. VSCRM activity content and notes require a separate extraction pass from the primary data export; if the export consolidates activity data into a single column or related table, we split it during the transform phase.

VSCRM supports custom fields on Contacts, Companies, and Deals, but the custom field list is not available via public API. We discover custom field names and data types from the customer's export file during the discovery pass, then pre-create the corresponding custom fields in Nutshell before importing any records. Custom field values transfer as typed Nutshell custom fields (text, number, date, dropdown) based on the discovered data format in the export.

VSCRM workflow automations are stored server-side with no export mechanism. Email triggers, field-update rules, and assignment automations configured in VSCRM do not carry over during migration. We document every active automation during the discovery call, capturing the trigger conditions, actions, and affected record types, and deliver a rebuild checklist for the customer's Nutshell admin to reconstruct the logic using Nutshell's automation tools. This is a manual reconstruction scope outside the data migration.