Migrate from Criminal Case Management to Microsoft Dynamics 365 Sales

Criminal cases map directly to Dynamics 365 Sales Case table or a custom Case__c table depending on jurisdiction workflow complexity. Original case number, filing date, jurisdiction, and case type transfer as custom fields. Standard Dynamics 365 Case status field handles minor statuses; major case-stage transitions (Investigation, Arraignment, Trial) require custom pick-list.

Defendants are Contact records in Dynamics 365 Sales with a custom Case_Role__c pick-list set to 'Defendant'. Criminal identification fields (DOB, SID number, FBI number) migrate as custom fields on Contact. If the source stores aliases or prior names, these append to a custom Aliases__c text field. Multiple aliases from source collapse into semicolon-delimited string.

Victims migrate as Contact records with Case_Role__c = 'Victim'. Contact protection status from source maps to a custom Is_Protected__c boolean field. Victim contact information is fully preserved; restraining order data migrates to a custom Restraining_Order__c pick-list if the source distinguishes order types.

Witnesses map to Contact records with Case_Role__c = 'Witness'. Witness contact details, testimony status, and subpoena records migrate as related sub-records. If the source stores witness statement dates, availability windows, and special accommodations (interpreter needs, security concerns), these transfer as custom fields on the Contact record. Witness availability windows and any special accommodations such as interpreter needs or security concerns transfer as custom fields on the Contact.

Legal counsel (defense and prosecution) migrate as Contact records with Case_Role__c = 'Defense Attorney' or 'Prosecutor'. Bar number, firm affiliation, and appointment type (court-appointed vs. retained) migrate as custom fields. Attorney contact records link to Cases via custom junction table or Case_Role__c on Contact.

Charges require a custom Charge__c table in Dynamics 365 Sales because standard Dynamics 365 tables do not have charge-specific fields. Each Charge__c record links to the parent Case via a Lookup field (Case__c). Statute code, charge description, severity (felony/misdemeanor), and classification (person crime, property crime, drug offense) map to custom pick-list and text fields on Charge__c.

Evidence items require a custom Evidence__c table to track item description, evidence type (physical, digital, documentary), custody chain timestamps, storage location, and chain-of-custody transitions. Each custody transfer (seizure, lab submission, court exhibit) becomes a Custody_Event__c related record. For large evidence volumes, evidence metadata migrates to Dynamics 365 with document files stored in SharePoint and linked via URL field.

Court appearances require a custom Court_Date__c table to store hearing type, scheduled date and time, courtroom location, judge name, and outcome. If source distinguishes between arraignment, preliminary hearing, motion hearing, and trial settings, each becomes a record type or custom pick-list value on Court_Date__c. Outcome data (continuance, plea entered, verdict) migrates to an Outcome__c pick-list field.

Case documents (motions, filings, discovery) migrate to SharePoint with a custom Document__c metadata table in Dynamics 365. Document type (motion, police report, exhibit, correspondence), filing date, and author link to custom fields. Dynamics 365 SharePoint integration requires site and library configuration before migration; FlitStack AI maps document URLs from source to destination SharePoint paths.

Case notes, investigator activities, and attorney work product migrate as Dynamics 365 Notes or Activities depending on type. Phone calls, emails, and meetings map to standard Activity records (Task or Appointment). Free-form case notes map to Note records. Original timestamps, authors, and parent Case lookup transfer via custom fields if Dynamics 365 standard fields do not capture all metadata.

Source systems with many-to-many party-to-case relationships (one defendant on multiple cases, or multiple defendants on one case) require either a custom Case_Party__c junction table in Dynamics 365 or use of Contact.Case_Role__c for simple 1:N relationships. FlitStack AI analyzes the relationship cardinality in source and recommends the appropriate model before migration.

Probation conditions, supervision start/end dates, and compliance status require a custom Supervision__c table linked to the Case and Defendant Contact. Supervision officer, reporting schedule, and violation history migrate as custom fields. If the source has separate supervision case numbers, these transfer as separate Supervision__c records linked to the originating criminal case.