Migrate from eBrief Ready to Microsoft Dynamics 365 Sales

eBrief Ready parties (barristers, solicitors, expert witnesses, clients) map to Dynamics 365 Contacts. Each party's name, email, phone, and firm affiliation maps to the corresponding Contact fields. Parties without email are flagged for manual review before migration. The migration also preserves the original party ID from eBrief Ready as a custom field for traceability and audit purposes.

eBrief Ready assigns roles per party within a matter (Barrister, Instructing Solicitor, Expert Witness, Client). These become a custom picklist field Party_Role__c on the Contact record. Role values are mapped one-to-one; unrecognized roles become 'Other' with the original value preserved.

eBrief Ready matters do not map to a native Dynamics object. We create a custom Dataverse table Matter__c linked to the Account record, storing matter number, case title, court, jurisdiction, matter status, and open/close dates. The Account record represents the client firm; the Matter__c record represents the legal matter.

eBrief Ready folders (Correspondence, Pleadings, Evidence, Chronology) are recreated as SharePoint document libraries linked to the Matter__c record via Dataverse SharePoint integration. The folder hierarchy is preserved in SharePoint; a Note record in Dataverse holds the mapping reference. This approach ensures that document organization remains intact and users can navigate the migrated files using the familiar folder structure they established in eBrief Ready.

Each eBrief Ready document migrates as a file in the associated SharePoint library. The original document name, upload timestamp, and uploader are stored as file metadata. Documents with eBrief Ready annotations generate a Note record with the annotation text, linked to the SharePoint file.

eBrief Ready annotations (highlights, tags, comments) migrate as Dataverse Notes attached to the SharePoint file record. The annotation author, creation date, and highlight text are preserved. Rich-text formatting is converted to HTML within the Note body. A custom field on the Note record tracks the original eBrief Ready annotation ID, enabling traceability back to the source system.

eBrief Ready chronology tool entries (date, description, document reference) migrate to a custom Dataverse table Chronology_Entry__c linked to the Matter__c record. Each entry's date, description, and source document link are stored as columns. Chronology is not a native Dynamics object and requires custom table creation.

eBrief Ready tags (e.g., privilege, hearsay, exhibit, key-finding) migrate to a custom multi-select option set Tag__c on the Matter__c record if fewer than 20 unique tags exist. For taxonomies exceeding 20 values, tags migrate as a text field with pipe-delimited values for reference.

eBrief Ready matter statuses (Active, Pending Review, Filed, Closed, Archived) map to a custom option set on the Matter__c record. Closed-date and closure-reason fields are added to track when the matter was archived in eBrief Ready. This mapping preserves the full lifecycle of each matter, allowing Dynamics users to understand the historical status progression without accessing the legacy system.

eBrief Ready AI-generated bank statement summaries have no Dynamics 365 equivalent. The analysis output is exported as a Note attached to the Matter__c record with a 'AI_Analysis' type flag for reference. The underlying transaction data remains in the document. This preserves the AI-generated insights while keeping the source data accessible in SharePoint for manual review or re-analysis using Azure AI services.

eBrief Ready AI document classification (suggested folder, document name, date) is a platform-specific automation with no Dynamics 365 equivalent. The classification output is not migratable; documents are re-classified after migration using Power Automate or manual review. We recommend documenting your classification rules and folder placement patterns during discovery so your team can recreate similar workflows in Power Automate or apply them manually during the initial organization phase.

eBrief Ready workflows, AI Smart Classification rules, and automated chronology triggers do not map to Dynamics 365. We export the workflow definitions as a JSON reference file for your admin to rebuild in Power Automate or as Dataverse plug-in steps.