Migrate from My Legal Software to Microsoft Dynamics 365 Sales

My Legal Software Client records map directly to Dynamics 365 Account. Client name, address, phone, email, and primary contact details translate field-for-field. Multi-contact clients get additional Contact records linked via Account. Primary attorney or responsible party stored as OwnerId resolved by email match.

Individual attorney contacts, paralegal contacts, and client representatives map to Dynamics 365 Contact records. Each Contact links to the parent Account via AccountId lookup. Primary attorney flag, bar number, and specialization details translate to custom fields such as Is_Primary_Attorney__c boolean, Bar_Number__c text, and Practice_Specialization__c picklist on the Contact record. Multiple attorneys per client create separate Contact records all linked to the same Account.

My Legal Software Matters become Dynamics 365 Opportunities. Matter name maps to Opportunity Name. Matter number stored as custom Matter_Number__c field for reference. Each Matter's status (Active, Pending, Closed) maps to a corresponding Opportunity Stage. Multiple Matters per Client create multiple Opportunity records linked to the same Account.

My Legal Software practice area categories (Family Law, Corporate, Litigation, Real Estate, etc.) map to a custom Opportunity Type picklist in Dynamics 365. Each unique practice area value requires a corresponding picklist value created in the destination org before migration runs.

Time entries in My Legal Software map to Dynamics 365 Task records. Task.Subject captures the billing description. Task.ActualDuration maps from hours logged. Task.OwnerId resolves by email to the Dynamics user who performed the work. Billable vs non-billable flag stored as a custom Billable__c field.

Bills and invoices from My Legal Software translate to custom Invoice__c table records in Dynamics 365 because Dynamics 365 Sales lacks native billing and invoicing functionality. The custom Invoice__c table includes Invoice_Number__c, Invoice_Date__c, Due_Date__c, Amount__c, Tax_Amount__c, and Status__c fields, all linked to the parent Opportunity representing the Matter. Invoice line items map to separate Invoice_Line_Item__c records for detailed billing breakdowns.

Trust account balances and retainer records have no Dynamics 365 native equivalent. We create a custom Trust_Account__c table with Balance__c, Retainer_Amount__c, and Last_Reconcile_Date__c fields linked to the Account. Individual trust transactions map to Trust_Transaction__c records with Amount__c, Type__c (Deposit/Withdrawal), and Matter__c lookup.

My Legal Software documents attached to Matters re-upload to SharePoint Online using the built-in Dynamics 365 — SharePoint integration. Document metadata (document name, Matter reference, created date) stored as SharePoint document library columns. File size limits of 100 MB per file apply.

My Legal Software court deadlines, filing deadlines, and calendared events map to Dynamics 365 Task records with Task.ScheduledEnd set to the deadline date. Court deadlines include the opposing party deadline and internal preparation cutoff stored as custom fields. Recurring deadlines such as monthly compliance reports and annual renewals generate individual Task records per occurrence. Task.Priority maps directly from urgency level (High/Medium/Low) in the source system.

All firm-defined custom fields in My Legal Software become Dataverse custom columns with new_ prefix. Field data type is preserved (text, number, date, picklist). Picklist values require corresponding option set values in Dynamics 365 before migration. Custom field relationships to Matters or Clients map via Dataverse lookups.

My Legal Software staff records resolve to Dynamics 365 SystemUser by email address match. Unmatched staff members are flagged as inactive users — your admin either creates their Dynamics account first or assigns their records to a fallback owner before migration commits. User roles and permissions are destination-side configuration.

My Legal Software case notes map to Dynamics 365 Annotation records (the modern notes entity). Note text, created date, and author resolve to the correct SystemUser. Rich-text formatting is preserved where the source API returns HTML content. Notes linked to specific Matters connect via the RegardingObjectId lookup pointing to the Opportunity record.