Migrate from LegalE to Twenty CRM

LegalE client records map directly to Twenty CRM People objects. Every person record carries a name, email, phone, and job title. The company association migrates as a companyId relation — the parent Company must land first so the foreign key resolves. Records without a company association attach to a default 'Unassigned' company created during setup.

LegalE company records (law firm names, corporate client organizations) map directly to Twenty CRM Companies objects. Industry, size, website, and address fields migrate as standard Company fields. Parent-child company hierarchies use the same ParentId pattern — the parent company must migrate first or circular references are flagged and resolved before the run.

LegalE matter or case records do not have a direct One-to-One equivalent in Twenty's default Opportunity object. We map them to Opportunities and add custom fields for legal-specific properties: Practice_Area__c (text), Jurisdiction__c (text), Matter_Status__c (select), Billing_Arrangement__c (select). The Opportunity stage maps to a Matter_Stage field with legal-relevant values: Intake, Active, Pending, Closed.

If LegalE stores practice areas (Family Law, Corporate, Litigation, etc.) as a structured field, we create a Practice_Area__c custom select field on Twenty's Opportunity object. Values map one-to-one. If practice areas are stored as tags or free-text, they migrate as a text array in a custom field and can be converted to select options post-migration.

Hourly, flat-fee, contingency, and pro-bono billing arrangements from LegalE migrate to a Billing_Arrangement__c custom select field on Opportunity. Value mapping is direct where the pick-list matches; non-matching values are preserved as a text fallback and can be normalized in Twenty after migration.

LegalE assigns attorneys and staff to matters by user ID. Twenty CRM uses WorkspaceMember for user management. We resolve LegalE user IDs to Twenty WorkspaceMember records by email match — unmatched attorneys are flagged before migration. Unassigned matters receive a fallback assignee designated by your team during scoping.

LegalE note records and communication logs migrate as Twenty CRM Notes attached to the parent People or Opportunity record. Original timestamps, note authors, and any structured fields (conflict-check results, intake notes) are preserved. Notes with attachments require file re-upload to Twenty's storage since the attachment format differs.

LegalE task records (deadlines, court filing reminders, client follow-ups) map directly to Twenty CRM Tasks linked to the parent People or Opportunity. Due dates, assignees, and completion status transfer with original timestamps. Recurring tasks that rely on LegalE automation logic are flagged for manual rebuild in Twenty.

LegalE document attachments on matters or client records are downloaded and re-uploaded to Twenty CRM. Files attach to the corresponding Note record or are stored as file links in a custom URL field. File size limits and storage costs differ between platforms — FlitStack flags oversized files before migration.

Any LegalE custom field that does not map to a standard Twenty object field becomes a custom field created in Settings → Data Model before the migration run. FlitStack documents every custom field with its type, pick-list values, and object assignment in the pre-migration schema plan. Fields must exist before CSV import so the import mapper recognizes them.

LegalE may store relationship metadata between contacts (primary, co-counsel, opposing counsel). Twenty CRM supports relation fields between People records. We map primary contact relationships to a Relation record with type 'Primary Contact'. Other relationship types migrate as Relation records with the original label preserved or a normalized type value.

If LegalE stores invoice history and line items, we assess whether to create a custom Invoice object in Twenty or store summary billing data on the Opportunity. A custom Invoice object captures invoice number, date, amount, status, and linked Opportunity. Invoice line items require a custom Line_Item__c field or a second custom object with a relation to Invoice.