Migrate from Legal Case Tracker to Microsoft Dynamics 365 Sales

Legal matters map to Dynamics 365 Case if your firm uses service-style tracking, or to a custom Dataverse table (new_matter) for matter-centric workflows. We create the custom table with the required columns before migration runs. Matter status values map via value_mapping to Dynamics Case StateCode/StatusCode.

Direct map. Each Legal Case Tracker contact becomes a Dynamics 365 Contact. The Contact's primary AccountId resolves from Legal Case Tracker's client link. Unlinked contacts create as standalone Contacts with no AccountId. During migration we verify that the email address on each contact is unique; duplicates are flagged for manual merge or conversion to a different record type. The AccountId lookup is case‑insensitive, ensuring consistent matching even if capitalization differs.

Direct map. Legal Case Tracker clients with company type map to Dynamics 365 Account. Sole practitioner clients without a company create as Accounts with the contact name in the Account Name field. We also map the client’s address, phone, and website fields to the corresponding Account fields, preserving all contact details for downstream sales and service processes.

Documents migrate to SharePoint document locations linked to the target Matter (custom table) record. File content re-uploads to SharePoint; original filenames and create dates preserved. Inline email attachments from Outlook integration become Dataverse Annotation records. If your SharePoint library uses content types or metadata columns, we map those to the document location’s additional properties, ensuring that classification and retention policies carry over without manual re‑tagging.

Direct map. Legal Case Tracker tasks with due dates and owners map to Dynamics 365 Tasks. Task priority values map via value_mapping to Dynamics PriorityCode (low=0, normal=1, high=2). Open tasks land as Open tasks; completed tasks retain completed status. We also preserve the original task description and any linked notes, and we map the task’s regarding object to the appropriate matter or contact record to maintain context.

Direct map. Legal Case Tracker calendar events with start/end times migrate as Dynamics 365 Appointments. The regarding_objectid links to the target Matter or Contact record. All-day events preserve the IsAllDayEvent flag. We also map the location field and any recurrence patterns, converting them to the corresponding Dynamics recurrence schema so that recurring hearings or deadlines are replicated accurately.

Dynamics 365 has no native time-tracking entity. We create a custom Dataverse table (new_timeentry) with fields for hours, date, description, billable flag, and regarding lookup to the Matter record. Original time-entry dates and staff assignments preserved. The custom table also includes a lookup to the staff member’s SystemUser record, ensuring that each time entry is tied to the correct attorney or paralegal for billing and utilization reports.

Legal Case Tracker expense records require a custom Dataverse table (new_expense) because Dynamics 365 lacks native expense tracking. Fields include amount, date, category, receipt attachment, and regarding lookup to the Matter record. We also map the vendor name and currency code to the corresponding fields, and we preserve the original receipt file as a SharePoint document or Annotation, linked to the expense entry for audit trails.

Legal Case Tracker staff records resolve to Dynamics 365 SystemUser by email match. Unmatched staff are flagged before migration; you either invite them to Dynamics 365 first or assign their records to a fallback owner. Primary role and department map as custom fields on SystemUser.

Legal Case Tracker custom fields on any object become Dataverse custom columns on the target table. Data type mapping applies: text fields become nvarchar, number fields become integer or decimal, date fields become datetime2. Pick-list values require value_mapping per option set.

Legal Case Tracker supports N:1 and N:N contact-to-matter relationships. In Dynamics 365, the primary contact gets a lookup field on the Matter table. Additional contacts require either a custom junction table (new_mattercontact) or the native Contact entity's regarding lookup, depending on the relationship type.

Legal Case Tracker email integrations that attach Outlook emails to matters do not have a direct Dynamics 365 equivalent. We export the email metadata and body as Annotation records or SharePoint documents so the communication history is preserved, though the native Outlook link does not transfer.