Migrate from GAIA.law to Twenty CRM

GAIA.law stakeholders (contacts tied to agreements) map to Twenty CRM People. Fields migrate: name, email, phone, job title, company affiliation. Stakeholder-role labels from GAIA.law require a custom pick-list field on the People object in Twenty since Twenty has no native role-label field.

GAIA.law organizations map to Twenty CRM Companies. Organization name becomes Company displayName. Industry defaults to 'Legal Services' unless GAIA.law stores a specific industry value. Domain maps to the website field. Parent-organization hierarchies in GAIA.law map to the same parent-company structure in Twenty.

GAIA.law agreements become Twenty CRM Opportunities to leverage pipeline tracking. Agreement name maps to Opportunity name. Contract value maps to Opportunity amount. Agreement status (Draft, In Review, Executed, Expired) requires a custom pick-list field (Agreement_Status__c) on the Opportunity since Twenty has no native contract-status field.

Agreement type, effective date, expiration date, and contract ID from GAIA.law migrate as custom fields on Twenty's Opportunity object. These fields must be created in Twenty's Settings → Data Model before import. Agreement type becomes a custom select field with GAIA.law's exact agreement type values.

GAIA.law stakeholder roles (Authorized Signatory, Witness, Reviewer, etc.) require a custom pick-list field on Twenty's People object. Each role value is created as a select option. If the role is unstructured text in GAIA.law, it migrates as a text field for manual cleanup post-migration.

GAIA.law stakeholder activities (meeting records, call logs, notes) map to Twenty CRM Tasks and Notes objects. Original timestamps, activity type, and parent People record link are preserved. Twenty's Task object captures assignee, due date, and completion status from GAIA.law's activity records.

GAIA.law approval chains and routing rules have no equivalent in Twenty CRM. Twenty's workflow builder handles trigger-based automations but lacks approval-chain logic such as reviewer assignment gates, escalation routing, or conditional approval paths. FlitStack exports the complete GAIA.law workflow definitions as a structured reference document for your Twenty admin to rebuild manually in Twenty's Settings → Workflows editor. Plan for 1-3 days of admin time per complex approval chain to map conditions and rebuild routing logic.

GAIA.law e-signature records (signatory email, signature timestamp, completion status) migrate as custom fields on the associated agreement's Opportunity record in Twenty. Since Twenty has no native e-sign capability, signature status is preserved as a custom select field rather than a native status.

GAIA.law contract files and attachments re-upload to Twenty CRM's attachment storage linked to the corresponding Opportunity (agreement) record. Each file is downloaded from GAIA.law and re-hosted within Twenty. File size limits apply — contracts exceeding 25MB per file are flagged for splitting before upload.

GAIA.law custom objects (e.g., Regulatory Filing, Compliance Record, Legal Hold) map 1:1 to Twenty CRM custom objects. Custom-object fields migrate to corresponding Twenty custom object fields. N:N relationships between custom objects in GAIA.law require junction objects in Twenty since Twenty uses a relational model rather than a document-store approach.

GAIA.law allows N:N links between agreements and stakeholders (multiple signers per agreement, one stakeholder across multiple agreements). In Twenty CRM, this maps to a custom multiple-select field on the Opportunity pointing to People records, or a junction object if the relationship needs full history tracking with timestamps.

GAIA.law agreement comments and discussion threads migrate as Twenty CRM Notes attached to the corresponding Opportunity record. Thread structure is flattened — each comment becomes a separate Note record with the original author and timestamp preserved in the Note body or custom fields.