Migrate from FactBox to Microsoft Dynamics 365 Sales

FactBox matters translate to Dynamics 365 Opportunities representing the business value of each case or matter. Matter name maps to Opportunity Name, matter description becomes the Opportunity Description field, and matter create date is preserved in a custom Created_Original__c datetime field since Dynamics sets CreatedDate at migration time.

FactBox parties (plaintiffs, defendants, witnesses, other contacts) map to Contact records with Account linkage. Multiple party roles per person collapse to primary Contact with role designation stored in a custom Role__c pick-list field. Each party's contact details (name, email, phone, address) map directly to standard Contact fields.

FactBox party roles (Plaintiff, Defendant, Witness, Expert, Other) map to a custom pick-list field on Contact. Each role value is mapped value-by-value so your Dynamics admin can filter contacts by role in views and reports. Role-based filtering replaces the role-based filtering available in FactBox.

FactBox facts — dated entries with descriptions and source-document links — do not have a native Dynamics 365 equivalent. We create a custom FactEntry__c Dataverse table with fields for FactDate, Description, SourceDocumentUrl, and linked ContactId. Alternatively, for simpler migrations, facts map to Notes on the Opportunity record with formatted body text.

FactBox documents linked to facts must be downloaded and re-uploaded to Dynamics 365 SharePoint or Dataverse file storage. We preserve the original file name, upload to a SharePoint folder structure mirroring the matter hierarchy, and store the SharePoint URL in a custom DocumentUrl__c field on the related FactEntry record.

Dynamics 365 sets Opportunity CreatedDate at the time of migration, overwriting the original matter creation timestamp. To preserve historical data integrity, we store the original FactBox matter creation date in a custom Created_Original__c datetime field. This custom field maintains reporting continuity, enables historical matter age calculations, and supports time-based analysis in Dynamics 365 reports and dashboards.

FactBox matter statuses (Active, Pending, Closed, Archived) map to Dynamics 365 Opportunity StateCode and StatusCode values. Active matters map to Open state; Closed matters map to Closed/Won or Closed/Lost based on outcome field. Custom status values require value-by-value mapping during schema setup.

FactBox custom fields per matter type (e.g., Court_Name__c, Case_Number__c, Statute_of_Limitations__c) require corresponding custom columns in Dataverse. We create each custom column with the appropriate data type (text, date, number, picklist) and map values during migration. Type conversion is applied where FactBox field types differ from Dataverse equivalents.

FactBox matter owners are matched to Dynamics 365 users by email address. Unmatched owners are flagged before migration — your team either creates Dynamics user accounts or assigns records to a fallback owner. No record lands without a valid OwnerId in Dynamics 365.

FactBox timeline events (depositions, hearings, filings) map to Dynamics 365 Tasks or Appointments depending on duration. Event subject maps to Task Subject or Appointment Subject, event date maps to ScheduledStart, and description maps to Task Description. Owner resolution follows the same email-match logic applied to matter owners.

FactBox notes and comments attached to matters or parties map directly to Dynamics 365 Annotations (Notes) on the corresponding records. Original create timestamps from FactBox are preserved in a custom Created_Original__c datetime field on the Annotation record to maintain audit trails. Rich-text formatting including bold, italics, and lists is converted to Dynamics 365-supported HTML markup to preserve visual structure in the destination system.