Migrate your Odoo CRM data

Contacts and Partners share the same res.partner model in Odoo. Standard fields (name, email, phone, address, company_id) are fully exportable via XML-RPC. We map res.partner records directly to the destination CRM's contact object, preserving the partner_id on any related records.

Leads (crm.lead) are the top-of-funnel records with fields including name, contact_name, email_from, phone, source_id, and stage_id. When a Lead is converted to an Opportunity, it creates a linked crm.lead record with type='opportunity'. We export both types and flag which records originated as Leads vs. converted Opportunities.

Opportunities are crm.lead records with type='opportunity', linked to pipeline Stages and Sales Teams via stage_id and team_id. Key fields include expected_revenue, probability, date_closed, and partner_id (the customer). We preserve the opportunity-to-contact linkage and the pipeline stage ordering.

Stages live in crm.stage and are ordered per team via crm.team.stage.rel. Custom stages added by the customer are included in the export. We sequence the stage order and map stage names to the destination CRM's pipeline stage definitions, flagging any stage that uses Automation rules that may not transfer.

Sales Teams (crm.team) group Opportunities and assign Leads to team members via user_id and member_ids. Each team has its own pipeline with independent stage configurations. We export team membership and map it to the destination's equivalent team or user assignment model.

Activities (mail.activity) are linked to crm.lead records and include type, date_deadline, user_id, and note. Activity history is a key migration concern because it is high-volume and loosely coupled — we export it after leads/opportunities and validate record counts before loading.

Custom fields defined via Odoo's Studio or in custom addons are stored as columns in crm.lead. These are fully exportable, but their field types (selection, many2one, many2many) may not map 1:1 to the destination CRM's custom field system. We flag field-type mismatches during the scoping call.

Attachments (ir.attachment) linked to crm.lead records are stored in the Odoo filestore. Large attachment volumes can bloat exports. We chunk the filestore export separately and remap ir.attachment.res_id/res_model references after target IDs are assigned, using the attachment.res_model + res_id linkage to re-attach them to the correct records in the destination.

Tags (crm.tag) are applied to crm.lead records via a many2many field. Tag names are preserved as a flat list and mapped to the destination CRM's tagging or label system. Custom tags added by the customer are included in the export.

Odoo's predictive lead scoring (crm.scoring.rule) is an Enterprise-only feature with a proprietary algorithm that depends on Odoo's AI infrastructure. We do not migrate scoring rules because they have no equivalent in most destination CRMs and the model cannot be reliably reverse-engineered.

CRM automation rules (base.action.rule and ir.actions.server scoped to CRM) are Enterprise-exclusive and tightly coupled to Odoo's action framework. These cannot be migrated to non-Odoo CRMs. We export a plain-English audit of which rules exist so the customer's implementation team can manually reproduce them.

Quotations (sale.order) are linked to Opportunities via create_uid and Odoo-specific relational fields. They carry line items (sale.order.line), pricing, and taxes. We export quotations with their linked partner and opportunity, but note that the full sale.order data model includes accounting fields that may require the Accounting module to be active in the destination.