Migrate from openCRX to Odoo CRM

openCRX LegalEntity records map directly to Odoo res.partner with partner_type set to company. The LegalEntity name maps to name, postal address from the related PostalAddress object maps via address fields (street, city, country, zip), and phone from related PhoneNumber maps via phone. openCRX multi-currency settings per LegalEntity map to Odoo partner properties. We resolve the parent-child LegalEntity hierarchy into Odoo's commercial partner link if present.

openCRX Contact records map to Odoo res.partner with type=contact, linked to a parent res.partner (type=company) via parent_id. Contact's PostalAddress and PhoneNumber relations map to Odoo partner address fields. openCRX's Contact.fullName splits into firstname and lastname on Odoo. We use email as the dedupe key across both LegalEntity and Contact imports. Role-based attributes on openCRX Contact (e.g., buyer, decision-maker) are preserved as tags on the Odoo partner record.

openCRX Opportunities inherit from the abstract contract hierarchy and carry deal fields, ratings, and associated notes. We map Opportunity to Odoo crm.lead where type=opportunity (versus type=lead for unqualified prospects). The openCRX contract rating maps to crm.lead probability. Stage transitions and timestamps from openCRX activity on the Opportunity are preserved as stage change comments and activity history in Odoo.

openCRX Quotes inherit from the same contract hierarchy as Opportunities and Sales Orders, with line positions modelled as contract positions. We map Quote to Odoo sale.order in quotation state. Quote positions map to sale.order.line with product, quantity, price_unit, and discount preserved. openCRX's multi-currency pricing rules carry into Odoo currency_id and price_list_id on the sale.order.

openCRX Sales Orders follow the contract hierarchy and can be transformed from Quotes. The Sales Order header maps to Odoo sale.order with state=sale. Each order position maps to sale.order.line with product_id, product_uom_qty, price_unit, and discount preserved. If the Sales Order was created from a Quote, we map the sale.order.source_document to the original sale.order quotation.

openCRX Invoices are terminal contract objects in the sales process chain, inheriting from contract classes. We map Invoice headers to Odoo account.move records of type=out_invoice, preserving invoice number, date, and payment terms. Line positions map to account.move.line records. openCRX's payment status and currency context carry into Odoo's invoice state and currency_id. Invoices in openCRX that are posted or reconciled map to Odoo posted account.moves.

openCRX Products with bundles and design-to-order configurations map to Odoo product.product with type=service or type=product. openCRX multi-currency price lists and run-time pricing rules map to Odoo product.pricelist records. openCRX Product.run_time_pricing rules become Odoo pricelist rule records. We capture product.product fields name, default_code, list_price, standard_price, type, and categ_id during import.

openCRX Activities with time-tracking map to Odoo mail.activity records. Activity Tracker groupings in openCRX (which group related activities under a named tracker) map to Odoo mail.activity.type and stage_id on crm.lead, or to tags if the tracker structure does not map cleanly to a stage. Custom feature definitions on openCRX activity subtypes are identified during scoping and mapped to Odoo custom activity type definitions. Activity timestamps and duration carry into Odoo date_deadline and activity_date_deadline.

openCRX custom fields added via DataBinding PropertySet are stored as feature definitions bound to CrxObject at runtime. We identify all active PropertySet custom fields during scoping, map their data types to Odoo field definitions (Char, Text, Float, Integer, Date, Datetime, Many2one, One2many), and pre-create them as ir.model.fields on the relevant res.partner, crm.lead, or product.product model before migration begins. openCRX multi-valued PropertySet attributes become Odoo One2many or Many2many relations where the data model supports it.

openCRX stores binary attachments linked to objects via its document management layer. We extract attachment metadata and file content from the export process. During Odoo import, attachments re-attach to the corresponding migrated record (res.partner, crm.lead, sale.order) via ir.attachment records with res_model and res_id pointing to the target record. We run the export on a Linux or macOS client to avoid the Windows WebDAV quirks that affect openCRX file access. We flag any attachment whose original file is inaccessible due to WebDAV path issues for manual re-upload.

openCRX role-based security with segment-scoped user assignments maps to Odoo res.users. We extract active users by email from openCRX and match against Odoo user records. openCRX segment membership maps to Odoo sales team membership via crm.team member records. Permissions and access levels from openCRX roles are documented in the migration scope for the customer's admin to reassign manually in Odoo Access Rights configuration. We do not map openCRX role definitions to Odoo groups as the models are structurally different.

openCRX Workflow Processes are segment-scoped and stored as instance-bound definitions, not as records that can be exported and re-imported. We extract workflow process definitions (trigger conditions, actions, assigned activities) during discovery and deliver them as a written inventory for the customer's admin to rebuild in Odoo Studio. This is not a code migration; it is a process audit and handoff. Alert Topics follow the same constraint and are documented separately.