Migrate from edge CRM to Mailchimp

edge CRM Contacts map directly to Mailchimp Contacts within a single Audience. Standard properties (first name, last name, email, phone) migrate as Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE). Custom fields on edge CRM Contacts transform to Mailchimp merge fields with a matching type where possible: text fields to text merge fields, date fields to date merge fields, and dropdowns to radio-button merge fields. The contact's subscribed or unsubscribed status in edge CRM maps to Mailchimp's Member Status. Email address case sensitivity is normalized to lowercase before import to prevent duplicate contacts (RFC 5321 compliant).

edge CRM Companies do not have a direct Mailchimp equivalent because Mailchimp is contact-centric rather than account-centric. We handle this by writing the Company name and domain into contact-level merge fields (COMPANY, COMPANY_DOMAIN) and applying a tag per company name so that contacts from the same company can be segmented in Mailchimp without a separate Account object. The Contact-Company association in edge CRM is preserved as a tag on each migrated contact. Teams requiring a full account model should connect Mailchimp to a CRM via Zapier or Mailchimp's native CRM integrations post-migration.

edge CRM Deals with pipeline stage, monetary value, expected close date, and owner do not map to any native Mailchimp object. We extract the Deal data during the audit phase and write it into contact-level merge fields (DEAL_VALUE, DEAL_STAGE, DEAL_CLOSE_DATE) or apply tags representing pipeline stages (e.g., tag: DealStage-Prospecting, DealStage-ContractSent). This preserves deal data as contact metadata rather than losing it, but deal-level reporting must be rebuilt in Mailchimp using contact segments filtered by deal-stage tags. Full deal pipeline management is not achievable in Mailchimp alone; teams should connect to a CRM via Mailchimp's native integrations or Zapier post-migration.

edge CRM Leads (distinct from Contacts, often enriched with AI-scored qualification data) migrate as Mailchimp Contacts with their lead score value stored in a merge field (LEAD_SCORE) and their lead status stored as a tag (LeadStatus-Open, LeadStatus-Qualified). Mailchimp does not have a separate Lead object, so unqualified prospects are mixed with existing customers in the same audience. Teams requiring a strict pre-contact pipeline should add a CRM alongside Mailchimp post-migration.

edge CRM Activities (calls, emails, meetings, notes with timestamps and free-text body) do not have a native Mailchimp equivalent. We extract the most recent and highest-value notes (last five per contact or any note marked as important by the sales rep) and write them as Mailchimp Contact Notes. Individual call logs, meeting timestamps, and email engagement history at the contact level do not transfer. We flag this as a data loss item during scoping and recommend that teams capture critical activity context as contact notes before migration.

edge CRM Tasks (follow-up items assigned to users with due dates and completion status) migrate partially as Mailchimp Contact Notes, preserving the task description and due date. Completed versus open status is noted within the note text. Overdue status is not a Mailchimp flag and is embedded in the note body. Task assignment to specific users does not transfer because Mailchimp is a shared audience rather than a user-assigned task system. We flag this as a gap and recommend a task management tool (Trello, Asana, or a connected CRM) for post-migration follow-up tracking.

edge CRM custom pipeline stages with names and ordering do not have a Mailchimp equivalent. We extract the full stage list during scoping and create Mailchimp tags in the format Pipeline-{StageName} applied to contacts based on their current deal stage. Stage probability and ordering are not transferable. We recommend using Mailchimp audience segments filtered by pipeline-stage tags for basic pipeline reporting, and connecting to a full CRM for stage-based pipeline management.

edge CRM custom properties on Contacts, Companies, Deals, and Leads migrate to Mailchimp merge fields. We extract the full custom field schema during the audit phase, map each field type to the closest Mailchimp merge field type (text, number, date, or dropdown), and flag any fields that cannot be represented in Mailchimp's schema (e.g., multi-select arrays map to comma-separated text fields). The maximum merge field count per Mailchimp audience is 40, which we check against the customer's total custom field count and flag any overflow during scoping.