Migrate from Case UI to Microsoft Dynamics 365 Sales

Direct one-to-one mapping. Dynamics 365 requires an AccountId lookup on Contact; Case UI contacts without a primary client association are attached to a default 'Unassigned Account' record or held as standalone Contacts pending a client assignment decision. The new_SourceContactID__c field preserves the original Case UI contact identifier for delta-run de-duplication after migration.

Direct mapping of Case UI clients to Dynamics 365 Account records. Case UI clients store company name, address, industry tags, and billing address, which map to Account.Name, Address fields, Industry, and BillingAddress respectively. Multi-contact clients in Case UI consolidate into one primary Account record per client to maintain a clean Account hierarchy in Dynamics 365.

No native Case entity exists in Dynamics 365 Sales standalone. We create a new_Case custom table with fields for case number, title, status, priority, responsible attorney, opposing counsel, court/jurisdiction, practice area, billing rate, and client reference. new_Case requires pre-migration setup in your Dynamics 365 environment.

Case UI documents attached to cases are exported as files and re-uploaded to SharePoint via Dynamics 365's native SharePoint integration. A new_DocumentReference custom table stores the original Case UI document ID, file name, and SharePoint URL for traceability and future reference linking back to the source matter.

Emails logged in Case UI map to Dynamics 365 Email (email) activities with the original Subject, Description, and timestamp preserved. Owner resolved by email match against Dynamics 365 users. The new_SourceEmailID__c field preserves the original Case UI email identifier for delta-run de-duplication after migration.

Case UI call logs map to Dynamics 365 PhoneCall activities; meetings and hearings map to Appointment entities with original start/end times, location (courtroom or client office), and attendees preserved. The new_SourceActivityID__c field preserves the original Case UI activity identifier for delta-run de-duplication after migration.

Case UI task items map to Dynamics 365 Tasks with Subject, Description, Due Date, Priority, and Status fields preserved. Open and completed states map directly to Dynamics 365 Task status values. The new_SourceTaskID__c field preserves the original Case UI task identifier for delta-run de-duplication after migration.

Billable hours logged in Case UI migrate as records in a new_TimeEntry custom table linked to new_Case and Contact. Fields include date, hours, billing rate, description, and billable flag. Your admin sets up the relationship in Dynamics 365 before migration.

Case UI expense entries migrate as new_Expense records linked to new_Case. Fields include date, category, amount, description, and receipt reference. Dynamics 365 Sales does not have a native expense entity; this requires a custom table that your admin creates in Power Apps before migration begins.

Invoice history from Case UI migrates as new_Invoice records linked to Account and new_Case. Dynamics 365 Sales Professional does not include invoice management; Enterprise or a separate Business Central instance handles this natively. We preserve invoice data as reference records for continuity.

Court hearings and client appointments in Case UI map to Dynamics 365 Appointments with the original start/end datetime, location (courtroom or office address), and case reference preserved. Recurring hearing schedules are flattened to individual Appointment records to maintain historical accuracy.

Case UI allows labeling contacts with roles on a case (e.g., Expert Witness, Opposing Counsel). Dynamics 365 Contact has no native role-per-case field. We create a new_ContactCaseRole custom field on the Contact or new_Case table to preserve this association for each matter.

Referral source tracking in Case UI (e.g., client referral, court referral) has no direct Dynamics 365 equivalent. We migrate referral sources as Lead records or as a new_ReferralSource custom pick-list field on Account for reporting purposes and downstream analytics.

Client trust account balances from Case UI migrate as new_TrustBalance records linked to Account. Dynamics 365 Sales does not have a native trust accounting entity; this requires a custom table and is handled as a reference record for reconciliation against your accounting software.

Case UI staff members and attorneys map to Dynamics 365 SystemUser records resolved by email match. Unmatched Case UI owners are flagged before migration and assigned to a fallback user or held in a staging queue for your admin to reconcile.