Migrate from bxp software to Odoo CRM

bxp Contacts map to Odoo res.partner records. We resolve the Contact record by email (the dedupe key) and preserve the original bxp contact_id in a custom Char field bxpid__c for cross-system reference. Custom fields attached to the bxp Contact (industry classification, territory, segment flags) are created as ir.model.field entries in Odoo before import and mapped by name. Any bxp contact-centre agent assignment is preserved in a custom res.partner field for reporting.

bxp Forms are the primary data container and can hold arbitrary field configurations per client instance. Each Form maps to an Odoo model based on its function: sales-oriented Forms map to crm.lead (the Odoo CRM lead object), financial Forms map to account.move or account.invoice, and bespoke Forms map to a custom model we create during schema provisioning. The mapping is determined during scoping by enumerating every Form in the source instance and classifying by purpose. This enumeration step cannot be skipped because bxp's value proposition is that no two instances share the same Form set.

bxp custom fields are enumerated during scoping and recreated in Odoo using the Settings > Technical > Custom Fields interface (Enterprise) or via Python module development (Community). Field types are mapped: bxp text to Char, bxp number to Float or Integer, bxp date to Date, bxp dropdown to Selection, bxp multi-select to Char (comma-separated) or Many2many tags. Each custom field receives a bxpid__c reference back to the original bxp field name for audit traceability.

bxp call activities and agent interactions log against Contact records. These map to Odoo crm.activity records linked to the res.partner via the res_id and model fields. Call duration, wrap time, and disposition codes from bxp become custom fields on the crm.activity record. The original bxp timestamp is preserved as activity_date for timeline ordering. Odoo's crm.activity model stores activity type (call, email, meeting, todo) with optional duration and description fields.

CDA (Custom Data Archive) is a proprietary bxp export format that must be parsed before loading into Odoo. We convert CDA exports to structured CSV or JSON using a format-specific parser developed during scoping. The parsed records are mapped to an Odoo custom model (e.g., bxp_agent_metrics or bxp_custom_archive) created specifically for the migrated data. CDA records are loaded after the standard res.partner and crm.lead migration phases are validated.

CCL (Contact Centre Log) is a proprietary bxp archive format used for detailed call-centre activity exports. Like CDA, CCL requires format-specific parsing before migration. We convert CCL exports to structured records and load them into the same custom Odoo model used for CDA data, with a record_type field distinguishing CCL call logs from CDA data. CCL call timestamps become the crm.activity activity_date; disposition codes map to a custom selection field.

bxp stores contact-centre agent metrics including call duration, wrap time, QA scores, and target attainment. These have no native Odoo CRM equivalent. We create a custom bxp_agent_metrics model in Odoo with fields for each metric type (call_duration_seconds, wrap_time_seconds, qa_score, target_attainment_pct). The model links to res.partner (for agent) and crm.activity (for associated call). This custom model is provisioned before the main migration and loaded after res.partner and crm.activity phases are validated.

bxp QA evaluations are tied to specific call records and agents. The QA schema varies by client deployment (bespoke evaluation forms). We enumerate every QA field during scoping, create a custom bxp_qa_record model in Odoo with the specific evaluation criteria as fields, and link each QA record to the associated crm.activity (call) and res.partner (agent). Evaluation scores and outcome flags are preserved as custom Float and Selection fields on the custom model.

bxp eLearning module stores training completion records, module scores, and assignment data. Odoo has no native eLearning module in its base CRM. We export eLearning records as structured data loaded into a custom bxp_elearning_record model (module_name, completion_date, score, status) linked to res.partner (the trainee). Alternatively, for read-only historical records, we export as PDF or CSV attachments on the relevant res.partner record. The customer chooses the preferred approach during scoping.

bxp Users (agents, supervisors, admins) map to Odoo res.users by email match. We extract every distinct bxp user referenced on Contact, Activity, and Form records and match by email against the destination Odoo instance's res.users table. Any bxp user without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import resumes. User active status, name, and email migrate directly.

Historical Form submissions in bxp (submissions stored against Contacts with timestamp and field values) map to crm.lead records if they represent lead intake, or to a custom model if they represent operational data types. The mapping is determined by the Form classification in the scoping enumeration. Submission timestamps become the crm.lead create_date; field values map to crm.lead standard fields (name, email_from, phone, description) or custom fields.

bxp notes and file attachments linked to Contact or Form records migrate to Odoo ir.attachment records linked via the res_model and res_id fields to the corresponding res.partner or crm.lead. Attachments are uploaded via Odoo's ir.attachment API. Notes migrate as mail.message records of type comment with body text preserved, linked to the parent record for activity timeline display.