Migrate from LegalEdge to Microsoft Dynamics 365 Sales

Matter-to-Opportunity mapping requires a custom entity with no native Dynamics 365 equivalent

Dynamics 365 Sales has no built-in Matter or Case object — legal matters from LegalEdge must become a custom Matter__c entity built on Dataverse. Every matter-type category (litigation, corporate, real estate) that requires distinct stage values or form layouts needs its own record type on the Matter entity, which your Dynamics admin must pre-create before data lands. Without record types, all matter records share one pick-list set, losing the type-specific workflow logic your firm relies on. We deliver a Matter entity schema plan including record types, custom fields, and form assignments as part of the migration package so the Dynamics side is ready before the first record moves.

Billing records and invoices have no native Dynamics 365 Sales object and require a custom table

LegalEdge treats billing entries and invoices as first-class records with relationships to matters, attorneys, and clients. Dynamics 365 Sales has no native equivalent — there is no native invoice object, no time-tracking entity, and no billing ledger. Migrating these as-is requires a custom Billing_Line_Item__c table and Invoice__c table built in Dataverse before migration. If your firm needs to preserve historical billing data for reporting, the custom table schema must be defined upfront; otherwise, billing records can be exported as a CSV reference file for compliance purposes without occupying Dynamics schema real estate.

Document attachments require SharePoint re-upload and manual link restoration post-migration

LegalEdge stores documents within matter records using its own document management system. Dynamics 365 does not have a native document storage equivalent — files attach via SharePoint integration, which must be configured in your Dynamics environment before migration. We export LegalEdge file attachments and re-upload them to the appropriate SharePoint document library, but the link between the document record and the Matter record in Dynamics must be re-established manually after the migration or through a post-migration script. This step requires SharePoint admin access and typically adds 4–8 hours to the project timeline.

Power Platform API rate limits affect bulk migration throughput for large record sets

Dynamics 365 Sales uses Dataverse API with Power Platform request limits that vary by license tier. For migrations exceeding 100,000 records, bulk API throttling can extend migration clock time significantly if batch sizing is not tuned. We monitor request consumption during migration and adjust batch sizes dynamically; for enterprise-scale migrations we route writes through Azure Data Factory with Dataverse connector to stay within throttling tolerances. This is disclosed in the migration plan so your team can budget for extended cutover windows if your Dynamics license tier has lower request allocations.

LegalEdge workflows and matter automation must be rebuilt in Power Automate

LegalEdge workflows handling matter assignments, status-based routing, conflict checks, and deadline triggers do not export in any transferable format. Dynamics 365 Sales relies on Power Automate for workflow automation and model-driven app business rules for form-level behavior. We export your LegalEdge workflow definitions as text descriptions and trigger-condition logs so your Power Automate admin has a rebuild reference. Any automation that depends on LegalEdge-specific fields or matter-status logic will need those custom fields created first in Dynamics — we sequence the rebuild workstream to follow the custom schema step.