Migrate from myCRMS.com to Mailchimp

myCRMS.com contacts map directly to Mailchimp audience members via email address as the primary key. We apply a pre-import deduplication check against Mailchimp's suppression list (unsubscribed, bounced, cleaned contacts) to prevent importing records that would be immediately suppressed. First name, last name, phone, address, and any standard fields map to Mailchimp's built-in merge fields (FNAME, LNAME, PHONE, ADDRESS). Custom field values map to Mailchimp merge fields created during pre-migration scope.

myCRMS.com Company records attach to contacts via a relationship field. We resolve this by either creating a COMPANY merge field on the Mailchimp audience and populating it from the related Company name, or by creating a Tag on each contact named after the Company for segmentation by account. The customer chooses the strategy during scoping based on whether they need to send to all contacts at a company at once (use Tag) or just label records (use merge field). Companies without related contacts are held in a separate inventory document.

Mailchimp has no native deal or opportunity object. Deal records from myCRMS.com are converted to Tags on the related contact record (e.g., tag Deal_ClosedWon_2025, tag Deal_Active_Pipeline) or to custom fields if the customer needs to track deal value or stage on the contact. We deliver a written inventory of all deal records with stage, amount, and close date so the customer's admin can decide whether to use tags, custom fields, or a separate CRM integration for ongoing pipeline tracking.

myCRMS.com custom fields on Contact are mapped to Mailchimp audience merge fields. Mailchimp enforces a 30-field limit on Essentials and Standard plans, 80 on Premium. During scoping we audit all custom fields, flag any that exceed the destination plan's limit, and work with the customer to prioritize the most operationally critical fields. Lower-priority fields are documented in a field inventory for future addition or for use in a connected CRM integration.

myCRMS.com Smart Lists are filtered saved views of contacts meeting specific criteria. Mailchimp's Segments serve the same purpose with different logic operators. We audit every Smart List during pre-migration scope, document the filter criteria for each, and deliver a written segment reconstruction guide showing how to replicate each Smart List as a Mailchimp Segment. The customer's admin rebuilds segments post-migration; we do not automate Mailchimp segment creation as part of the data migration scope.

myCRMS.com Owner assignments (sales rep assigned to a contact or deal) map to a Tag on the Mailchimp audience member (e.g., tag Owner_jsmith). Mailchimp does not have a native user-assignment model for contacts; tags provide a workable segmentation proxy. If the customer later connects a CRM integration (Salesforce, HubSpot) to Mailchimp, owner assignment can be managed through the integration rather than tags.

myCRMS.com Notes attached to contacts have no Mailchimp equivalent. Notes are exported as a CSV attachment inventory keyed by contact email address, with the note body and creation timestamp preserved. The customer imports this as a supplemental reference document during Mailchimp onboarding. For contacts with critical note content, we can optionally append note text to a NOTES merge field if the plan's field limit permits.

Original contact creation dates and last-modified timestamps from myCRMS.com are preserved in merge fields (created_date, last_modified) on each Mailchimp audience member. These fields support segmentation by tenure (e.g., contacts added before 2024) and audit reconciliation. We do not migrate engagement activity history (calls, emails, meetings) as Mailchimp does not store that data model; the activity timeline exists only in the source CRM.