Migrate from Legistify to Mailchimp

Legistify matters have no Mailchimp equivalent. The matter record itself does not migrate — only the parties and contacts embedded in the matter are extracted. Matter identifiers are stored as reference tags on contacts for traceability. Matter type, status, and region are also captured as separate tags to allow segmentation by practice area or jurisdiction, preserving the organizational context without reconstructing a full matter record.

Party records with email addresses map directly to Mailchimp contacts. Each party becomes a subscriber in the target audience. Party type (individual, corporate) is stored as a tag rather than a separate field. Tag names use the prefix PTYPE_ to keep the taxonomy organized and avoid collisions with other labels.

Individual parties with first name, last name, email, and phone map to Mailchimp contacts with those merge fields populated. Organization affiliation from the matter is stored as the COMPANY merge field or as a tag. If a party has multiple organization affiliations, each is added as a separate tag to preserve the full relationship without overloading the COMPANY field.

Corporate parties without a named individual contact are represented as contacts with the organization name in the COMPANY merge field. A 'Corporate Party' tag identifies these records. If no email exists for a corporate party, the record is flagged for manual review.

Legistify custom matter properties migrate as Mailchimp merge fields. Text properties under 255 characters map directly; longer text properties are truncated or stored as document reference links. Pick-list values become merge field options. When a property exceeds the 255-character limit, the full text is exported to a CSV with a unique reference ID, and the merge field contains the truncated snippet for quick reference.

Legistify clause library references have no Mailchimp equivalent. Standard clause types (indemnification, limitation of liability, etc.) are stored as tags on the contact if the clause relates to a party. Full clause text is not migrated. Tag names follow a CL_ prefix followed by the clause type, for example CL_INDEMNIFICATION, to make them readily identifiable in the Mailchimp audience.

Compliance records in Legistify track regulatory adherence and deadline dates. These do not map to Mailchimp contacts directly. Compliance status tags (GDPR, SOC2, etc.) may be applied if relevant to contact communication preferences. If a compliance item has an associated deadline, the date is stored in a custom merge field called COMPLIANCE_DEADLINE for future segmentation and reminder workflows.

Legistify documents attached to matters do not migrate to Mailchimp. Mailchimp supports file attachments in campaigns but not document management. Document metadata (filename, upload date, type) is exported to a reference CSV for manual handling. The CSV includes the original Legistify document ID and a link to the source file, enabling your team to reattach documents in a document management system if needed.

Legistify audit logs track matter changes, user actions, and system events. Mailchimp does not have an audit log equivalent for contacts. Audit log data is exported to a separate CSV file for compliance retention. The exported CSV includes timestamps, user IDs, action types, affected matter IDs, and the state of each record at the time of the event, providing a full audit trail.

Legistify matter types (litigation, contracts, compliance, employment) map to Mailchimp tags on the associated party contacts. This allows segmentation by practice area in Mailchimp campaigns without losing organizational context. Tag names use the prefix MTYPE_ followed by the matter type, for example MTYPE_LITIGATION, to keep the taxonomy consistent and simple to filter.

Party roles (plaintiff, defendant, counterparty, vendor, client) from Legistify matter associations are stored as Mailchimp tags. Role values are mapped one-to-one to tag names for consistent labeling across contacts. If a contact has multiple roles across different matters, each role is applied as a separate tag, preserving the full role history without overwriting any existing tags.

Legistify matter status values (active, pending, closed, on-hold) are mapped to Mailchimp tags on party contacts. This enables filtering contacts by matter status without creating separate audiences for each status. Tag names use the prefix MSTATUS_ to distinguish them from other tag categories, for example MSTATUS_ACTIVE, making it straightforward to build segments based on current matter state.