Migrate from ConvergeHub to Odoo CRM

ConvergeHub Leads map to Odoo CRM Lead records. The HubSpot-style separation between Leads and Contacts does not exist in Odoo — Leads in Odoo are pre-conversion opportunities that an Odoo user manually converts to a Contact linked to a Company. We preserve all HubSpot Lead fields (status, source, assignment, score) in Odoo Lead fields, and create a custom field original_lead_source__c to retain the original HubSpot lead source for reporting continuity.

ConvergeHub Accounts map to Odoo CRM Company records. The Account ID becomes the external identifier used to resolve Contact-to-Company relationships during the Contact import phase. Industry, size, address, and any custom properties map to Odoo's res.partner fields with is_company=True. Company records load first so that the Contact import can satisfy the partner_id lookup dependency.

ConvergeHub Contacts map to Odoo CRM Contact records with is_company=False linked to their parent Company via parent_id. Contact roles, lifecycle stage, phone, email, and custom fields migrate directly. The original HubSpot contact-to-account relationship reconstructs via the foreign key extracted from ConvergeHub's CSV exports, mapped to the Odoo parent_id reference on res.partner.

ConvergeHub Deals map to Odoo CRM Opportunity records. HubSpot deal stage maps to Odoo stage_id via a configured stage sequence that we define during Odoo CRM setup. Deal value, probability, expected close date, and owner assignment migrate directly. Pipeline assignment from HubSpot maps to Odoo team_id (sales team) and a custom pipeline__c field if the customer uses multiple distinct pipelines in ConvergeHub.

Each HubSpot deal pipeline and its stages become an Odoo CRM stage sequence. We configure the stage names, sequence order, and probability percentages in Odoo CRM before migration. Closed-Lost and Closed-Won statuses from ConvergeHub map to Odoo's Lost and Won stage states.

ConvergeHub Cases map to Odoo Helpdesk Ticket records if the customer installs the Odoo Helpdesk module. Case status, priority, subject, description, and linked Contact/Account migrate to Ticket. Stage configuration maps ConvergeHub case statuses to Odoo ticket stages. If Helpdesk is not installed, Cases map to CRM Lead for a lighter-weight destination.

ConvergeHub Invoices migrate to Odoo Accounting Account Move records. Line items, totals, tax, and payment status migrate; however, payment gateway transaction history and partial payment states require the Odoo Accounting module to be installed and configured. Invoice-to-Deal linkage is preserved via a custom field invoice_origin_deal__c.

ConvergeHub Products map to Odoo Product Template records. Product name, SKU (mapped to default_code), unit price, and description migrate directly. Product associations to Deals in ConvergeHub are preserved by linking the migrated Opportunity to the migrated Product Template via Opportunity Line Items if the customer enables the Sale module.

ConvergeHub Activities (calls, tasks, events, logged communications) map to Odoo Mail Activity records linked to the parent Lead, Contact, or Opportunity via res_id and res_model. Activity type, timestamp, notes, and owner assignment migrate. ConvergeHub's activity-to-record linkage reconstructs via the external ID references in the CSV exports.

ConvergeHub document metadata and blob storage references migrate to Odoo Ir Attachment records. We download file attachments from ConvergeHub, map their associations to the migrated Contact, Account, Deal, or Case, and upload them to Odoo's attachment storage. Only metadata and attachment blobs migrate; document version history is not preserved.

ConvergeHub custom fields on Accounts, Cases, Contacts, Deals, Invoices, Leads, Products, and Targets are inventoried during scoping and created as custom fields on the corresponding Odoo model (res.partner, crm.lead, sale.order, etc.) before migration begins. Picklist values, multi-select fields, and date formats are mapped in a field-level substitution table generated during discovery.

ConvergeHub automation rules defined in the Tools section have no export path. We document each active automation via screenshots and structured notes, then deliver an Odoo Studio automation inventory that maps each HubSpot trigger-action sequence to an equivalent Odoo Automated Action or Server Action. The customer's admin rebuilds automations in Odoo Studio post-migration.

ConvergeHub User records (name, email, role, ACL assignment) map to Odoo Res Users. We resolve ConvergeHub owner assignments on Deals, Cases, and Contacts by matching email addresses to Odoo user records. Any HubSpot owner without a matching Odoo user goes to a reconciliation queue for admin provisioning before record migration.

ConvergeHub Targets (sales goals and quota tracking) migrate as Odoo CRM Pipeline Forecast records if the customer enables the forecasting feature, or as a custom target object if the customer's Odoo configuration uses a Project-based goal structure. Target values, periods, and owner assignments migrate directly.

ConvergeHub Quotations map to Odoo Sale Order records. Line items, pricing, terms, and linked Deal association migrate. Product references resolve to the migrated Product Template. If Odoo Sale module is not installed, Quotations are stored as CRM Lead notes with a custom quotation__c flag for admin awareness.