Migrate from MyCase to Microsoft Dynamics 365 Sales

MyCase contacts (individuals at client firms) map directly to Dynamics 365 Sales Contact records. Each contact requires an AccountId lookup — the client company must be migrated first so the AccountId foreign key resolves at insert time. We also preserve the original MyCase contact ID in a custom Source_System_ID__c field for subsequent reconciliation.

MyCase company records (the client organization) map to Dynamics 365 Sales Account. Billing address, industry, and number of employees transfer as direct fields. Parent-company hierarchies in MyCase map to Account.ParentAccountId. We retain the original MyCase company identifier in new_companyid for traceability and delta re-sync.

MyCase matters carry legal context — practice area, billing type, court information — that has no direct Dynamics 365 Sales equivalent. We map the matter name to Opportunity.Name, estimated value to Amount, and stage to a legal-specific opportunity stage value-map. Legal context fields become custom columns on the Opportunity table.

MyCase time entries (attorney hours, rates, task descriptions) cannot be stored as native Dynamics 365 Sales activities because the platform lacks a billing engine. We create custom decimal and text columns on the Opportunity to hold total billed hours, blended rate, and a JSON-encoded time-entry log for audit purposes.

MyCase invoices and outstanding balances have no Dynamics 365 Sales counterpart. We preserve invoice status, outstanding amount, and last-invoice date as custom fields on the Opportunity or Account. Firms that need billing continuity route this data to Dynamics 365 Business Central separately.

MyCase Advanced-tier custom fields on matters require new_ prefixed columns on the Opportunity table in Dynamics 365 Dataverse. Pick-list fields undergo value-by-value mapping; text fields map directly. We create the columns during the pre-migration schema build and validate with a sample run.

MyCase custom properties on contacts — intake sources, referral channels, billing contact flags — become new_ prefixed custom columns on the Contact table. We extract the full custom-field schema from MyCase during discovery and pre-create every target column in Dataverse.

MyCase documents attached to matters are downloaded and re-uploaded to the SharePoint or OneDrive location that Dataverse manages for the Account or Opportunity. We preserve the original folder path hierarchy and file names. Inline images in notes are downloaded and rehosted in the Dynamics 365 document storage.

MyCase calendar events (court dates, depositions, deadlines) and tasks map to Dynamics 365 Sales Task and Appointment entities. Original start/end times, assigned attorney or staff user, and parent record links are preserved. Task priority and status map value-by-value. We also keep the MyCase event ID in new_eventid for future reference and audit trails.

MyCase users (attorneys, paralegals, staff) are resolved against Dynamics 365 Sales SystemUser records by email address match. Unmatched users are flagged before migration so the firm can invite them to Dynamics 365 or assign a fallback owner before records land.

MyCase workflow tasks, automated deadline triggers, and intake form logic have no Dynamics 365 Sales equivalent. We export workflow definitions as a structured reference document and deliver template assets so your Dynamics admin can rebuild them in Power Automate and Dynamics 365 Sales automated flows.

MyCase Advanced Document Automation templates and clause library are Word-based assets tied to MyCase's ADA add-in. We export the template files and field-mapping documents so they can be uploaded to Dynamics 365 Sales document templates or Power Automate document-generation flows.