Migrate from Dibcase Legal Case Management to Salesforce Sales Cloud

Dibcase matters are the primary case record. We map these to Salesforce Cases by default using the disability-case record type. If Dibcase has multiple matter types (SSD, VA, PI), each type can map to a separate Salesforce record type with its own page layout and status pick-list values. The dibcase_matter_id is stored as Source_System_ID__c for traceability.

Dibcase contacts attached to a matter map directly to Salesforce Contacts. Each Contact links to a primary Account (the client's organization or individual name). Dibcase contact roles on a matter map to the Contact's Role field on the Case or to a custom Contact_Role__c pick-list.

Dibcase allows attaching organizational clients. These map to Salesforce Accounts with the organization's name, industry, website, and size fields mapped directly. Individual clients without an organization map to an Account with the individual's name in Account.Name. We also preserve any Dibcase account-level custom fields (e.g., billing reference, regional office) as __c fields on the Account object. Multiple contacts per organization link to the same Account via AccountId, maintaining hierarchy.

Dibcase's SSA/VA form pipeline stages (e.g., Initial Filing, Medical Review, Hearing Scheduled, Fully Favorable) are mapped value-by-value to Salesforce Case Status pick-list values or to a custom Disability_Stage__c pick-list field on Case. We preserve the stage-entered timestamp as a custom datetime field for reporting continuity.

Dibcase files attached to matters ( briefs, medical records, SSA notices) are downloaded and re-uploaded as Salesforce Files linked to the corresponding Case record. File size limits apply (Salesforce default 25MB per file; larger files require file chunking or an external storage integration). Folder structure in Dibcase is preserved as a custom Folder_Path__c text field on ContentDocument.

Dibcase tasks mapped to Salesforce Tasks with Type='Task', original due dates preserved as ActivityDate, and owner resolved by email match to Salesforce users. Tasks without a Salesforce user owner are assigned to a designated fallback owner and flagged for review.

Dibcase text notes on matters migrate to Salesforce ContentNotes linked to the Case. Rich text formatting is preserved. Plain-text Dibcase notes migrate to ContentNote with no formatting applied. If a Dibcase note contains attachments, those files are extracted and re-associated as Salesforce Files on the Case. We also capture note metadata (created date, author) as custom fields on ContentNote for audit trails.

Dibcase's SSA/VA form templates (hundreds of pre-built merge forms) have no Salesforce equivalent — Salesforce does not store document templates in the CRM by default. We export the template definitions as a PDF reference document for your admin to configure via Salesforce's native document generation tools (or a third-party app like Conga or DocuSign).

Dibcase's ERE batch queue, session-aware downloads, and automated SSA pull workflows are vertical-specific automation with no Salesforce equivalent. We document the ERE workflow logic so your Salesforce admin or implementation partner can evaluate AppExchange alternatives (e.g., Boomi, MuleSoft) for automated record retrieval.

Dibcase custom fields added to matters (e.g., hearing date, disability onset date, RFC determination) map to custom fields on the Salesforce Case object using the __c naming convention. Data types are mapped type-aware: date fields to Date, pick-lists to pick-list, text to Text(255). Dibcase field-level security settings do not map — sharing rules must be reconfigured in Salesforce.

Dibcase integrations built in Zapier (e.g., Slack notifications, calendar sync, intake form webhooks) must be rebuilt as Salesforce Flow triggers or Salesforce native integrations. We document the Zap triggers and payloads so your admin can recreate them in Salesforce or via a reconnected Zapier account.

Dibcase calendar events (hearing dates, ERE session times) map to Salesforce Events linked to the Case with original start/end times, subject, and description preserved. Events without a Salesforce user owner are flagged and assigned to a fallback owner. We also map Dibcase recurring events, if any, to Salesforce recurring Event series. Time zone handling preserves the original UTC offset to ensure hearing times display correctly in Salesforce calendar views.