Migrate from Legistify to Microsoft Dynamics 365 Sales

Legistify matters map to Dynamics 365 Incidents (cases). Matter name becomes Incident Subject; priority and stage become custom pick-list fields on the Incident entity. Court name, judge, and filing date are stored as custom text or datetime fields on the incident since Dynamics does not have a native legal court schema.

Legistify matter statuses (Active, Pending, Closed) are mapped value-by-value to Dynamics Incident StatusCode options (Active = 0, On Hold = 1, Resolved = 5, Cancelled = 6). Mapping is reviewed against the Dynamics organization's status option set before migration runs to avoid invalid status values.

Legistify contracts map 1:1 to Dynamics 365 Opportunities. Contract amount migrates to Opportunity EstimatedValue; contract close date migrates to Opportunity ActualClosedate. The opportunity name uses the contract title. A custom field Legistify_Contract_ID__c preserves the original Legistify contract identifier for traceability.

Contract monetary values transfer directly to the EstimatedValue field on Opportunity. Currency is preserved where available; Dynamics uses the organization's base currency where the source currency is not specified. Exchange-rate conversion is not applied — amounts land as stated in Legistify.

Legistify clients are legal entities (companies, law firms, opposing parties) and map to Dynamics 365 Accounts. Client name becomes Account Name. Client type (Law Firm, Corporate, Government) maps to a custom pick-list field on Account since Dynamics does not have a native client-type attribute.

Legistify contacts associated with clients map directly to Dynamics 365 Contacts. The primary account link is established via AccountId lookup after the Account record exists. For contacts without a client assignment, a placeholder 'Unassigned Account' record is created in Dynamics.

Legistify user records are resolved by email match against Dynamics 365 SystemUser entities. Matched users are assigned as incident owners and opportunity owners. Unmatched users are flagged before migration; the team either creates the user in Dynamics first or assigns records to a fallback owner designated by the administrator.

Legistify calendar entries and court date reminders migrate as Dynamics 365 Tasks. The subject line becomes Task Subject; the due date maps to Task ScheduledEnd. Original timestamps are retained in a custom datetime field, and the original reminder text is saved in the Task Description. Recurring calendar entries are expanded into individual task records, each linked to the related Incident via RegardingObjectId.

Legistify notes attached to matters or contracts migrate as Dynamics 365 Annotations (Notes). The note body populates the Annotation Body field, while the original creation timestamp is stored in a custom datetime field for audit continuity. The parent object ID (RegardingObjectId) links each annotation to the appropriate Incident or Opportunity, ensuring the note appears in context. If the note includes file attachments, those files are handled via the document migration pipeline.

Legistify document attachments are downloaded from the source platform's storage and re-uploaded to the SharePoint or OneDrive location connected to the parent Dynamics record (Incident or Opportunity). File metadata (filename, original upload date) is preserved in the SharePoint document library. Dynamics file size limits (25 MB default) are enforced during upload.

Legistify custom properties on matters (e.g., judge name, opposing counsel, case type, statute of limitations) require pre-created custom fields on the Dynamics Incident entity. We deliver a custom field manifest as part of the pre-migration schema plan so your Dynamics administrator can create the fields before data lands.

Legistify workflow rules, escalation triggers, and notification automations have no native equivalent in Dynamics 365. These must be rebuilt in Power Automate post-migration. We export Legistify automation definitions as a structured JSON reference so your Dynamics administrator has a rebuild guide.