Migrate from HubSpot to Odoo CRM

HubSpot Contacts with a Company association merge into the corresponding Odoo res.partner record with company_type='contact' and parent_id pointing to the merged Company partner. Contacts without a company association create standalone res.partner records. The HubSpot email address becomes the res.partner email field and the dedupe key. We use HubSpot's associatedCompany property to resolve the parent_id at migration time. Lifecycle Stage from HubSpot migrates as a res.partner category or customChar field for audit purposes.

HubSpot Companies map to Odoo res.partner with company_type='company'. The HubSpot company domain becomes the website field. Company properties (industry, annual revenue, number of employees) map to custom fields on res.partner that we define before migration. Company is created before any Contact import so that parent_id references are satisfied at the moment of Contact insert.

HubSpot Deals map to Odoo crm.lead records with type='opportunity'. The HubSpot dealstage maps to Odoo crm.stage via a stage name lookup we configure before migration. Closed-Lost and Closed-Won dates from HubSpot become Odoo lost_reason and won_date fields. Probability percentage from HubSpot maps to Odoo's stage_id probability or a manual probability field if the stage probabilities do not align.

Each HubSpot pipeline stage becomes an Odoo crm.stage record within the appropriate crm.team. We configure stage names, sequence order, and probability percentages. If HubSpot has multiple pipelines, we map them to separate Odoo crm.team records with their own stage sequences.

HubSpot's multiple deal pipelines (up to 15 on Professional, 100 on Enterprise) map to separate Odoo crm.team records, each with its own stage sequence. Odoo supports unlimited teams at all tiers, removing the pipeline ceiling that HubSpot enforces at lower tiers.

HubSpot Lead records (Enterprise-only, introduced 2023) map to Odoo crm.lead with type='lead'. The HubSpot lead_status maps to the Odoo crm.stage for leads. Lead score and any custom lead properties migrate as custom fields on crm.lead.

HubSpot Products map to Odoo product.product records with the product type (goods, service) set from HubSpot product type. The HubSpot SKU becomes the Odoo default_code. Product descriptions and URLs migrate as product.description and product.website descriptions respectively.

HubSpot Line Items attached to Deals map to Odoo sale.order.line records. We create a draft sale.order attached to the migrated crm.lead opportunity and populate line items with product_id, product_uom_qty, price_unit, and discount. If the Odoo Sale module is not active, line items attach to crm.lead as custom fields instead.

HubSpot Owners map to Odoo res.users by email match. Any HubSpot Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive HubSpot owners map to Odoo inactive users so that deal and contact assignment history is preserved.

HubSpot email engagements migrate to Odoo mail.message records attached to the res.partner record via model='res.partner' and res_id pointing to the partner id. Email body and subject migrate as mail.message body. The HubSpot timestamp becomes mail.message.date for chronological ordering in the Odoo chatter.

HubSpot call engagements map to Odoo mail.message records with a custom call subtype. Call duration, disposition, and recording URL migrate as custom fields on the mail.message. We set mail.message.date to the original HubSpot timestamp for timeline ordering.

HubSpot meeting engagements map to Odoo calendar.event records. Start datetime, stop datetime, location, and attendee list migrate. Attendees resolve to res.partner records via email match and are added as calendar.event partner_ids. The HubSpot meeting title becomes the calendar.event name.

HubSpot Notes (engagement type NOTE) migrate as Odoo mail.message records attached to the parent res.partner or crm.lead record. The note body migrates as plain text. Attachments on HubSpot notes migrate as Odoo ir.attachment records linked via res_model='res.partner' or 'crm.lead' and res_id pointing to the parent.

HubSpot Task engagements map to Odoo project.task if the Odoo Project module is active and the customer uses project tracking. Otherwise tasks migrate as mail.message records with a task subtype. Status, priority, and due date migrate directly. HubSpot owner assignment resolves to res.users via email match.

HubSpot Tickets migrate to Odoo helpdesk.ticket if the Helpdesk module is active. Ticket pipeline stages map to helpdesk.stage, and ticket properties migrate as custom fields on helpdesk.ticket. If Helpdesk is not active, tickets migrate to crm.lead with a ticket-type tag for manual triage.

HubSpot custom objects (Enterprise-only) require Odoo developer scoping before migration. We create the ir.model definition and the corresponding database table via Odoo developer tools or a Python migration script before importing records. Custom object fields map to ir.model.fields with the appropriate ttype (char, many2one, selection, etc.). This step must complete before any custom object records are migrated and may extend the timeline by 2-4 weeks for complex schemas.

HubSpot tags stored as multi-checkbox contact properties migrate to Odoo res.partner.category (tags) applied to the res.partner record. If the customer has used tags as structured data rather than loose labels, we map them to a custom field (char, selection, or many2many) chosen during scoping. The customer determines the tag strategy before migration.