Migrate from OpenCRM to Odoo CRM

OpenCRM Company records map to Odoo res.partner with is_company set to True. The company name maps to name, and all standard address fields (street, city, postcode, country) map directly. We use the OpenCRM record ID as an external identifier stored in a custom ref field on res.partner to enable safe upserts and cross-reference audit after migration. Companies must be imported before Contacts to satisfy Odoo's partner_id foreign-key on the contact partner record.

OpenCRM Contact records map to Odoo res.partner with is_company set to False and parent_id pointing to the Company res.partner created in the previous step. The parent_id is resolved using the OpenCRM record ID that we stored as the external reference on the Company partner. If a Contact has no parent Company in OpenCRM, we create an is_company partner record for it and flag it in the reconciliation report. Title, phone, mobile, email, and website map directly; any custom contact fields map to custom res.partner fields created during schema provisioning.

OpenCRM Deal records map to Odoo crm.lead with type = opportunity. The deal value maps to expected_revenue, the expected close date maps to date_deadline, and the owner maps to user_id by email matching. Deals attached to a Contact map with partner_id pointing to the Contact res.partner; Deals attached to a Company map with partner_id pointing to the Company res.partner. We resolve the Odoo partner_id using the OpenCRM record ID stored as the external reference on the res.partner.

OpenCRM pipeline stage names are tenant-defined and rarely align with Odoo's default crm.stage values (New, Qualified, Proposal, Negotiation, Won, Lost). We produce a stage-mapping table during scoping, present it to the customer for confirmation, and apply the mapping during crm.lead import so each record lands in the correct Odoo stage. Stage probabilities are mapped from OpenCRM to Odoo stage_sequence and probability fields. If the customer uses multiple OpenCRM pipelines, each maps to a separate crm.team in Odoo with its own stage sequence.

OpenCRM Activities map to Odoo mail.activity records linked via res_model = crm.lead or res.partner and res_id pointing to the migrated record. Activity type (call, meeting, task) maps to Odoo's activity_type_id, with the original activity name preserved in the activity note. Dates and timestamps are normalised to UTC before import. We resolve the Odoo user_id for activity assignment by email matching against the Odoo res.users table.

OpenCRM Notes attached to Contacts, Companies, or Deals map to Odoo mail.message records with message_type = comment. We link each message via res_model and res_id to the migrated crm.lead or res.partner using the OpenCRM record ID cross-reference. Note body migrates as plain text; rich formatting in OpenCRM Notes is simplified on import. Author attribution maps to the Odoo user by email.

OpenCRM file attachments stored against Contacts, Companies, or Deals are extracted to a file store during staging and then loaded into Odoo ir.attachment with res_model pointing to crm.lead or res.partner and res_id pointing to the migrated record ID. We generate reference links in the attachment name to the source OpenCRM record for audit traceability. Files are ingested via Odoo's base_import module or direct file write to the Odoo filestore depending on volume.

OpenCRM Owner records map to Odoo res.users by email matching. The OpenCRM owner reference on Contact, Company, and Deal is resolved to an Odoo user_id at migration time. Any OpenCRM Owner without a matching Odoo user is held in a reconciliation queue for the customer's Odoo admin to provision before the record import resumes.

OpenCRM custom fields on Contacts, Companies, and Deals are discovered during scoping, typed (text, number, date, picklist), and provisioned in Odoo via ir.model.fields or Odoo Studio before data import begins. Custom field values are included in the CSV staging files and mapped field-by-field during the import transform. Picklist values in OpenCRM are mapped to Odoo selection fields or many2one relations depending on the data.

OpenCRM tags on Contacts and Companies map to Odoo crm.tag records with a many2many relation to crm.lead. Tags stored as flat string arrays in OpenCRM are split and deduplicated, and crm.tag records are created before the crm.lead import. The tag-many2many relation is established during the crm.lead insert using the tag names as the matching key.

OpenCRM Workflow rules are not migrated as executable code. We inspect each active OpenCRM workflow, document its trigger (record creation, field change, stage transition), conditions, and actions, and deliver a written inventory recommending Odoo Automated Actions (ir.actions.server) or Studio action rule equivalents. The customer's Odoo admin rebuilds the automations post-migration using Odoo Studio or the developer interface.

OpenCRM record creation and modification timestamps are preserved on the migrated Odoo records. crm.lead.create_date is set from the OpenCRM Deal creation date; mail.activity.date_deadline preserves the original activity due date. We normalise all timestamps to UTC during the staging phase to avoid timezone offset issues when loading into Odoo.