Migrate from Aderant Milana to Microsoft Dynamics 365 Sales

Milana Matter records map to a custom Dataverse table Milana_Matter__c. Fields include matter title, matter number, status, practice area, and the original Milana matter ID stored as Milana_Matter_ID__c for traceability. Dynamics 365 Sales Enterprise allows unlimited custom tables; Professional tier is capped at 15 tables, which may require custom-field consolidation for Milana matters.

Milana Party records split into Dynamics 365 Contact (for individual persons: clients, attorneys, witnesses) and Account (for organizations: law firms, opposing parties, courts). The Milana_Party__c custom table stores the party role (Client, Opposing Counsel, Expert, etc.) and the N:N link back to Milana_Matter__c, since Dynamics 365 native Account-Contact relationships don't natively carry role semantics.

Milana party role values (Client, Opposing Counsel, Co-Counsel, Expert Witness, Court, Mediator, etc.) are mapped to a custom picklist Milana_Party_Role__c on the Milana_Party__c junction table. Each role type is preserved value-by-value; if a role has no Dynamics 365 equivalent, it is stored as a custom picklist value for reference.

Milana attorney and staff assignments on matters map to Dynamics 365 User records (OwnerId on the Milana_Matter__c record) plus a Milana_Attorney__c custom table storing the attorney role type (Lead Counsel, Associate, Paralegal, Billing Attorney) and matter-specific billing codes. Owner resolution happens by email match.

Milana's embedded court rules (CompuLaw-sourced jurisdiction rules) are extracted as read-only records in a Milana_CourtRule__c custom table. Fields include jurisdiction, rule set name, rule version, and effective date. This preserves the source rule context for deadline re-calculation in Power Automate post-migration.

Milana deadline records (calculated from filing dates + court rules) map to a Milana_Deadline__c custom table in Dynamics 365. Each deadline record stores the calculated due date, the triggering event (e.g., 'Answer Due', 'Discovery Cutoff'), the associated Milana_Matter__c link, and the Milana_CourtRule__c that generated it. Dynamics 365 Tasks are created for near-term deadlines to surface them in the Sales app.

Milana court event records (hearings, trials, depositions,filing submissions) map to a Milana_CourtEvent__c custom table linked to Milana_Matter__c. Fields include event type, court name, judge, courtroom, event date, and the associated Milana_CourtRule__c. Dynamics 365 doesn't natively model court events; this custom table preserves the full event context.

Milana documents linked to matters are downloaded and re-hosted in SharePoint Online (via the native Dynamics 365 + SharePoint integration). A Milana_Document__c custom table stores the document name, Milana file reference, SharePoint URL, and version history. File size limits apply: Dynamics 365 file fields cap at 128 MB per file; SharePoint handles larger documents natively.

Milana billing records link to Aderant Expert for time tracking and invoicing. There is no direct Dynamics 365 equivalent. We store the billing reference ID and matter linkage in a Milana_Billing__c custom table and recommend a Dynamics 365 Business Central integration for full billing continuity. The financial data itself does not migrate as CRM records.

Milana user accounts are mapped to Dynamics 365 Users by email address. Unmatched users are flagged before migration; the firm must create their Dynamics 365 accounts first or assign records to a fallback owner. Milana user roles and permissions do not migrate — those are destination-side security role configurations.