Migrate from Thomson Reuters Case Center to Microsoft Dynamics 365 Sales

Case Center Case records become a custom Case table in Dynamics 365 Dataverse. The Case table requires a custom schema since Dynamics 365 has no native Case object beyond the service-level Cases entity. We create CaseNumber, CaseTitle, CaseType, FiledDate, CourtName, and CaseStatus fields on the custom entity. Case-party relationships are established via a lookup from the custom Case table to the Contact record.

Case Center Parties (plaintiffs, defendants, witnesses, experts) map to Dynamics 365 Contacts. Each party role is stored in a custom PartyRole pick-list field on the Contact (e.g., Plaintiff, Defendant, Witness, Expert Witness). We map the party's name, firm/organization, email, phone, and address fields directly to Contact standard fields. Related-party organizations map to Account records with a Contact-to-Account lookup.

When a Case Center party is an organization (e.g., corporate defendant, government agency), we map to Dynamics 365 Account. Account stores the organization name, website, address, industry, and employee count. The Contact record links to Account via the Parent Customer ID lookup. Party-specific metadata (e.g., party type, insurance carrier) is stored in custom fields on the Account.

Case Center exhibits (documents, images, multimedia) migrate as Dynamics 365 Notes (Annotation entity). Each exhibit retains its exhibit number, title, description, and original upload timestamp. The Note is linked to the parent Case record via the RegardingObjectId lookup. File content is re-uploaded to Dynamics 365/SharePoint; inline annotations and redactions are preserved as Note text content or attachments.

Case Center hearing records become Dynamics 365 Appointments or custom Hearing activities. We map hearing date, start time, end time, hearing type (e.g., Motion, Trial, Status Conference), virtual/in-person flag, and court location. The activity is linked to the parent Case record. Judge name and courtroom are stored in custom fields since Dynamics 365 Appointments have no native hearing-specific fields.

Case Center annotations (court clerk notes, judge remarks, party correspondence logged in the case file) migrate to Dynamics 365 Notes attached to the parent Case or Contact record. Original annotation author and timestamp are preserved in the Note's CreatedBy and CreatedOn fields. Rich-text formatting is converted to plain text or HTML depending on Dynamics 365 version.

Any custom fields configured in the Thomson Reuters Case Center account (e.g., Case Jurisdiction, Practice Area, Assigned Judge, Case Status Reason) map to custom columns on the Case table in Dataverse. Custom fields follow Dynamics 365 naming conventions — alphanumeric Column names without spaces. We create the fields in the Dataverse schema before migration and map values field-by-field.

Case Center user accounts (court staff, attorneys, judges, litigants) are mapped to Dynamics 365 SystemUser records by email address match. Permissions and access roles do not migrate — Dynamics 365 security roles and team membership are configured post-migration based on your security model. We flag any Case Center users without email matches before migration so you can decide whether to invite them to Dynamics.

Case Center organizes exhibits in folder hierarchies. We reconstruct these as SharePoint Document Locations linked to the Dynamics 365 Case record. The folder structure (top-level: Case Number, sub-levels: Exhibit Type, Filing Date) is preserved in SharePoint. Dynamics 365 maintains a pointer to each SharePoint location via the DocumentLocation entity.

Case Center evidence-to-exhibit cross-references and hyperlink relationships require a custom junction table in Dynamics 365. For example, if Exhibit A references Exhibit B via a footnote, we create a custom EvidenceReference junction entity with SourceExhibitId and TargetExhibitId lookups to the Note entity. This preserves the evidentiary relationship graph without relying on Dynamics 365's flat note structure.

Case Center hearing reminder notifications, exhibit deadline alerts, and filing deadline workflows do not have a Dynamics 365 equivalent. These must be rebuilt as Power Automate flows or Dynamics 365 workflows post-migration. We export the workflow definitions from Case Center as a reference document so your admin can map each trigger and action to the Power Platform equivalent.

Case Center tracks case billing status and legal hold flags. These map to custom pick-list fields on the Case table (BillingStatus__c, LegalHold__c). Dynamics 365 has no native billing or litigation-hold concept — these are operational flags maintained in custom fields for reporting and compliance tracking.