Migrate from Clarra to Mailchimp

Clar a contact (person linked to a matter via Party) maps directly to a Mailchimp subscriber within an audience. The email address is the unique subscriber identifier. Contacts without email addresses are flagged for manual enrichment before migration. During the migration, we also verify email format validity and remove hard bounces to maintain list hygiene.

Clar a Party records the role a contact plays in a matter (Plaintiff, Defendant, Opposing Counsel, Expert Witness). Mailchimp has no native role concept. We convert role values to Tags (e.g., tag all Defendants with 'Defendant') and optionally create a Role__c merge field for granular reference.

Clar a Matter has no Mailchimp equivalent. Matter name or number is applied as a Tag to all Contacts linked to that Matter (format: 'Matter: {name}'), enabling segmentation by case in Mailchimp. Matter-level custom fields requiring retention become additional merge fields on the subscriber.

Clar a custom contact properties (e.g., referral_source, billing_tier, practice_area) are type-mapped to Mailchimp merge field types — text, number, date, address, or phone. We pre-create merge fields in the target audience before the migration load runs. This ensures that all custom data is correctly associated with each subscriber and can be used for segmentation and personalization in campaigns.

Clar a matter-level custom fields (e.g., court_division, judge_name, case_value) that need preservation are migrated as merge fields on the subscriber records associated with that matter. Since Mailchimp has no matter object, the context is flattened onto each contact record. We retain the original matter identifier as a tag for straightforward reference and future reporting.

Clar a document references attached to matters and parties have no storage location in Mailchimp. We export a document manifest (file names, URLs, parent record IDs) as a CSV reference file for your team to manage externally or in a connected DMS.

Clar a docketing entries (deadline records, court dates, filing deadlines) are litigation-specific with no Mailchimp equivalent. We export a docketing log CSV so your team can rebuild calendar-based automations in Mailchimp Customer Journeys if needed. The exported file includes deadline type, related matter ID, and responsible party, enabling precise recreation of each rule within Mailchimp's workflow builder.

Clar a activities attached to contacts (calls logged, internal notes) can be represented as a historical note merge field in Mailchimp — or excluded from the migration and surfaced as a separate CSV. Mailchimp has no native activity timeline on subscriber records.

Clar a user and owner records linked to contacts by email are resolved against Mailchimp's user model. Because Mailchimp does not have a native owner-assignment concept, attorney or paralegal assignments are migrated as a Tag (e.g., 'Owner: {attorney_name}') on the associated subscriber records.

Clar a contact addresses (street, city, state, zip, country) map directly to Mailchimp's built-in ADDRESS merge field type, which supports formatted address rendering in email templates. Multi-line addresses are parsed and structured per Mailchimp's required field layout. This mapping ensures that address data appears correctly in personalized mailings and can be used for geographic segmentation in campaigns.

Clar a phone and mobilephone fields map to Mailchimp's PHONE merge field type, which supports SMS-capable number flags if your Mailchimp plan includes SMS. We preserve the original phone type label as a value in the field where Clarra distinguishes mobile from office.

Clar a contact email maps directly to Mailchimp's subscriber email address, which serves as the unique subscriber identifier. Subscribers with duplicate emails are flagged for de-duplication before the migration loads.

Clar a internal object IDs are preserved as a text merge field (Clarra_ID__c) on the Mailchimp subscriber record for traceability, delta-run de-duplication, and future reconciliation. This ID also enables integration with external legal analytics tools and supports audit trails for compliance reporting.

Clar a system timestamps (createdate, updatedate) have no native equivalent in Mailchimp subscriber records. We preserve them as DATE merge fields so reporting on contact age and update recency can continue after migration. These date fields also allow you to segment based on when a contact was originally added, facilitating time-based re-engagement campaigns.