Migrate from The Legal Assistant to Mailchimp

The Legal Assistant stores client contact records with name, email, phone, and address. These fields map directly to Mailchimp audience members. The contact's primary matter association becomes a tag or custom field so segmented campaigns can target by practice area. We preserve the contact's source ID for de-duplication on subsequent delta runs and maintain the original create date for reporting continuity across both platforms.

Mailchimp has no native case or matter object. Matter status, practice area, and jurisdiction from The Legal Assistant are decomposed: practice area becomes a tag group, case status becomes a custom pick-list field (Case_Status__c), and matter number is stored as a custom text field for reference. Firms with multiple matter types per contact receive multiple tags reflecting each active case association.

The Legal Assistant assigns attorneys and paralegals to contacts under each matter. This relationship is preserved as Mailchimp tags named after the assigned attorney (e.g., 'Attorney: Jane Smith'). Contacts may receive multiple tags if assigned to multiple attorneys across different matters, enabling you to filter the audience by assigned counsel for targeted communications about specific case types.

The Legal Assistant stores street, city, state, ZIP, and country per contact. These map to Mailchimp's native ADDRESS merge field. If The Legal Assistant stores multiple addresses per contact (billing vs. mailing), the primary address is mapped to the standard ADDRESS field and secondary address stored as a custom field (Alt_Address__c).

The Legal Assistant contact phone and mobile phone fields map to the PHONE merge field. If only one phone is stored in The Legal Assistant, it maps to PHONE; the alternate number maps to a custom field (Alt_Phone__c) if present. Both numbers are preserved to ensure your Mailchimp audience retains complete client contact information for campaign outreach.

Mailchimp does not have a native consent-timestamp field. The Legal Assistant intake date is stored as a custom date field (Consent_Date__c) in Mailchimp so firms can demonstrate consent history for GDPR compliance purposes. This date field enables you to segment contacts by when they entered the firm's pipeline and supports audit documentation for regulatory reviews.

The Legal Assistant tracks billing arrangements such as hourly, flat fee, contingency, and pro bono structures. This maps to a custom pick-list field (Billing_Type__c) in Mailchimp with corresponding values. Marketing to contacts based on fee structure requires this field to be migrated as a custom property so you can tailor billing-related communications or segmented offers based on the client's engagement model.

The Legal Assistant deadline and calendar data has no equivalent in Mailchimp's schema and cannot be migrated directly. These records are documented in the migration reference document delivered alongside your audience export. Firms needing deadline reminders should configure Mailchimp's automation triggers independently or integrate a complementary calendar application to maintain scheduling workflows after cutover.

Case documents, templates, and correspondence stored in The Legal Assistant cannot migrate to Mailchimp. While Mailchimp supports campaign attachments including images and PDFs, it is not designed as a document management system for legal case files. We provide a document inventory export separately that lists all matter files organized by contact and case number for your firm's records retention purposes.

Task alerts, matter-stage triggers, and deadline automations built in The Legal Assistant do not transfer to Mailchimp's platform. We export an automation inventory listing every workflow trigger and action configured in your source system so your Mailchimp administrator can rebuild equivalent Customer Journey automations from the reference documentation during the post-migration setup phase.