Migrate from CASEpeer to Mailchimp

Every Casepeer Contact (client) becomes a Mailchimp Audience Member. Email address is the unique identifier — contacts without email addresses cannot be added to Mailchimp and are flagged as exceptions before migration. First name, last name, phone, and address fields map to Mailchimp merge fields FNAME, LNAME, PHONE, and ADDRESS respectively.

Email address is the primary key in Mailchimp. Casepeer contacts with duplicate email addresses are merged or flagged per your preferred rule (most-recently-modified wins). Contacts with missing or invalid email addresses are excluded and listed in the exception report for review and correction.

Casepeer first and last name fields populate Mailchimp's standard FNAME and LNAME merge fields. Salutations and suffixes (Jr., III) stored in a separate Casepeer field map to a custom merge field SUFFIX__c if present. This ensures accurate personalization and proper formal address usage in Mailchimp email campaigns.

Phone numbers transfer to Mailchimp's PHONE merge field. Casepeer stores phone in multiple formats (with/without country code); we normalize to E.164 format before loading. Mobile and office numbers stored in separate Casepeer fields merge into a single PHONE field or split into MOBILE + OFFICE custom merge fields.

Casepeer stores street, city, state, zip, and country as separate fields. Mailchimp's ADDRESS merge field expects a structured format with addr1, addr2, city, state, zip, country. We concatenate and split Casepeer's address components into Mailchimp's structured format during load to ensure proper geocoding and deliverability.

Casepeer's case_type values (e.g., Auto Accident, Slip and Fall, Medical Malpractice, Workers' Comp) become Mailchimp Tags on each subscriber. We map each case_type label to a corresponding tag name and apply all applicable tags during migration. Tags enable Mailchimp segmentation by practice area in your customer journeys.

Casepeer's case pipeline stages (e.g., Intake, Under Investigation, Negotiation, Litigation, Settlement, Closed) map to a custom Mailchimp merge field CASE_STATUS__c as pick-list values. This field allows you to segment clients by case progress in Mailchimp campaigns without revealing case details.

Mailchimp does not preserve original subscriber enrollment dates when contacts are added via API — the member-since date is set at import time. We store Casepeer's original contact create date in a custom merge field ORIGINAL_ENROLLMENT_DATE__c for reporting continuity and segmentation by client cohort.

Casepeer's internal record ID is stored in Mailchimp as SOURCE_SYSTEM_ID__c on each subscriber. This enables delta-run de-duplication, rollback identification, and cross-referencing if you need to re-import or reconcile against Casepeer after go-live. It also supports audit trail documentation and compliance verification for future data integrity checks.

Insurance carrier information from Casepeer has no native Mailchimp equivalent. We create a custom merge field INSURANCE_CARRIER__c and populate it where present. This field is optional and may be excluded if your firm prefers not to store this data in a marketing platform.

Casepeer's referral source field (e.g., Doctor referral, Internet search, Repeat client, Partner firm) migrates to a custom merge field REFERRAL_SOURCE__c. This is valuable for Mailchimp segmentation to personalize outreach based on how the client originally found the firm and to improve ad targeting and content relevance.

Casepeer case notes contain attorney-client privileged content, case strategy, medical provider records, and adjuster communications. Mailchimp has no note or case-log functionality. These records are excluded from the Mailchimp migration entirely. We export them to a structured JSON file as part of the migration package for your records.

Casepeer stores case documents, medical records, and correspondence. Mailchimp's file management is limited to email attachment templates and image hosting. Documents are excluded from migration. If you need document links available in Mailchimp, we can add a URL merge field pointing to a secure document portal you designate.

Casepeer workflow rules (case-stage triggers, task generation, deadline rules) are legal-process logic with no equivalent in Mailchimp's email automation builder. These must be rebuilt manually in Mailchimp's Customer Journey editor. We provide a workflow audit export from Casepeer as a rebuild reference.

Casepeer's calendar events and statute of limitations dates are legal calendaring data with no Mailchimp equivalent. Mailchimp's automation can trigger on subscriber date fields (birthday, anniversary), but legal deadlines are not appropriate for a marketing platform. These remain in Casepeer or your chosen legal calendar system.