Migrate your Dibcase Legal Case Management data

Client records are the primary billing entity in Dibcase. Active, Deferred, Inactive, and Other statuses count toward the plan's client tier limit; Leads, Rejected Leads, Closed, and Archived do not. We migrate all client records and preserve their status as a mapped field so the destination tier count aligns with Dibcase's definition.

Cases link to Clients and carry pipeline stage, case type (SSD, VA, PI, WC), assigned attorney, and disability determination status. We map case-to-client relationships and preserve the full case type taxonomy across migration.

Dibcase stores documents in an indexed client file system with an in-app viewer and recent document visibility. We export the full document library per client, preserving folder structure, file names, and upload timestamps for audit continuity.

Dibcase ships hundreds of SSA and VA form templates plus custom Word/PDF templates created by the firm. We export custom templates as Word/PDF files; standard government forms are referenced by name. Template-to-field mapping requires field-level alignment with the destination system's document generation layer.

Contact records include party information for claimants, medical providers, witnesses, and opposing counsel. We migrate all contact types and preserve their role associations with specific cases.

Time tracking records billable and non-billable hours against cases. We export time entries with date, duration, description, attorney assignment, and billing rate for continuity in the destination practice management or billing system.

Fees tracker records statutory fees, contingency percentages, and SSA representative payee fee arrangements. We export fee records as structured data tied to the corresponding case for accurate billing history in the destination system.

Medical records are tracked per case with document attachments and source citations. We export medical record entries and linked documents; the structured versus unstructured split varies by firm setup and requires case-by-case field mapping.

Dibcase uses custom pipeline stages for case progression. We capture the full stage taxonomy and map each stage name to the destination CRM's pipeline stages, flagging stages with no direct equivalent for manual reassignment.

Digital intake forms capture claimant information at onboarding. We export intake form responses as structured data or flattened notes attached to the client record, depending on the destination's intake object model.

SMS and email communications are stored threaded against client or case records. We export communication threads as note entries with timestamp and sender metadata in the destination system.

Firms can create custom fields on client, case, and contact objects. We detect custom field schemas at scoping, export field names and values, and map them to equivalent custom fields in the destination or flag gaps requiring post-migration field creation.