Migrate from Criminal Case Management to Odoo CRM

Case records map to crm.lead with type='opportunity'. Case title becomes the opportunity name, case status maps to Odoo stage_id via value mapping, and case number, court name, filing date, and judge name migrate as custom fields (x_case_number, x_court_name, x_filing_date, x_judge_name) on the crm.lead record.

Client party records map directly to res.partner with partner_type='contact'. Client name maps to partner name fields. Address, phone, and email fields migrate directly. The party's role in the case (Plaintiff, Defendant, Victim) is preserved as a custom x_party_role field on the partner record or via res.partner.category assignment.

Attorney and opposing counsel party records map to res.partner with x_bar_number stored as a custom field and x_counsel_role storing the role value (Opposing Counsel, Co-Counsel, Bonding Company). Where available, attorney email resolves to an Odoo user_id via email match so the attorney appears as a team member on the related opportunity.

Witness and victim party records map to res.partner with x_party_role set to 'Witness' or 'Victim'. Contact information (address, phone, email) migrates directly. Witness statements or special notes attached to the witness record migrate as notes on the partner or as custom fields if the source stores structured witness data.

Attorney-to-case assignments map to the crm.lead record via a custom many2many field (x_attorney_ids) linking to res.partner records of attorney type. If the attorney has an Odoo user account, their user_id is also linked so their name appears in the opportunity's Salesperson field. Multi-attorney assignments require splitting to multiple linked records in the many2many field.

Case documents (pleadings, evidence files, court orders, correspondence) re-upload to Odoo ir.attachment with res_model='crm.lead' and res_id pointing to the migrated opportunity record. Original filenames and MIME types are preserved. File size limits from the source platform are handled by chunking large files during the migration run.

Case notes and hearing summaries map to crm.lead notes (mail.message with subtype 'comment'). Each note retains its original create_date and author information. If the source platform records note type (internal memo vs. court filing note), the type is preserved as a custom x_note_type field on the message record.

Scheduled court dates map to calendar.event records linked to the crm.lead via x_case_id custom field. The event name uses the case number and hearing type. Start and stop times come from the source court date fields. If the source includes court room or virtual hearing link, those migrate as x_court_room and x_hearing_link custom fields on the event.

Billable hours, hourly rates, and total case costs migrate as custom monetary fields (x_hourly_rate, x_total_hours, x_total_case_cost) on crm.lead. Odoo Invoicing handles actual billing post-migration. Trust account balances are not migrated — those require separate Odoo Accounting configuration. Time entries are preserved as a reference dataset for rebuilding in Odoo.

Source-specific case type pick-list values (Felony, Misdemeanor, DUI, Drug, Violent Crime, etc.) map to corresponding values in a custom x_case_type pick-list on crm.lead. Values with no direct Odoo equivalent are preserved as-is and flagged for admin review — often used for filtering and reporting by case classification in Odoo views.

Probation start/end dates, sentencing details, and supervision level migrate as custom datetime and selection fields (x_probation_start, x_probation_end, x_supervision_level) on crm.lead. These require Odoo Studio setup before migration. Where the source stores compliance check dates, those map to scheduled activities on the opportunity record in Odoo.