Migrate from CASEpeer to Odoo CRM

CASEpeer case records map to Odoo crm.lead (opportunity). The CASEpeer case number becomes crm.lead.name or a custom field Case_Number__c. Case stage names from CASEpeer (Intake, Under Investigation, etc.) map to Odoo pipeline stage values via value_mapping, potentially requiring a custom pipeline in Odoo CRM to mirror CASEpeer's lifecycle stages.

CASEpeer parties are separate records with a role field (Plaintiff, Defendant, Insurance Carrier). Odoo res.partner stores all parties in one model. We create one res.partner per party and use a custom pick-list field Party_Role__c to preserve whether the contact is a plaintiff, defendant, or medical provider. Multi-party cases link via opportunity_partner_rel or a custom junction table.

CASEpeer insurance carrier contacts map to res.partner records with Carrier__c checked as a boolean custom field. These carrier partners link to the crm.lead via partner_id or a custom Insurance_Carrier_ID__c lookup field, enabling carriers to receive status updates through Odoo's mail gateway and activity assignments tied to coverage verification deadlines.

Medical providers from CASEpeer migrate as res.partner records with Provider__c custom boolean flag set to true. Their contact information (name, phone, address, NPI number if available) copies directly into Odoo fields. Provider records link to the case opportunity via custom Provider_ID__c lookup field for reporting on medical record requests, treatment timelines, and provider communication logs.

CASEpeer case notes are timestamped text entries per case. We import them as mail.message records linked to the crm.lead with message_type='comment'. Odoo's chatter displays these chronologically. If the note count is large, we batch them via mail.message create() calls through the xmlrpc API.

CASEpeer calendar rules (court-specific deadlines) and manually created events become Odoo mail.activity records with activity_type_id, date_deadline, and user_id. We preserve the original event title as activity display name and the description as note. Recurring calendar rules require Odoo automation rules to be rebuilt using Odoo's server actions.

CASEpeer file attachments (settlement demands, court filings, medical records) are downloaded and re-uploaded as Odoo ir.attachment records. They link to the crm.lead via res_model='crm.lead' and res_id=lead_id. Odoo Enterprise stores attachments in its filestore; Community uses database attachment storage by default. File size limits differ — CASEpeer has no stated cap; Odoo Community caps at 128MB per file on direct upload.

CASEpeer custom intake fields (e.g., Statute_of_Limitations_Date, Referral_Source, Insurance_Policy_Number) map to Odoo custom fields created via ir.model.fields on the crm.lead model. Each custom field requires a separate field creation step before migration. We map text fields, date fields, pick-list fields, and boolean fields type-by-type.

CASEpeer custom fields on party records (e.g., Bar_Number for attorney contacts, DOB for plaintiff records) map to Odoo custom fields on res.partner. Field types must match — date fields to date fields, pick-lists to selection fields — or Odoo's import validation rejects the values.

CASEpeer attorney and staff users map to Odoo res.users by email address. CASEpeer owner_id on case records resolves to Odoo user ID via email match. Unmatched owners are flagged and assigned to a fallback Odoo user or an unassigned placeholder created in advance.

CASEpeer case outcomes (Settled, Won, Lost, Dismissed) map to Odoo pipeline stage values. We create a custom Odoo pipeline called 'Case Pipeline' with stages matching CASEpeer status names. Stage probability and forecast category are set per Odoo stage configuration. Historical outcome timestamps are preserved in custom datetime fields on the lead.

CASEpeer tracks case hours and fees within the case record. Odoo separates billing into sale.order (for time-and-material quotes) and account.move (for invoices). We preserve CASEpeer fee totals and hour counts as read-only custom fields on the crm.lead. Odoo billing workflows must be rebuilt in Odoo if trust accounting is required.