Migrate from CompanyHub CRM to Odoo CRM

CompanyHub Contacts map to Odoo res.partner records with partner_type set to contact. The CompanyHub Contact's linked Company becomes the partner's parent_id, establishing the hierarchical relationship Odoo uses for address and billing grouping. Custom fields on the Contact transfer to custom res.partner fields, which we provision before import. Email, phone, title, and address fields map by API name. We use the partner's email as the dedupe key to prevent duplicate creation on re-runs.

CompanyHub Companies map to Odoo res.partner with partner_type set to company. The company record is created before any linked Contact import so that the parent_id relationship is satisfied at Contact insert time. CompanyHub's company domain and industry fields map to website and industry_id respectively. Custom fields on the Company transfer to the company-type partner record. If both a Company and Contact share the same name during migration, we create a single partner record and attach the contact as a child.

CompanyHub Deals map to Odoo crm.lead with type set to opportunity. The Deal's pipeline stage maps to a crm.stage that we configure in Odoo before migration. Deal amount transfers to planned_revenue, expected_revenue, and probability fields. The Deal's linked Contact becomes the lead's partner_id contact_id reference, and the linked Company becomes the partner_id. Closed-won and closed-lost status from CompanyHub sets the lead stage to won or lost and the active flag to False.

CompanyHub pipeline stages are user-defined text values. We capture the full stage list during discovery and provision matching crm.stage records in Odoo in the same sequence order. Each stage gets the same sequence number, and probability values map to stage_default_probability on each crm.stage. If the customer has multiple pipelines in CompanyHub, we create separate stage categories in Odoo or use tags to distinguish pipeline membership since Odoo's standard CRM does not support multiple named pipelines without custom development.

CompanyHub Tasks map to Odoo project.task records. The task's linked Contact and Deal become the task's partner_id and project_id references. Due date, priority, and assigned user transfer to date_deadline, priority, and user_ids respectively. Tasks created by UTrons are included in the migration but the triggering automation logic does not transfer. We note the Utron that created each task in a custom description field for the admin to review during post-migration rebuild.

CompanyHub Custom Tables (domain-specific objects like Properties, Courses, Payments) require pre-provisioning in Odoo. We request the customer provide Custom Table field layouts during discovery because the CompanyHub API does not expose table schemas programmatically in all cases. For simple tables (5-10 fields, no lookups to other objects), we provision custom fields on the relevant Odoo model (res.partner, crm.lead) using Odoo Studio. For complex tables with cross-object relationships, we create a custom Odoo model via a module that we provision alongside the migration data.

CompanyHub custom fields on standard objects map to Odoo custom fields on res.partner and crm.lead. We read the field definitions from the CompanyHub API (field name, type, options) and create matching fields in Odoo via Studio before import. Picklist options in CompanyHub become selection fields or relational fields in Odoo depending on whether the options represent a fixed set or references to other records.

CompanyHub Quotes map to Odoo sale.order records. Line items transfer to sale.order.line with product_id resolved by SKU match, quantity, and price. Quote totals and tax calculations are preserved. The linked Deal becomes the sale.order's opportunity_id. Signed quote PDFs and attachments migrate as ir.attachment records linked to the sale.order. Quote templates from CompanyHub do not migrate; we document the template structure for the customer to rebuild in Odoo's sale.quote template system.

CompanyHub users (owners) map to Odoo res.users. We match by email address. Any CompanyHub Owner without a matching Odoo User goes into a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status transfers from CompanyHub to Odoo. Owner-level field visibility rules in CompanyHub do not transfer; Odoo's record rules are configured post-migration based on the customer's access requirements.

CompanyHub email activity records map to Odoo mail.message with message_type=email. The linked Contact or Deal becomes the res_id and model reference on the message. Email body content migrates as the message body; we note that CompanyHub may truncate email content in API responses, and we flag any records with missing body text in the reconciliation report. Open tracking metadata transfers to mail.message tracking values if the destination Odoo instance has the email tracking addon enabled.

CompanyHub Notes map to Odoo mail.message with message_type=comment. The note body becomes the message body, and the linked Contact or Deal becomes the res_id reference. Notes created by UTrons retain a reference in the message body indicating the automation that generated them.

CompanyHub field-level and record-level visibility settings (Enterprise tier) do not migrate programmatically. We document the visibility matrix during discovery and provide a written specification for Odoo record rules and field groups to configure post-migration. The customer's Odoo admin applies these rules based on the organizational structure.