Migrate from Assembly Trialworks to Twenty CRM

Trialworks Case maps to Twenty Opportunity as the primary record. Case Number and Case Name map to Opportunity.name; case status maps to stage via value_mapping against a pick-list you define. Case-type pick-list values require explicit mapping to your Twenty pipeline stages before migration. Original create date preserved as a custom datetime field since Twenty's CreatedAt is set at migration time.

Party records map directly to Twenty People. PartyName becomes the person's display name; address, phone, and email map to the equivalent People fields. PartyType (Plaintiff, Defendant, etc.) has no native equivalent in Twenty — we carry it as a custom select field (PartyType__c) on the People record. Parties without an email are created as People with no email, and you choose whether to merge duplicate entries.

Insurance Carrier records map to Twenty Companies. CarrierName becomes Company.name; address maps to the company address fields. Claim Number is carried as a custom text field on the associated Opportunity so the carrier-to-claim link remains queryable. If a carrier has multiple claimants, the carrier record is created once and linked via OpportunityId.

Attorney party records map to Twenty People and are resolved to WorkspaceMembers by email match. If the attorney email matches an existing Twenty workspace member, the People record is linked to that member. If no match, the attorney is created as a People record without workspace access. Opposing counsel is stored as a custom People field on the related Opportunity.

Trialworks documents are represented as Twenty Notes attached to the related Opportunity (Case). The Note body contains the original file path (e.g., \\server\cases\123\exhibit-A.pdf) and document type (Pleading, Correspondence, Exhibit). File attachments themselves require manual re-upload or API-based transfer since Trialworks CSV export does not package file binaries — see the gotchas section for details.

Trialworks firms commonly add custom fields for litigation-specific data: Damages Breakdown, Court Venue, Jurisdiction, Statute of Limitations, etc. All custom fields on Case are recreated as Twenty Opportunity custom fields via Settings → Data Model before migration. We deliver a field creation plan listing field name, type (text, number, date, select), and pick-list values so your Twenty admin can pre-provision them.

Custom fields on Party records — such as Bar Number for attorney parties or Insurance Policy ID for insured parties — are recreated as People custom fields in Twenty. The mapping plan names each custom field and its target type so the schema is ready before data lands. Fields that apply only to attorney-type parties are created as optional fields on the People object.

Trialworks tracks case status transitions with timestamps. Twenty has no native audit trail for Opportunity stage changes. We preserve the last 10 status transitions as a custom long-text field (Case_Status_History__c) on each Opportunity, formatted as 'Status | Date' lines. This is reference data — it does not drive pipeline logic in Twenty.

Plaintiff, Defendant, Claimant, Co-Counsel, and Expert Witness are party-role values from Trialworks that have no direct equivalent in Twenty. We map each role string to a corresponding value in a custom PartyType__c select field on the People object. You define the full pick-list in Twenty's data model before migration so the import validates cleanly.

Settlement amounts in Trialworks map to a custom currency field (Settlement_Amount__c) on the Opportunity. Amount__c on the Opportunity holds the case value or damages estimate; Settlement_Amount__c holds the resolved settlement. Both coexist as separate custom fields so your pipeline reporting and settlement accounting remain distinct.