Migrate from Court Clerk to Odoo CRM

Court Clerk case records map directly to Odoo crm.lead as Opportunities. The case_number field becomes the Opportunity name; case_type determines the pipeline or custom field value assigned. The original case_number from Court Clerk is preserved as a custom field x_court_case_id on the crm.lead for historical traceability after migration completes.

If Court Clerk records include billable fees or court costs, those amounts map to Odoo sale.order lines during migration. Fee line items become order products; total assessed costs map to sale.order.amount_total. This billing migration is opt-in and depends on case-type configuration in your Odoo environment.

Court Clerk party records including plaintiffs, defendants, witnesses, and attorneys map to Odoo res.partner records. The party role (plaintiff, defendant, witness, attorney) is stored as a custom pick-list field x_party_role on the partner record. Multiple party roles per case require junction records via the crm.lead.res_partner_rel table.

Court Clerk attorney records resolve by email match against Odoo res.users table. Attorneys with matching email addresses receive user_id assignment on their linked crm.lead records. Unmatched attorneys become res.partner records with partner_type = 'attorney' rather than system users. Your administrator confirms attorney-user assignments before migration runs.

Court Clerk judge_name field has no Odoo standard field equivalent. The judge is stored as a res.partner record with partner_type = 'judge'. A custom field x_judge_id on crm.lead acts as a Many2one pointer to the judge's partner record for reporting and filtering purposes.

Court Clerk filing documents including complaints, motions, and orders export as PDFs and re-upload to Odoo as ir.attachment records linked to the related crm.lead. File naming convention is {case_number}_{filing_type}_{date}.pdf. Inline images extracted from scanned filings are rehosted individually within Odoo attachments.

Court Clerk appearance records including scheduled hearings, hearing dates, and outcomes map to Odoo mail.message entries on the crm.lead with message_type = 'notification'. The next_hearing_date is stored as a custom datetime field x_next_hearing_date on the opportunity record for calendar integration.

Court Clerk judgment outcomes map to the Odoo Opportunity stage plus custom fields including x_judgment_date, x_judgment_amount, and x_disposition tracking granted, denied, or remanded dispositions. Disposition pick-list values require value-by-value mapping against your specific Odoo stage configuration.

Bond amounts and financial assessments in Court Clerk map to custom numeric fields on crm.lead (x_bond_amount, x_assessed_costs). If fee invoicing is active in your Odoo configuration, these values generate Odoo account.move records via sale.order conversion after the initial migration completes.

Court Clerk court_jurisdiction values (circuit, district, municipal, appellate, supreme) have no Odoo standard field. We create x_court_jurisdiction as a custom pick-list on crm.lead with the source jurisdiction values preserved exactly as exported from Court Clerk for accurate historical representation.

Court Clerk case status values (filed, active, pending, closed, appealed) map to Odoo crm.stage names via value-mapping. Each source status is mapped to the most appropriate Odoo stage in your configured pipeline. Probability percentages are re-applied per stage in Odoo settings after migration completes.

Court Clerk case_type values (civil, criminal, family, probate, traffic) map as a custom pick-list x_case_type on crm.lead. If your Odoo setup uses separate pipelines per case type, case_type also determines the crm.team assignment during migration for appropriate routing and team-based visibility.