Migrate from LegalServer to Twenty CRM

LegalServer Contact records map 1:1 to Twenty People. Names, emails, phone numbers, addresses, and contact type (Individual/Organization) transfer directly. The Person record must be created before linking to an Organization/Company record. During migration, each Contact's unique LegalServer identifier is preserved as a custom field for audit trails and future integrations. Duplicate detection runs automatically using email matching to prevent redundant People records in Twenty's workspace.

LegalServer Organization records map to Twenty Companies. Organization name, type, address, and domain fields transfer as Company.Name, Company.type, Company.address fields. Parent/child organization hierarchies use Twenty's CompanyRelations object. Each Organization's LegalServer ID is stored in a custom field for reference and data reconciliation. Organization hierarchies with multiple levels are flattened and linked via CompanyRelations records to maintain the relationship structure in Twenty.

LegalServer Case (Matter) records become Twenty Opportunities. The case number maps to a custom Opportunity field (LegalServer_Case_Number__c), case name becomes Opportunity.Name, and case status values are mapped to Twenty pipeline stage values. Case type, service area, and billing type migrate as custom select fields on the Opportunity.

LegalServer's service area pick-list values (Immigration, Housing, Family Law, etc.) have no native equivalent in Twenty. We create a custom select field (Service_Area__c) on Opportunity and map each LegalServer value to the matching Twenty option. This field drives pipeline filtering in Twenty.

LegalServer Grant Management tracks funding sources, available balance, and billing type (Flat Hourly Rate, Variable Hourly Rate). These have no native Twenty equivalent. We create a Grant custom object with fields for Grant_Name__c, Available_Balance__c, Billing_Type__c, and a link to the Opportunity representing the associated case.

LegalServer Contractor records (managed assigned counsel, panel attorneys) include organization/individual type, subject matter expertise, languages, and fee structures. Individual contractors map to Twenty People; organizational contractors map to Companies. Fee structures and case assignment links require a custom Contractor_Panel__c junction object.

LegalServer Time Slips (staff time recorded against a case) become Twenty Tasks with Type='Billable'. Each Task links to the Opportunity representing the case and carries the staff member as the Task assignee. Hours, date, and billing description are stored as custom fields on the Task.

LegalServer Communication Logs on a case (emails, phone calls, letters) become Twenty Notes attached to the corresponding Opportunity. Original timestamp, communicating party, and log text are preserved in the Note body. Each Note links to the Opportunity representing the case.

LegalServer documents attached to cases ( briefs, correspondence, court filings) are downloaded and re-uploaded as Notes with file attachments in Twenty. We preserve the original document name and upload date. File size limits per Twenty's storage configuration apply — large batches are split across import runs.

LegalServer site-specific custom fields on cases (e.g., Court_Date__c, Judicial_Officer__c, Referral_Source__c) are created as custom fields on the Opportunity object before migration. All custom field definitions are extracted from LegalServer's Admin > Custom Field Management and mapped field-by-field to Twenty's Settings → Data Model.

LegalServer prescreen records (intake eligibility screening) do not map to any standard Twenty object. We create a Prescreen custom object capturing eligibility fields, income data, and screening outcome, linked to the resulting Case/Opportunity. Poverty percentage migrates as a custom number field.

LegalServer Outreach records (community outreach events, clinic sign-ups) become a custom Outreach_Event__c object in Twenty with event date, outreach type, location, and attendees as custom fields. Attendance records link to People. Each outreach event preserves its original LegalServer ID and creation timestamp for audit purposes. The outreach type field uses a picklist that mirrors LegalServer's values, ensuring consistency in reporting and filtering across the workspace.

LegalServer Financial Information records (poverty percentage, income data) used for eligibility migrate as custom fields on the People record (Poverty_Percentage__c, Income_Level__c). These drive case acceptance decisions and grant eligibility tracking. Each Financial Information record's original LegalServer ID is preserved for reconciliation. The poverty percentage field uses number formatting matching LegalServer's precision, and income data is stored as currency values to maintain accuracy in financial reporting.

LegalServer staff users map to Twenty Workspace Members. Owner resolution happens by email match — if a LegalServer staff email matches a Twenty workspace member email, records are assigned to that user. Unmatched owners are flagged for manual assignment before migration commits.