Migrate from Variable Soft CRM to Mailchimp

VSCRM Contact records map to Mailchimp audience members. The contact's email address is the Mailchimp subscriber hash key for deduplication. First name, last name, phone, and lifecycle stage migrate as standard Mailchimp merge fields (FNAME, LNAME, PHONE, LIFEycle). We validate email format and suppress invalid addresses before import to protect deliverability metrics.

VSCRM Lead records map to Mailchimp audience members. Mailchimp has no Lead object, so unqualified prospects migrate as standard audience members. We flag any Lead records with status values that indicate disqualified or spam sources so they can be suppressed at import rather than added to the active audience.

VSCRM Company records do not have a direct Mailchimp equivalent. We map the company name to the COMPANY merge field on each associated Contact's audience member record. If the customer uses company as a segmentation signal, we create a Tag per unique company name and apply it to all members from that company. Company-level custom fields (industry, size, region) cannot migrate to Mailchimp because Mailchimp lacks a custom fields API beyond standard merge fields.

VSCRM Deals carry value, stage, owner, expected close date, and pipeline. Mailchimp has no deal or opportunity object. We document the active deal count, total pipeline value, and stage distribution in a written deal inventory delivered alongside migration. If the customer wants deal context preserved on the contact record, we apply a Tag matching the deal name and stage to the associated Contact's audience member record, but this is informational only and not a functional CRM link.

VSCRM Pipelines (custom stage sequences per line of business) have no Mailchimp equivalent. Mailchimp's segmentation is tag-based and campaign-based, not pipeline-based. We document the pipeline names and stage labels in the automation inventory so the customer's admin can decide whether to represent pipeline context as tags or to retire the pipeline concept entirely in favor of Mailchimp's audience journey model.

VSCRM Activity records (call logs, email content, meeting records, task completions) are linked to Contacts and Deals. Mailchimp does not store activity history for individual contacts beyond campaign-level engagement metrics (opens, clicks, unsubscribes) which are generated by Mailchimp sends, not imported. We cannot migrate VSCRM activity content. Campaign engagement history generated inside Mailchimp post-migration is tracked natively.

VSCRM custom fields on Contacts and Companies are discovered from the customer's export file. Mailchimp supports text, number, date, phone, address, and birthday merge field types, each capped at 255 characters. Long-text custom fields in VSCRM are truncated or dropped. We map each VSCRM custom field to the nearest Mailchimp merge field type during the transform pass and flag any truncation above 200 characters as a data-loss risk for customer review before import.

VSCRM Workflow rules are server-side and non-exportable. We do not migrate automations. We document every active VSCRM workflow rule (trigger, conditions, actions) during discovery and deliver a written rebuild checklist so the customer's admin can reconstruct equivalent logic in Mailchimp Customer Journeys if they hold the required plan tier. Mailchimp Customer Journeys are available on Essentials and above; the free Standard plan does not include journey automation.