Migrate from Corteza CRM to Mailchimp

Corteza Contact records map directly to Mailchimp Members. The email address serves as the primary key and deduplication identifier. We preserve first name, last name, phone, job title, and postal address as Mailchimp merge fields (FNAME, LNAME, PHONE, JOBTITLE, ADDRESS). Any existing Mailchimp Member with the same email address is matched rather than duplicated during import. Contact-account linkage is preserved by tagging the Member with the parent Account name as a Mailchimp tag.

Corteza Lead records map to Mailchimp Members using the same email-based deduplication logic as Contacts. We apply a Mailchimp tag Lead to distinguish migrated leads from converted contacts in the audience, and we carry forward the lead rating as a merge field so that sales-qualified status is available for segmentation without requiring a full CRM. Leads that have not been converted still migrate because they represent a marketing addressable audience.

Corteza Accounts map to Mailchimp as a tag applied to every Member that is linked to the Account via the contact-account relationship. The Account name becomes the tag value (for example, Acme Corporation), allowing segmentation by company across the Mailchimp audience. Mailchimp does not have a native account or company object, so this tag-based approach provides the closest equivalent for audience segmentation by organization.

Corteza CampaignMember records link Contacts and Leads to a Campaign. We migrate each CampaignMember record by adding a Mailchimp tag matching the Campaign name to the corresponding Member record. The Campaign itself is documented as a Mailchimp Campaign record so that the campaign naming structure is preserved. Actual campaign performance statistics (opens, clicks, bounces) do not transfer because they are Mailchimp-native metrics that belong to the Mailchimp instance.

Corteza Opportunities track deal stage, amount, probability, close date, and account linkage. Mailchimp has no Opportunity, deal, or pipeline object. We document the full Opportunity inventory during migration — including stage, amount, probability, close date, and owner — in a CSV delivered alongside the audience migration so that the customer admin can decide how to handle pipeline data (CRM rebuild, spreadsheet, or no action). Opportunities are not loaded into Mailchimp as there is no valid destination field.

Corteza Cases track support issues with status, priority, origin, and linked Account and Contact. Mailchimp has no case or ticket object. We migrate case linkage by adding a Mailchimp tag with a Case: prefix and the case status to the Member record (for example, Case:Open, Case:Resolved). Full case history, conversation threads, and resolution notes are documented in a separate CSV as Mailchimp does not store support interactions natively.

Corteza event records for meetings and calls linked to Contacts or Leads map to Mailchimp Member activity where the platform supports it. Meeting engagements are preserved as notes on the Member record with date, duration, and location. Mailchimp does not store full email body content in member records, so we document email engagement dates and subject lines as Member notes for reference. Plain task records that are standalone (not linked to a specific Contact or Lead) are similarly documented as Member notes.

Corteza custom modules with simple field types (text, number, date, phone, checkbox) that contain marketing-relevant data map to Mailchimp merge fields on the Member record. We evaluate each custom module during discovery to identify which contain addressable contact data versus operational CRM data that has no Mailchimp equivalent. Merge field names are derived from the Corteza field label and limited to ASCII characters; long text fields exceeding 255 characters are truncated and documented as truncated in the migration report.