Migrate from Legl to Mailchimp

Legl contacts migrate as Mailchimp members. Email address serves as the primary key for deduplication — Legl records with duplicate emails collapse to one Mailchimp member. Original Legl contact create date migrates as a merge field since Mailchimp sets CreatedAt at import time.

Legl business records attach to contacts via a linked entity. Business name, industry, and registration number merge into Mailchimp member merge fields. Multiple businesses per contact collapse to the primary business record or the most-recently-modified entry. If the primary business changes later, FlitStack updates the merge field during delta-pickup.

Legl engage-request records track client interaction status. Each unique engage-request status value (pending, completed, declined) becomes a Mailchimp tag applied to the associated member. Tags enable Mailchimp segment filters to target clients by engagement state. We also preserve the engage-request type as a separate tag, allowing segmentation by both status and category.

Legl risk-assessment outcomes store as structured data per client. The assessment status (low, medium, high risk) migrates to a custom merge field. Full assessment JSON cannot fit in Mailchimp's 255-character merge field limit — outcome summary migrates only. The full JSON is exported separately for compliance records.

Legl payment records track client billing transactions. Mailchimp is an email platform, not a billing system. Payment history does not migrate — export to a CSV for accounting records. Consider a separate accounting system export. This CSV can be imported into your accounting tool for reconciliation.

Legl Organisation records contain firm-level metadata (firm name, jurisdiction). This maps to Mailchimp account-level information and can be stored as static audience fields for reference, though Mailchimp does not have a native firm-level object. Use these static fields to set audience defaults and sender identity.

Legl AML ongoing monitoring flags per client become Mailchimp tags. Values like 'monitoring_active', 'monitoring_paused', 'monitoring_flagged' map to corresponding tags so compliance-aware segments can filter clients for communication restrictions. These tags help ensure that clients with active AML flags are excluded from marketing campaigns per regulatory requirements.

Legl stores client documents and signed agreements. Mailchimp does not have a document repository. Documents remain in Legl or export to a document management system. Client-facing communication in Mailchimp can link to Legl-hosted documents by URL. Ensure URLs are kept up to date as Legl document IDs may change after migration.

Legl matters track legal work categories per client. Matter type names (e.g., 'M&A', 'Employment', 'IP') split into individual Mailchimp tags on the member. A client with three matters generates three tags rather than a single matter-list field. This granular tagging supports precise segmentation by legal practice area.

Legl staff records track which team member owns a client relationship. Mailchimp does not have a native owner-assignment model for members. Staff attribution does not migrate — if owner tracking is needed, add staff email as a merge field manually post-migration.