Migrate from Assembly Trialworks to Microsoft Dynamics 365 Sales

Trialworks Client maps directly to Dynamics 365 Sales Account. The client name becomes Account Name, primary address maps to Address fields, and the firm's main phone maps to Telephone 1. Owner resolution uses the assigned Trialworks staff member's email matched against Dynamics 365 Sales user email addresses.

Dynamics 365 Sales has no native matter or case object. We create a custom tw_Matter__c table in Dataverse with custom columns matching each Trialworks matter field — including case type, case number, assigned attorney, opposing counsel, court/jurisdiction, status, and open/close dates. The custom table links to the Account (client) record via a lookup field.

Trialworks matter types — such as Personal Injury, Contract Dispute, Family Law, and Estate Planning — are mapped one-to-one to values in the tw_CaseType__c custom pick-list column on the tw_Matter__c table. During schema design we create each pick-list entry in the Dynamics 365 Sales column definition, validate against existing Trialworks data for consistency, and handle any new case categories by adding them to the pick-list before migration runs.

Trialworks party contacts — including plaintiffs, defendants, witnesses, and opposing counsel — are mapped to Dynamics 365 Sales Contact records. Each contact is linked to its primary Client/Account through the AccountId lookup field, preserving the party role in a custom tw_PartyRoleType__c pick-list. Contacts that lack a primary client are attached to a default 'Unassigned Party' Account record to keep the CRM referentially intact and avoid orphan entries.

Trialworks FileIT document records contain file paths on the firm's local or network drive. We migrate these as SharePoint document location records pointing to the original file server UNC path, and as Dynamics 365 Notes annotations containing the original file name, extension, and path. Actual file bytes are not moved unless the firm uses SharePoint Online for document storage.

Trialworks calendar events — including hearing dates, deposition schedules, and filing deadlines — map to Dynamics 365 Sales Appointment records (activity entity). Original event date/time, duration, and description are preserved. The related Matter lookup links each appointment to the corresponding tw_Matter__c record.

Trialworks billable time entries are aggregated by matter. We sum hours and amounts per matter and write them to two custom decimal/currency columns on tw_Matter__c: tw_TotalBillableHours__c and tw_TotalBillableAmount__c. Individual line-item time entries are preserved as custom activity records linked to the matter.

Trialworks staff records map to Dynamics 365 Sales SystemUser records. Resolution is by email match. Unmatched staff are flagged before migration — the firm either creates their Dynamics 365 Sales user account first or assigns their records to a fallback user. Security roles are assigned post-migration.

Trialworks task records are migrated as Dynamics 365 Sales Task activity records, preserving the subject, description, due date, priority, and status fields. The regarding_objectid field ties each task to its parent tw_Matter__c record or Contact record, maintaining the contextual relationship. Any associated notes or file references from Trialworks are imported as annotations on the task, ensuring that additional context is available to users without requiring the original system.

Any user-defined custom fields configured in Trialworks on the matter record are migrated as custom columns on the tw_Matter__c table. We infer the data type from Trialworks schema (text, number, date, pick-list) and create the equivalent Dataverse column type. Pick-list values require manual value-mapping setup.

Trialworks document generation templates (merge fields for letters, contracts, discovery documents) have no equivalent in Dynamics 365 Sales. We export the template field list as a PDF reference document for the firm's Dynamics 365 admin to use when rebuilding templates in Microsoft Word Mail Merge or a Power Automate document-generation flow.

Matter-opening workflows and procedural templates from Trialworks do not migrate. We provide a structured workflow audit export — listing each trigger, condition, and action — that the firm's Power Platform admin uses to rebuild equivalent Cloud Flows in Dynamics 365 Sales.