Migrate from CaseManager to Mailchimp

CaseManager contacts map directly to Mailchimp audience members. We deduplicate by email address when one contact is associated with multiple cases, creating a single member record rather than duplicate records. The contact's primary role and association type are preserved as tags for segmentation reference.

Email serves as the primary key for Mailchimp membership identification. We validate email format before import and flag invalid or malformed addresses in a separate error report for manual correction. Contacts without valid emails are excluded from the initial import batch.

First name maps directly to Mailchimp's standard FNAME merge field, enabling email personalization in campaigns. Blank or null first names in CaseManager pass through as empty strings, which Mailchimp handles gracefully without errors.

Last name maps to Mailchimp's LNAME merge field. Some CaseManager configurations store the full name in a single field — our process detects this scenario and splits by the first whitespace character if a separate last-name field is empty.

Phone number maps to Mailchimp's PHONE merge field for SMS-enabled audiences. We strip all non-numeric characters during transformation except leading plus signs to preserve international dialing codes, matching Mailchimp's phone formatting requirements.

CaseManager case status values such as Open, Pending, Closed, and Resolved become Mailchimp tags on the member record. We create tags using the format 'CaseStatus: Open' to preserve context and enable precise segmentation by historical case state across the audience.

Case type values like Billing, Support, Legal, and Sales become Mailchimp tags on the member record. When a single contact is associated with multiple case types, each generates a separate tag on that member's record, creating a comprehensive case history profile.

Priority levels including High, Medium, and Low map to tags using the format 'CasePriority: High'. This tagging approach enables targeted re-engagement campaigns focusing specifically on high-priority past contacts with historical case involvement.

Mailchimp lacks a native owner or assignee concept for member records. We create a custom text merge field named OWNER_NAME and populate it with the CaseManager assigned user's name. Email-based owner lookup is not applicable in Mailchimp's contact-centric model.

Mailchimp's native created_at timestamp reflects when the record was imported, not the original CaseManager record creation date. We preserve the original case creation date in a custom merge field for historical reference and continuity in reporting.

The original last-modified timestamp from CaseManager is preserved as a custom merge field on the member record. Mailchimp's last-activity timestamp tracks email engagement separately and does not reflect case update activity from the source system.

CaseManager structured address fields including street, city, state, postal code, and country map to Mailchimp's compound ADDRESS merge field using the required format: addr1, addr2, city, state, zip, and country components.

Custom fields defined on CaseManager case records are mapped to Mailchimp merge fields with corresponding data types. Text maps to text, number maps to number, and date fields use Mailchimp's date format. Fields exceeding 250 characters are truncated with notation in the migration report.

Contact-level custom fields from CaseManager are mapped to Mailchimp merge fields using the same type-conversion logic. We create all required merge fields in Mailchimp before the import batch runs to ensure schema availability during data loading.

Mailchimp provides no case, ticket, or opportunity object — it operates purely on members and campaigns. The case record as a standalone entity does not migrate. Only contact-linked data including parties and case metadata moves into member tags and merge fields for retention.

Files and documents attached to CaseManager cases cannot migrate to Mailchimp's platform. We generate a comprehensive file inventory report listing all attachments organized by case ID so your team can host them externally or document the archive location for compliance.

Mailchimp tracks email campaign activity including opens and clicks only. Internal case activity history such as call logs, meeting records, and internal notes does not migrate. We export the complete activity log as a separate CSV file for reference and compliance purposes.

CaseManager workflows represent case-centric automation rules triggered by status changes, assignment updates, or date-based escalations. These have no structural equivalent in Mailchimp's contact-centric Customer Journeys. We export workflow definitions as a PDF reference document for rebuilding.