Migrate from The Case File to Odoo CRM

The Case File contacts map directly to Odoo res.partner records. The 'company' flag on a contact sets the is_company boolean — true for organization contacts, false for individual contacts. Partner addresses (street, city, country) migrate to res.partner address fields using Odoo's address layout model.

The Case File company records become res.partner entries with is_company=True. The company name maps to name, domain maps to website, industry maps to industry_id via the res.partner.industry selection field. Employee count and revenue migrate as custom fields since Odoo stores these on the partner form but not as standard fields.

Each The Case File case maps to a crm.lead record in Odoo CRM. The case title becomes the lead name (name field), case description becomes the description text field, and case priority maps to priority (1=Low, 2=Normal, 3=High). The case type or category maps to the type field — use 'lead' for prospect cases and 'opportunity' for active deal cases based on case status.

The Case File status values (e.g., Open, In Progress, Resolved, Closed) map to Odoo crm.stage records by name. The migration creates stage records in the default pipeline if they do not already exist. Each stage gets sequence order matching the source status sort order. Probability values are assigned per stage using Odoo's stage probability defaults unless custom probabilities were tracked in The Case File.

Activities logged against a case in The Case File (calls, meetings, tasks, notes) migrate as mail.activity records. The activity_type_id is resolved by matching the source activity type label to Odoo's built-in activity types (call, meeting, todo, email). Original date and user assignment are preserved via activity_date_deadline and user_id respectively. Activity summary maps to activity_note.

Documents attached to cases migrate as ir.attachment records with res_model='crm.lead' and res_id set to the target crm.lead ID. The original filename is preserved in the name field, and the file binary content is stored in the datas field. Odoo's attachment size limit (default 100MB) is respected; files exceeding this threshold are flagged for manual handling.

Custom fields defined in The Case File are created as ir.model.fields entries on the crm.lead model before migration. Field types are translated: text/textarea becomes char or text depending on length, numbers become integer or float, dates become date, and pick-lists become selection fields with the original options as key-value pairs. Field technical names are generated from the source label (e.g., 'Contract Value' becomes x_contract_value).

Case owners in The Case File are matched to res.users records by email address. Unmatched owners are flagged as warnings — the case is assigned to a fallback user (typically the migration admin) and a custom Source_Owner__c field preserves the original owner name for manual reassignment in Odoo.

If The Case File has a team or department concept, these map to crm.team records. The team name and member list migrate; team members are linked via crm.team.member_ids (res.users many2many). Odoo requires the team to exist before members can be assigned, so the migration creates teams before user assignments are processed.

Billing records and invoice line items in The Case File do not map to standard Odoo CRM objects. These are exported as a separate dataset (account.move records in draft state) and handed to the accounting team for reconciliation. The case reference is preserved in the invoice line description for audit traceability.

Free-text notes attached to cases migrate as mail.message records on the crm.lead. The message_body field carries the note text, message_type is set to 'comment', and the original note date maps to date. Author is set to the system migration user if the original author cannot be resolved.