Migrate from Dibcase Legal Case Management to Freshsales

Direct map. Each Dibcase Client becomes one Freshsales Contact. The client's primary matter becomes the first Deal associated to that contact. Dibcase's client status values (Active, Deferred, Inactive, Other) map to a custom contact_status__c pick-list field on the Contact object. The mapping preserves all client contact details including name, email, phone, address, and custom fields while linking the contact to the appropriate firm Account.

Dibcase stores firm/organization data on the Client record itself. We extract the firm name field and create a corresponding Freshsales Account, then link the Contact to it via the primary AccountId lookup. If no firm name exists, the contact lands without an Account — flagged for manual review.

Each Dibcase Matter maps to one Freshsales Deal. The matter name becomes the Deal name, and Dibcase's matter status (New, In Progress, Pending SSA, Hearing, Approved, Denied) becomes a Freshsales custom matter_status__c pick-list. Freshsales deal stage (Appointment Scheduled → Proposal → Negotiation → Closed Won) is assigned based on matter type — SSA matters use a dedicated SSA pipeline with stage names that mirror Dibcase workflow states.

Matters in Dibcase lead stages (New Lead, Rejected Lead, Closed Lead) that haven't converted to full matters route to Freshsales Leads. Once Dibcase shows a matter has been formally opened (SSA filing started), that record splits to a Freshsales Deal instead, preserving the Dibcase matter ID in a source_matter_id__c field.

Dibcase's lead-stage kanban cards (New Lead → Pending SSA → Hearing → Decision) become a Freshsales Sales Pipeline with custom Deal Stage names. Each Dibcase lead stage gets a corresponding Freshsales stage so the pipeline view mirrors the firm's case workflow. Stage-entered timestamps are preserved as stage_entry_date__c custom datetime fields on the Deal.

Dibcase documents attached to matters are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Deal record. Dropbox/GDrive connected folders are flagged for manual re-link after migration — Freshsales's native file storage replaces the Dibcase cloud folder structure. File size limits apply: Freshsales caps files at 25MB per upload.

Dibcase's SSA ERE batch-queue records (SSA forms, hearing dates, status updates pulled from the SSA ERE website) have no Freshsales native equivalent. We migrate them as a custom SSA_Events__c object with fields for ssn_last_four__c, hearing_date__c, ecs_status__c, and source_updated_at__c. Your team rebuilds ERE monitoring using Freshsales workflows or a reconnected Chronicle integration.

Dibcase tasks and calendar events map to Freshsales Tasks and Events with original timestamps, due dates, and assigned attorney/representative preserved. Dibcase's SSA hearing reminders carry through as Freshsales Events with the hearing_date__c field populated. Task priority maps to Freshsales task priority (High / Medium / Low).

Dibcase time-tracking entries (attorney hours, paralegal time, case-related tasks) have no direct Freshsales equivalent. We migrate them as a Time_Entry__c custom object linked to the Contact and Deal, with fields for entry_date__c, hours__c, billing_type__c, and description__c. Freshsales's native billing is separate from time tracking — your team configures time-entry workflows in Freshsales or connects a billing add-on.

Dibcase stores fee agreements, outstanding balances, and billing records per client. Freshsales has no native billing module (that is handled by separate Freshworks products). We preserve fee records as a Fees__c custom object with amount__c, status__c, due_date__c, and billing_type__c fields for reference and reconciliation — your finance team maps these to Freshbooks or QuickBooks after cutover.

Dibcase custom fields built for SSD, VA, personal injury, and workers' compensation practice areas map to Freshsales custom fields. Each practice-area type requires its own field set — SSA disability fields (ICD_codes__c, onset_date__c, disability_type__c) and PI fields (incident_date__c, at_fault_party__c) live as separate field groups attached to the Deal object. Your admin pre-creates the field schema before data lands.

Dibcase's SSA ERE spreadsheet import (OHO and A/C spreadsheets downloaded from the SSA ERE website) stores row-level SSA case-update data. We migrate this as an ERE_Last_Import__c long-text area field on the Deal with the raw data preserved. Any automated ERE monitoring logic built in Dibcase has to be rebuilt using Freshsales workflow rules or a reconnected Chronicle Legal integration.