Migrate from LegalE to Mailchimp

LegalE contacts and signers map 1:1 to Mailchimp contacts. Email address is the unique identifier and must be present in the LegalE export for the record to import. Contacts without a valid email address are flagged and excluded from the migration batch.

LegalE document names are stored as Mailchimp tags (one tag per document name) so contacts can be segmented by signing history. The most recent document name is also placed in a custom merge field (DOC_LAST_NAME) for use in email merge tags. Long document names are truncated at 255 characters per Mailchimp's merge field limit.

LegalE signer status values (signed, pending, declined, viewed) have no Mailchimp native equivalent. We create a custom merge field SIGNER_STATUS__c and populate it with the most recent signing event state. This field is static post-migration — Mailchimp cannot update it when a signing event occurs in LegalE.

The timestamp of the most recent signing event is stored as a custom datetime merge field (SIGNED_DATE__c) on the Mailchimp contact. This preserves the original signing date for segmentation and reporting. If multiple documents were signed, the most recent date is used.

LegalE's internal document ID is encoded as a Mailchimp tag with the prefix DOC_ so the contact's signing history can be reconciled back to the LegalE record. Tags are used instead of a merge field because tags support multiple values per contact, whereas merge fields are single-value.

LegalE recipient roles (signer, approver, cc, witness) are placed in a custom pick-list merge field (SIGNER_ROLE__c) on the contact. This allows segmentation by role — for example, filtering to only contacts who were designated as approvers in LegalE. If your organization uses additional role labels beyond the standard four, they can be added to the pick-list before migration, and the field can be mapped to Mailchimp's built-in segmentation filters for more granular targeting.

LegalE's sequential signing order has no Mailchimp construct. We export the signing order as a JSON reference file alongside the migration so your team can manually recreate any sequential logic in Mailchimp automations if required. This file includes the order index, the document IDs associated with each step, and any conditional branches. You can use it as a blueprint to set up Mailchimp Customer Journeys that trigger based on contact field values or tag presence.

LegalE workflows (reminder sequences, escalation paths, conditional signing rules) cannot be imported into Mailchimp. FlitStack exports the workflow definitions as a JSON reference document that your Mailchimp admin can use as a blueprint when building equivalent customer journeys. The exported JSON captures each step's trigger conditions, the associated document IDs, and any time delays or email templates referenced. This data serves as a checklist for recreating automated sequences in Mailchimp's automation builder.

LegalE's per-document audit trail (IP address, browser, timestamps for each signing event) has no native Mailchimp field to receive it. We export the full audit log as a downloadable CSV reference. It should be retained in your records management system rather than relied upon post-migration.

LegalE's sender or account owner tied to a signing event is stored in a custom text merge field (ORIGINAL_SENDER__c) on the contact. Mailchimp has no native owner or user concept at the contact level, so this field is purely informational and cannot drive Mailchimp's permissions model.