Migrate from Wintouch CRM to Mailchimp

Wintouch Contact records map to Mailchimp contacts within a single Audience. Email address is the dedupe key. Standard contact fields (First Name, Last Name, Email, Phone, Address) map directly. We preserve the original Wintouch contact ID in a merge field wintouch_id__c for audit and reconciliation. All contacts migrate with their current email subscription status from Wintouch; unsubscribed or bounced addresses are flagged and held in a suppression list rather than imported. International addresses are normalized to Mailchimp's address merge field format (ADDRESS, CITY, STATE, ZIP, COUNTRY). The migration uses Mailchimp's batch import endpoint with exponential backoff and status polling to handle rate limits.

Wintouch Account records have no direct Mailchimp equivalent. We map each Wintouch Account to a Mailchimp tag named with the account name (e.g., tag: Account: Acme Corp) and apply it to all contacts linked to that account via the Wintouch Contact-to-Account relationship. For contacts with multiple account associations, we apply tags for each. The customer's admin decides during scoping whether to use tags, merge fields (ORGANIZATION), or both for account affiliation.

Wintouch Leads that have not been converted to Contacts map to Mailchimp contacts with a lead_status__c merge field carrying the original Wintouch Lead Status value and a tag Lead to differentiate unconverted records. Wintouch Lead-to-Contact conversion workflows cannot migrate; any leads already queued for conversion are documented and the customer reconverts them manually post-migration. Lead assignment rules and auto-assignment workflows are inventoried but not rebuilt.

Wintouch per-object custom fields require individual assessment. Text, numeric, date, and email custom fields map to Mailchimp merge fields of matching type. Picklist and multi-select custom fields map to Mailchimp merge fields (for single-select) or tags (for multi-select, as Mailchimp merge fields do not support multi-select). Wintouch allows up to 40 custom fields per object; Mailchimp allows up to 40 merge fields per audience, so organizations exceeding this threshold must prioritize and archive the remainder. We document every custom field with its type, values, and record coverage during discovery.

Wintouch activities (calls with disposition, emails with content, meetings with attendees, tasks with owner and due date) have no native equivalent in Mailchimp's contact record. We format each activity as a text note on the Mailchimp contact with a timestamp header: e.g., '2024-03-15 | Call | Duration: 12 min | Disposition: Interested - follow up next week'. This preserves the activity timeline on the contact record at the cost of losing structured fields. Activity owner assignment does not migrate because Mailchimp does not have a user or team assignment concept per contact note.

Wintouch notes attached to contacts migrate as Mailchimp contact notes with the original creation timestamp preserved. Notes containing file attachments extract the attachment text (where readable) and include a reference to the file stored in Mailchimp's file manager. Binary attachments (images, PDFs) are linked as URLs within the note body. Large note volumes increase migration time proportionally because each note requires formatting and API insertion.

Wintouch pipeline stages and deal records have no Mailchimp equivalent. Mailchimp does not track opportunities, deal values, or pipeline progress. We extract the full list of Wintouch pipeline stages with stage names, probabilities, and ordering and deliver this as a written inventory document for the customer's admin to use if they select a CRM replacement for pipeline management. This inventory is outside the data migration scope.

Wintouch geographic coordinates (latitude/longitude) generated from addresses are North America-only within Wintouch. International addresses may lack coordinates. We extract whatever geographic data exists in Wintouch but Mailchimp does not support latitude/longitude storage per contact. We flag any records with geographic data during scoping and recommend a post-migration geo-enrichment tool (e.g., Clearbit, Enrich) if the customer's use case requires coordinate data for segmentation.