Migrate from Assembly Trialworks to Salesforce Sales Cloud

Trialworks party records with role type 'Plaintiff' or 'Client' map directly to Salesforce Contacts. Each party record's name, address, phone, and email fields translate to Contact standard fields. The Contact's AccountId lookup points to the primary defendant Account or a default 'Matter' Account structure your firm defines before migration.

Non-client party records (Defendant, Medical Provider, Insurance Adjuster, Witness) map to Salesforce Contacts with a custom Party_Role__c picklist field to preserve the Trialworks role type designation. Multiple contacts can share the same Case parent. The original role value is captured in the custom field for reporting and rebuild reference.

Trialworks case files map to a Salesforce custom Matter__c object or to the standard Case object if your org includes Service Cloud. We recommend a custom object because it supports the multi-tab structure Trialworks uses. Each tab (Parties, Medical Records, Injuries, Statutes) becomes a related list or a child custom object with a lookup to Matter__c.

Trialworks medical record entries (provider name, date of service, record type, chart reference) have no Salesforce standard equivalent. We create a Medical_Record__c custom object with a lookup to the Matter__c parent and map each field individually. If records include attached files, those are re-uploaded to Salesforce Files and linked via ContentDocumentLink.

Injury descriptions, body parts affected, and damage categories from Trialworks tab fields map to a custom Injury__c object linked to Matter__c. Each injury gets its own record so your Salesforce reports can filter by injury type or body part. Injury severity and ICD code references map to custom picklist or text fields.

Trialworks statute-of-limitations dates map to a Statute_of_Limitations__c date field on the Matter__c object. A companion Statute_Alert_Date__c field (calculated as 90 or 180 days before the deadline) enables Salesforce Flow alerts. Firms can extend this with a Formula field that displays days remaining as a traffic-light indicator.

Trialworks file attachments are downloaded from the case file tabs (PLEADINGS, DISCOVERY, MEDICAL, CORRESPONDENCE) and re-uploaded as Salesforce Files. Each file is linked to the Matter__c record via ContentDocumentLink. Original file names, categories, and upload dates are preserved in Salesforce File metadata. Large document sets may require chunked upload batches.

Insurance carrier, policy number, coverage limits, and deductible information from Trialworks maps to a custom Insurance_Coverage__c object linked to Matter__c. Policy type (auto, GL, workers' comp) maps via value_mapping to a custom picklist. Coverage amounts map to currency fields with the original currency preserved.

Trialworks user accounts are matched to Salesforce Users by email address. Active Trialworks users with a confirmed Salesforce User match get their cases assigned to their Salesforce UserId as OwnerId. Unmatched users are flagged before migration — your admin either creates Salesforce User accounts first or assigns those records to a fallback owner.

Trialworks calendar entries and court deadline reminders map to Salesforce Events (for scheduled hearings or depositions) or Tasks (for to-do items). The original event date, time, and description map to Event.StartDateTime and Subject fields. Court deadlines that require all-day reminders map to Salesforce Tasks with IsAllDayEvent=true and a custom Due_Date__c datetime field.

Every Trialworks custom field maps to a Salesforce custom field on the appropriate destination object. Field type mapping follows standard conventions: text fields to Text(255), long text to Long Text Area, dates to Date, pick-lists to picklist with values preserved. Salesforce __c suffix is applied to all custom field API names. Fields are created in the target org before the migration run.

Contingency fee percentages, hourly rates, flat fees, and retainer amounts from Trialworks map to a Fee_Arrangement__c custom object or fields on Matter__c. Fee type maps via value_mapping to a structured picklist (Contingency, Hourly, Flat Fee, Hybrid). Outstanding balance tracking is not native to Salesforce and requires a custom field or integration with a billing tool.