Migrate from Dibcase Legal Case Management to Odoo CRM

Dibcase clients map to Odoo res.partner records. The client name maps to partner name fields, email to email, phone to phone. SSA-specific client identifiers like SSA representative contact info migrate as custom fields on res.partner using Odoo's x_ prefix convention.

Each Dibcase case becomes an Odoo crm.lead opportunity. The case number maps to the lead name or a custom x_case_number__c field. Case status (active, deferred, closed) maps to crm.lead stage_id values configured to match Dibcase status workflow. The client (res.partner) attaches via partner_id.

Dibcase practice areas (SSA disability, VA claims, personal injury, workers' compensation) map to Odoo crm.lead type values. SSA disability cases become type='opportunity' by default; other practice areas may use separate Odoo sales teams or custom fields for segmentation.

Dibcase case status values (new, in-progress, pending documentation, hearing scheduled, closed) map to Odoo stage_id pick-list values. We configure Odoo pipeline stages to match the firm's Dibcase workflow exactly, preserving stage sequence and probability weighting.

Dibcase tasks scheduled against cases map to Odoo project.task records if case management uses Odoo's project app, or to crm.lead activity records. Logged calls and meetings map to calendar.event with type and duration preserved. Task ownership resolves via Dibcase user-to-Odoo user email matching.

SSA-specific ticket number is a critical identifier with no Odoo CRM native equivalent. We create x_ssa_ticket_number__c as a Char field on crm.lead and populate it from Dibcase case data. This field is indexed for fast lookup and retained as a required reference for SSA practice workflows.

Dibcase disability type classification maps to x_disability_type__c as a selection field on crm.lead. SSA diagnosis codes may map to a separate x_ssa_diagnosis_code__c Char field depending on whether the firm tracks ICD or SSA-specific classification systems.

Dibcase ERE status fields (pending, retrieved, reviewed) and last check timestamps map to custom fields on crm.lead. x_ere_status__c uses selection values matching Dibcase ERE workflow states; x_ere_last_check__c preserves the last ERE polling timestamp for audit continuity.

Dibcase hearing scheduled date migrates to crm.lead date_deadline for pipeline visibility. If Dibcase stores hearing-specific notes or location, a calendar.event record is created with the hearing date as start_date. The crm.lead link preserves the case relationship.

Dibcase stores SSA representative contact details per case. In Odoo, the representative may be a res.partner record linked to the case (crm.lead) via an Odoo contacts relationship or stored as custom fields on the crm.lead (x_rep_name__c, x_rep_email__c) for firms not managing reps as contacts.

Dibcase file attachments stored in connected Dropbox folders are downloaded and re-uploaded as Odoo ir.attachment records linked to the target crm.lead or res.partner. The original file path is preserved in the attachment description field for audit trail. Large batches use Odoo batch processing to avoid timeout.

Dibcase notes attached to cases map to Odoo mail.message records on the crm.lead record. Author information resolves via Dibcase user email to Odoo user. Message body and create date are preserved; rich-text formatting may simplify to plain text depending on formatting complexity.

Any Dibcase custom fields added beyond standard SSA fields create corresponding custom fields on crm.lead. Field type is matched (Char, Date, Selection, Integer) and the Odoo x_ prefix or module-prefixed name is applied per Odoo naming conventions. Field relationships are maintained during migration.

Dibcase Dropbox folder connections and Zapier API credentials cannot be migrated to Odoo. Dropbox integration must be rebuilt using Odoo's document management or third-party storage connectors. Zapier-based automations require Odoo API credentials and rebuilt Zaps referencing Odoo's XML-RPC endpoints.