Migrate from CaseManager to Odoo CRM

CaseManager cases map 1:1 to Odoo crm.lead records. The crm.lead type field (lead/opportunity) is set based on CaseManager case status — Closed Won maps to opportunity, others default to lead. Original case create_date preserved as a custom field since Odoo's create_date reflects migration time.

CaseManager status values (Open, Pending, In Review, Closed) map to Odoo crm.stage records by name. Each status requires a corresponding stage in the Odoo pipeline. Stage sequence order is preserved from CaseManager's status flow. Closed cases map to a terminal stage with probability 100%.

CaseManager contacts map to Odoo res.partner records. The is_company flag is set false for person contacts. Email, phone, mobile, and address fields map directly. Partner records are created before crm.lead records so the partner_id lookup resolves correctly during migration. We also handle contact name splitting, parsing full names into firstname and lastname fields where CaseManager stores them as a single field.

CaseManager company records map to Odoo res.partner with is_company=True. Company name maps to partner name. Domain/website maps to website field. Industry, employee count, and revenue map to industry_id, employee_count, and revenue fields respectively if custom fields are configured in Odoo.

CaseManager links contacts to companies via a relationship field. In Odoo, contacts are child partners of the company partner record. We create the company partner first, then link contacts as child_ids with contact=True. Each contact also stores parent_id to the company partner.

CaseManager file attachments migrate to Odoo ir.attachment records with res_model='crm.lead' and res_id set to the target crm.lead ID. Files are downloaded from CaseManager's storage and uploaded to Odoo's filestore via the XML-RPC API. Inline images in case notes are extracted and attached separately. Large files exceeding Odoo's upload limit are chunked using the /web/binary/upload_attachment endpoint.

CaseManager logged activities (calls, emails, notes) map to Odoo mail.message records linked to the crm.lead. Call logs become mail.message with msg_type='notification'. Emails are stored as mail.message with email_from populated. Notes become mail.message with subtype='comment'. Original timestamps and authors preserved. Activity subject lines map to the mail.message subject field, and any attachments on activities are migrated as separate ir.attachment records linked to the mail.message.

CaseManager case owner ID is resolved by matching the owner's email address to Odoo res.users records. Unmatched owners are flagged before migration — you either invite them to Odoo first or reassign their records to a fallback user. No crm.lead lands without a valid user_id.

CaseManager priority values (Low, Medium, High, Critical) map to Odoo crm.lead.priority using the standard star-rating system (0-4 scale in Odoo). We apply a mapping table: Low=1, Medium=2, High=3, Critical=4. Custom priority labels require Odoo custom field creation. If CaseManager uses a numeric priority scale instead of named levels, we convert the numeric values to the nearest Odoo star rating during migration.

CaseManager custom fields on cases require Odoo custom field creation before migration runs. We deliver a field creation plan specifying field name, type (char, selection, float, date), and default value. Custom field IDs are stored as x_casemanager_field_id__c for traceability after migration.

CaseManager's case number/reference ID is preserved as crm.lead.name or as a custom field x_casemanager_case_number__c. Using a custom field avoids conflicts if Odoo's auto-naming sequence (LOGA/0001 format) is already in use. The original reference is critical for audit trails and linking back to source records.

CaseManager workflows, assignment rules, and automated triggers do not transfer to Odoo. Odoo uses its own automation engine (Studio workflows, server actions, automated actions) with different trigger semantics. We export CaseManager workflow definitions as a document your Odoo admin can use as a rebuild reference.