Migrate from GAIA.law to Mailchimp

GAIA.law stores contacts both as standalone contact records and as party links on agreement records. All contacts export by email address as the unique key. Duplicate emails across agreement-party roles collapse to a single Mailchimp Member — tags capture the full party-role context so no role is lost.

GAIA.law company records (counterparties and internal entities) map to Mailchimp's COMPANY merge field. Multi-party agreements where one contact links to multiple companies preserve the primary company as the Mailchimp COMPANY value; secondary companies are added as tags. GAIA.law parent-company hierarchies flatten to a single company name per member.

GAIA.law Agreement objects have no direct Mailchimp equivalent — agreement type and status map to a tag taxonomy (e.g., agreement_type-nda, agreement_status-active). Each agreement generates one or more tags on the relevant party contacts, allowing Mailchimp segmentation by agreement context without creating a formal agreement record in Mailchimp.

GAIA.law party-role values (Counterparty, Internal Reviewer, Witness, Approver, External Counsel) map to Mailchimp tags prefixed with role_ (e.g., role-counterparty, role-witness). Each contact receives one role tag per agreement they are linked to. Role tags enable segmentation so you can email all counterparties or all internal reviewers across agreement sets.

Mailchimp has no native agreement date field. We create a custom datetime merge field EFF_DATE__c and populate it from GAIA.law's agreement effective date. If the agreement has no effective date, the field is left blank. Date format is ISO 8601 (YYYY-MM-DD) to avoid locale formatting conflicts in Mailchimp's automation triggers.

GAIA.law's agreement expiry date migrates to a custom datetime field EXP_DATE__c on the Member record. This field can be used in Mailchimp automation triggers (e.g., send a renewal outreach email 90 days before expiry) if your Mailchimp plan supports time-based automation.

GAIA.law contract value migrates to a custom text field CONTRACT_VALUE__c. Because Mailchimp custom fields are text-merge fields capped at 255 characters, currency values are stored as plain strings (e.g., 'USD 150,000'). Numeric sorting on this field in Mailchimp is not supported — use FlitStack's audit log for numerical reporting on contract value ranges.

GAIA.law agreement types (NDA, MSA, SOW, Employment, Lease, etc.) map to tags with the prefix agreement_type- (e.g., agreement_type-nda, agreement_type-sow). These tags enable Mailchimp segment filtering so you can send type-specific email campaigns (e.g., all NDA counterparties). Up to 50 distinct agreement types are supported in the tag taxonomy.

GAIA.law agreement statuses (Draft, Pending Signature, Active, Expired, Terminated, Renewed) map to tags with the prefix agreement_status- (e.g., agreement_status-active). Status tags drive Mailchimp segmentation for lifecycle campaigns (e.g., outreach to contacts with expired agreements). GAIA.law's status-change timestamps are not transferred — use Mailchimp's campaign activity log for engagement timestamps.

GAIA.law custom fields on agreement objects (e.g., jurisdiction, governing law, auto-renewal clause) map to Mailchimp custom merge fields. Mailchimp limits merge field values to 255 characters — longer text fields are truncated and the full value is preserved in FlitStack's migration audit log. We recommend naming custom fields in ALL_CAPS per Mailchimp convention before migration runs.

GAIA.law tracks e-signature completion status as a native agreement field. Mailchimp has no e-signature capability — this data is preserved as a custom text field ESIGN_STATUS__c with values (Pending, Completed, Declined) carried over from GAIA.law. No Mailchimp automation depends on this field; it is migrated for audit completeness.

GAIA.law stores contract PDF files and attachments linked to agreement records. Mailchimp does not have a document management layer — attachments cannot be migrated into Mailchimp. We recommend exporting agreement documents separately from GAIA.law and storing them in a dedicated document repository (Google Drive, SharePoint, or a DMS) after migration.

GAIA.law's AI-assisted review workflows, approval routing, and inline e-signature orchestration are legal-operations constructs with no Mailchimp equivalent. Email sequences in Mailchimp (Marketing Automation Flows) are a different construct entirely — they must be designed from scratch. We can export GAIA.law workflow definitions as a reference document for rebuilding.