Migrate from eZnet CRM to Mailchimp

eZnet CRM Contacts with name, email, phone, and address fields map to Mailchimp Contact records within an Audience. Email address is the primary dedupe key and must be valid, non-suppressed format before import. We validate and normalize email addresses during the transform phase, flagging hard bounces and invalid formats for customer review before insert. Contact-Account association is preserved as a merge tag (ACCOUNTNAME) if the customer wants to retain company context in Mailchimp, since Mailchimp does not have a native relational Account model.

eZnet CRM Account names map to a custom Mailchimp merge tag (typically named ACCOUNTNAME) attached to each Contact record. Mailchimp merge tags support a maximum of 40 characters and alphanumeric characters plus underscores only. Long account names are truncated at import. Accounts are not standalone records in Mailchimp; the company context is flattened into the Contact. If the customer requires account-level segmentation, we recommend creating Mailchimp Groups per account name rather than relying on merge tags for grouping logic.

eZnet CRM Leads have a lifecycle distinct from Contacts. We map Lead status and lead source to Mailchimp Groups (for mutually exclusive categories like LeadStatus or LeadSource) and Tags (for non-exclusive labels like campaign来源 or industry type). The customer chooses the segmentation strategy during scoping: Groups are better for mutually exclusive buckets; Tags allow a Contact to carry multiple non-hierarchical labels simultaneously. We do not create a separate Audience for Leads since Mailchimp best practice is a unified audience with segment filters rather than separate lists per record type.

eZnet CRM Marketing Campaign records (campaign name, type, status, start/end dates, budget) map to Mailchimp Campaign records. Campaign member associations linking eZnet CRM Contacts to campaigns migrate as a Mailchimp Group named after the campaign. We import campaign metadata and create the campaign record, but campaign content (email templates, subject lines, body copy) does not migrate because it is not stored as structured data in eZnet CRM; we deliver a campaign rebuild guide listing the campaign name, dates, and target segment for manual reconstruction in Mailchimp's campaign builder.

eZnet CRM custom fields on Contacts (text, date, number, picklist) map to Mailchimp merge tags. We capture the full field schema including data type, picklist values, and visibility during discovery, then pre-create merge tags in the Mailchimp Audience before import. Mailchimp imposes a maximum of 40 merge tags per Audience and each tag name must start with a letter and contain only letters, numbers, and underscores. Field names exceeding 40 characters or containing special characters are renamed per Mailchimp conventions. Multi-select picklist values split across multiple single-value merge tags since Mailchimp does not support multi-select field types natively.

eZnet CRM Opportunities represent deal records with pipeline stages, amounts, and close dates. Mailchimp has no opportunity or pipeline object; it is an email marketing platform, not a sales CRM. Opportunities do not migrate. We flag each Opportunity with its stage, amount, close date, and owner in a written exclusions document so the customer's admin can evaluate whether to recreate a simple tracking mechanism in a separate system (a spreadsheet, a project tool, or a lightweight CRM) or accept that this data will not live in Mailchimp.

eZnet CRM Activities (calls, emails, meetings, tasks) attached to Contacts do not have a Mailchimp equivalent. Mailchimp tracks opens, clicks, and unsubscribes as engagement signals but not the full CRM activity timeline. We do not migrate Activity records. Email association metadata (which Contact an email is linked to) is not structurally importable into Mailchimp beyond the contact record itself. We note this limitation in the scope document and recommend that teams needing activity history retain it in eZnet CRM or a note-taking system during the transition window.

eZnet CRM Users referenced as record owners are mapped to Mailchimp Tags (e.g., OwnerEmail) on each Contact record. This preserves a loose reference to the original owner without creating Mailchimp User accounts. Mailchimp User management is separate from Contact management; users are account administrators and authors, not linked to individual Contact records. If the customer needs owner-level access controls within Mailchimp (e.g., restricting campaigns to specific team members), we document this as a Mailchimp admin configuration item rather than a data migration item.