Migrate from Sage CRM to Mailchimp

Sage CRM Contact records map to Mailchimp Subscribers. Email address is the unique identifier and dedupe key. First name (pers_firstname or lead_personfirstname), last name (pers_lastname or lead_personlastname), salutation, title, department, and email migrate to the corresponding Mailchimp merge fields (FNAME, LNAME, PER_SALUTA, PER_TITLE, PER_DEPART, EMAIL). We deduplicate by email using Mailchimp's upsert behavior and flag any soft bounces from prior Sage CRM sync for review before import.

Sage CRM Company data maps to Mailchimp merge fields on the Subscriber record. Company name (comp_name) maps to COMPANY merge field, company email (comp_emailaddress) to COM_EMAIL, company sector (comp_sector) to COM_SECTOR, and company website (comp_website) to COM_WEB. Territory (comp_secterr) maps to TERRITORY. These are the 13 fields that Sage CRM's native integration already creates in Mailchimp; we use the same field names to maintain compatibility with any existing Sage CRM Mailchimp sync configuration.

Sage CRM Lead records map to Mailchimp Subscribers using the same merge field mappings as Contacts (FNAME, LNAME, PER_SALUTA, PER_TITLE, EMAIL, PER_EMAIL). Lead-specific fields including lead_companyname, lead_companycountry, and lead_secterr populate the COMPANY, LEA_COUNTR, and TERRITORY merge fields. Leads that have not yet been converted to Contacts in Sage CRM are imported as separate subscribers with no duplicate detection against existing Contact subscribers unless email addresses overlap.

Sage CRM Opportunities have no equivalent in Mailchimp. Mailchimp tracks campaign engagement metrics (opens, clicks, bounces, unsubscribes) but does not store deal stages, revenue amounts, expected close dates, or pipeline data. We export Opportunity records as a CSV inventory delivered to the customer's admin for review. If pipeline tracking is required in Mailchimp, the customer must adopt a third-party CRM integration (e.g., HubSpot, Salesforce) connected to Mailchimp for deal-level data.

Sage CRM Cases have no equivalent in Mailchimp. Mailchimp is not a service or support platform. Case severity, status, and threaded communications (stored in the Communication table linked to case_id) do not transfer. We export Case records as a CSV inventory. If the customer requires case management alongside Mailchimp email marketing, we recommend evaluating a standalone helpdesk tool such as Zendesk or Freshdesk with a Mailchimp integration.

Sage CRM Communications (email logs, call records, meeting notes) stored in the Communication table link to entity IDs for Contact, Lead, Company, Opportunity, or Case. Email content can be preserved as Mailchimp Tags on the Subscriber record (e.g., tag: 'Opened Campaign March 2025') if the customer chooses, but the full communication body does not map to any native Mailchimp object. We scope the tagging strategy with the customer during discovery based on reporting needs.

Sage CRM Custom Entities use internal table names not visible in the UI (e.g., CustomEntityname). Each entity's fields can be mapped to Mailchimp merge fields (text, number, or date types) or Tags if the entity describes categorical data. Mailchimp allows up to 40 merge fields per audience. Custom Entities with more than 40 fields or complex multi-entity relationships cannot be fully represented in Mailchimp; we document the full entity schema during discovery and work with the customer to prioritize the 20 most business-critical fields.

Sage CRM workflow rules are stored as database records with embedded ASP-script logic, escalation triggers, and action definitions. These cannot be exported as portable configuration. We document every active workflow during discovery with its trigger, conditions, and actions, and deliver a written inventory for the customer's admin to evaluate for Mailchimp automation recipes or a third-party workflow tool (Zapier, Make) as replacements.