Migrate from Dibcase Legal Case Management to Microsoft Dynamics 365 Sales

Dibcase clients (SSA/VA claimants) map directly to Dynamics 365 Contacts. Dibcase stores first name, last name, email, phone, address, SSA claimant ID, and VA claim ID per client. The Dynamics Contact record holds standard fields; SSA/VA identifiers become custom fields (new_ssa_claim_number_c, new_va_claim_number_c). Dibcase practice-association (which firm the claimant is affiliated with) maps to AccountId on Contact.

If a Dibcase Client record has not yet been converted to an active SSA claim (status = 'Inquiry' or 'Lead' in Dibcase), it routes to a Dynamics 365 Lead record. SSA/VA identifiers are preserved as custom Lead fields. Once the SSA claim is filed in Dibcase, the Lead converts to a Contact with an associated Opportunity (case).

Dibcase practice entities (law firms, advocacy groups, SSA field offices) map to Dynamics 365 Accounts. Account Name, address, website, and industry map directly. Dibcase-specific firm identifiers (dibcase_practice_name, firm_tax_id) migrate as custom fields. Parent-firm hierarchies in Dibcase map to Account.ParentId in Dynamics.

Each Dibcase SSA/VA case maps to a Dynamics 365 Opportunity. Dibcase case_number maps to Opportunity.Name or a custom field (new_dibcase_case_number_c). Dibcase case_type (SSA Disability, VA Claim, Workers' Comp) maps to a custom pick-list field (new_case_type_c) on the Opportunity. Dibcase SSA-specific fields — claim number, disability onset date, hearing date, representative fee approved — map to custom Opportunity fields. The Opportunity's estimated close date corresponds to the Dibcase hearing date or projected decision date.

When Dibcase cases carry heavy SSA-specific metadata that does not fit cleanly on a standard Opportunity record, FlitStack AI recommends a custom 'Case' Dataverse table (new_case) scoped to Dynamics 365 Sales Enterprise. This custom table holds SSA/VA fields (new_ssa_claim_number, new_hearing_date, new_ere_session_status, new_onset_date, new_ssa_reviewer) and links to the Contact and Account via lookup fields. A 1:N relationship connects new_case to the Contact record.

Dibcase case status values (Initial Claim, Reconsideration, Hearing, Appeals Council, Federal Court) map to Dynamics Opportunity StageName values. Each stage maps value-by-value: 'Hearing' in Dibcase maps to 'Hearing Scheduled' or a custom stage in Dynamics. Probability weights and forecast category are re-applied based on Dynamics stage configuration. Stage-entry timestamps from Dibcase are preserved as custom datetime fields on the Opportunity.

Dibcase ERE Tool session data (SSA electronic records exchange — session dates, download counts, upload confirmations, exhibit flags) has no Dynamics 365 native equivalent. We map ERE session summary fields to custom fields on the Opportunity or custom Case entity: new_ere_session_status (single line of text), new_ere_last_download_date (datetime), new_ere_upload_confirmations (multiline text). The detailed ERE batch log migrates as a document attachment linked to the Opportunity.

Dibcase records of SSA reviewer calls, client emails, hearing scheduling meetings, and internal notes map to Dynamics 365 Tasks, Emails, Appointments, and Notes respectively. Activity timestamps, assigned staff (owner), and parent record links (case) are preserved. Dibcase internal notes with SSA correspondence details map to Dynamics Notes with a 'SSA Correspondence' category tag.

Dibcase client files and SSA exhibits (PDFs, correspondence, medical records) do not store as Dynamics native attachments. FlitStack AI exports Dibcase documents to a SharePoint library, creates a SharePoint Document Location record in Dynamics tied to the Contact or Opportunity, and preserves the original filename and Dibcase file index metadata. Inline Dibcase file viewer links are replaced with SharePoint document URLs.

Dibcase user records (attorneys, advocates, paralegals, support staff) map to Dynamics 365 SystemUser records by email address lookup. Unmatched users are flagged before migration — the team either creates a Dynamics user or assigns records to a fallback owner. Dibcase role labels (Attorney, SSA Advocate, Paralegal) map to a custom pick-list field on SystemUser (new_dibcase_role_c) for reporting continuity.

Dibcase custom fields not covered by standard mappings — such as dibcase_social_security_number, dibcase_va_file_number, dibcase_onset_date, dibcase_claim_status — are enumerated during discovery and mapped to custom fields on the appropriate Dynamics entity. Each custom field receives a new_ prefix and appropriate Dataverse data type. Fields not applicable in Dynamics (e.g., SSA-specific workflow triggers) are preserved as read-only reference fields for audit purposes.