Migrate from Legal Workspace to Twenty CRM

Legal workspace contacts map directly to Twenty's People object. Primary email, phone, job title, and address fields migrate 1:1. Contacts without a company link land as standalone People records in Twenty — your team can link them to Companies after import.

Legal workspace organizations map to Twenty's Company object. Company name, website, industry, and employee count migrate directly. If the source stores parent-child company hierarchies, the parentId field on the Company record maps to the parent Company record — parent must migrate first.

Matters translate to Twenty Opportunities — the deal-name becomes the matter name, the matter number becomes a custom field (Matter_Number__c), and the estimated value or billing amount maps to the Opportunity amount field. Matter status (Active, Closed, Pending) maps to Opportunity stage via value-mapping.

Each matter status value in the source system maps to a corresponding Twenty Opportunity stage pick-list value. Active matters route to 'New' or a stage representing open work; Closed matters route to 'Won' or 'Closed'; Pending routes to a stage representing work-on-hold. If the source has more than five matter statuses, Twenty's stage pick-list is expanded to match.

Legal billing rates have no direct equivalent in Twenty's Opportunity object. We create a custom number field (Billing_Rate__c) on the Opportunity object and populate it from the matter's rate field. If multiple rate types exist (e.g., partner rate, associate rate), we create additional custom fields and map each explicitly.

Practice area labels (Corporate, Litigation, Real Estate, etc.) become a custom select field (Practice_Area__c) on the Opportunity object. We create the pick-list options in Twenty's Settings → Data Model before import, then map each source value to the corresponding option during the ETL run.

The responsible attorney email resolves against Twenty's workspace members by email match. If the attorney does not yet have a Twenty account, we flag the record and assign it to a fallback owner — your team invites the attorney before the full migration runs. The Opportunity Assignee field is populated from this resolution.

Tasks linked to matters migrate to Twenty's Task object with the parent Opportunity reference preserved. Due dates, task status (Open, Completed), and task descriptions carry over. If the source uses sub-task hierarchies, we flatten them into individual Task records and note the parent-child relationship in a custom field.

Notes attached to matters migrate to Twenty's Note object, linked to the corresponding Opportunity record. Rich-text formatting in source notes is preserved where the export format supports it; plain-text notes migrate as-is. Large documents referenced in the source are noted in a custom URL field — actual files are flagged for manual re-upload to Twenty's file storage.

Any custom fields on the source matter object (e.g., court jurisdiction, opposing counsel, filing deadline) are created as custom fields on Twenty's Opportunity object via Settings → Data Model before the migration runs. The import CSV includes these custom columns so the values land in the right fields on first load.

Legal billing records — invoices, trust account entries, and payment histories — have no equivalent in Twenty CRM. These records are preserved as a separate CSV export for import into dedicated legal accounting software (e.g.,，火山 or LawPay). The billing CSV is handed off as a rebuild artifact, not loaded into Twenty.

Client intake fields (referral source, conflict-check result, engagement status) that live on the contact or matter record in the source platform become custom fields on Twenty's People object. We create these fields before import and populate them from the source export so the data is present from day one.