Migrate from Legal Files to Twenty CRM

Legal Files matters map to a Twenty custom object named Matter when the matter tracks legal case data (status, court, opposing counsel). When the matter also represents a revenue-generating engagement, it maps to Twenty's Opportunity object with the custom Matter object linked as a related record. We create the custom object in Twenty's Settings → Data Model before migration runs.

All party roles — plaintiff, defendant, third party, interested party — map to Twenty's People object. The party role type migrates as a custom select field (PartyRole__c) so you can filter by role in Twenty views. Multiple parties on one matter link via the custom Matter object's N:1 relationship to People.

Attorney records from Legal Files migrate as People records with a custom field (AttorneyRole__c) set to 'Responsible Attorney' or 'Of Counsel' based on the source role. Attorney bar number, firm name, and contact info map to standard and custom fields on the People record. Attorney email is used for Twenty Workspace Member resolution.

Opposing counsel migrates as a People record with AttorneyRole__c set to 'Opposing Counsel'. Firm name, address, phone, and email map to standard and custom fields. Opposing counsel records are flagged separately in Twenty views so your team can distinguish them from your own attorneys.

Legal Files stores documents with version history inside the matter. Since Twenty has no native document management, we preserve the original document path or URL as a text field on the related Matter record (DocumentRef__c). Your team chooses whether to keep files in existing storage and link by path, or re-upload to a connected storage solution post-migration.

Court dates, filing deadlines, and statute of limitations from Legal Files migrate as Twenty Tasks linked to the Matter custom object. The due date maps to Task dueDate, and the deadline description maps to Task subject. Task status tracks completion; incomplete deadlines appear as open tasks in Twenty's kanban or list view.

Free-form case notes from Legal Files migrate as Twenty Notes attached to the corresponding Matter custom object. Note body preserves text content; author and create date map to Note metadata. Rich-text formatting is simplified to plain text where the original contains unsupported markup.

Insurance carrier name, policy number, and billing reference from Legal Files have no direct Twenty equivalent. We create custom text fields on the Matter custom object (InsuranceCarrier__c, PolicyNumber__c, BillingReference__c) and preserve the values during migration. Billing integration requires separate configuration in Twenty.

Court name, jurisdiction, and venue from Legal Files migrate as custom select fields on the Matter object (Court__c, Jurisdiction__c). The court address maps to a custom text field if present. These fields enable filtering by jurisdiction in Twenty's table or kanban views.

Any custom fields defined in Legal Files' schema builder (e.g., CaseType, StatuteOfLimitations, TrialDate) map to identically named custom fields on the Twenty Matter custom object. Field type mapping follows: text → TEXT, number → NUMBER, date → DATE, picklist → SELECT. The custom fields must be created in Settings → Data Model before import.

Legal Files user accounts (attorneys, paralegals, administrative staff) map to Twenty Workspace Members. Resolution is by email address — if a Legal Files user email matches an existing Twenty Workspace Member, records assign to that user; otherwise the user is flagged and must be invited to Twenty before migration commits.

Legal Files supports multiple parties linked to one matter and one party linked to multiple matters (N:N). Twenty's standard model is N:1 (one Company per People record via companyId). We handle this by creating a custom junction object (MatterParty__c) with relations to both Matter and People, preserving the full association graph from Legal Files.