Migrate from The Plaintiff to Microsoft Dynamics 365 Sales

The Plaintiff contact records map directly to the Dynamics 365 Contact table. The primary email address becomes Contact.Email, phone becomes Phone, and the name fields map to FirstName and LastName. Ownership is resolved by email match against existing Dynamics 365 users.

The Plaintiff firm or company name maps to the Account.Name column in Dynamics 365. Website URL maps to Account.Website. Industry values from The Plaintiff are mapped value-by-value to the Account.Industry pick-list. Employee count and revenue figures map to NumberOfEmployees and AnnualRevenue respectively.

Contacts in The Plaintiff flagged as prospective clients (status not yet a matter) route to the Dynamics 365 Lead table. Prospective contacts retain the source contact ID in a custom External_Source_ID__c field for traceability and later conversion to Contact, Account, and Opportunity records during the sales lifecycle stages in Dynamics 365 Sales.

Active matters in The Plaintiff become Opportunities in Dynamics 365 Sales. The case name maps to Opportunity.Name, case value or billing amount maps to Amount, and the case open date maps to CloseDate. Case status maps to a custom Opportunity_Status__c pick-list; stage assignment follows the default Dynamics Sales Process.

If the destination is Dynamics 365 Sales Enterprise, The Plaintiff cases can map to the native Incident (Case) table. This requires custom column creation for fields specific to the legal matter (e.g., Matter_Type__c, Referring_Attorney__c) and Field-Level Security configuration per Business Unit.

All logged calls, emails, and meetings in The Plaintiff map to the Dynamics 365 ActivityPointer table with the specific type set. Original timestamps, owner (resolved by email), and regarding object (parent Contact or Case) are preserved. Attachments are downloaded and re-uploaded to Dynamics 365 Notes or SharePoint document location.

Documents attached to The Plaintiff cases or contacts are extracted and attached to the corresponding Dynamics 365 record via the Annotation (Notes) entity or uploaded to the associated SharePoint document location configured on the Account or Contact, preserving the original file structure and attachment relationships for downstream retrieval and compliance requirements.

Each custom property The Plaintiff stores on contacts requires a new_ prefixed custom column on the Contact table in Dataverse. We match the data type (text, number, pick-list, date) and create the column before migration. Pick-list custom properties require a new_ pick-list with matching values.

Case-specific custom properties migrate to custom columns on the Opportunity or Incident table depending on the chosen mapping strategy. All new_ columns are published before the migration run. If the source custom property uses a pick-list, we build a corresponding Dynamics 365 pick-list with identical values.

The Plaintiff user records are matched to Dynamics 365 SystemUser by email address. Unmatched users are flagged as warnings — the migration plan requires either inviting them to Dynamics 365 first or assigning their records to a fallback owner before migration commits.