Migrate from Odoo CRM to HubSpot

Odoo companies stored in res.partner with is_company=True map directly to HubSpot Company records. Odoo's street, city, country, phone, website fields on the partner record map to HubSpot's address properties and Website field. Parent-company hierarchies in Odoo (parent_id on res.partner) map to HubSpot's parent company association.

Odoo individual contacts (is_company=False) map to HubSpot Contact records. The contact's email, phone, mobile, job title (function field in Odoo), and address properties migrate as HubSpot contact properties. Odoo's parent_id on a contact record determines the HubSpot primary CompanyId association.

Odoo's crm.lead serves both lead and opportunity records. We map all crm.lead records to HubSpot Deal objects regardless of Odoo's type flag. Odoo's type distinction is preserved as a HubSpot custom property (lead_type__c) since HubSpot does not have a native equivalent split between lead and deal.

Odoo stage names (New, Qualified, Proposal, Won, Lost, etc.) map value-by-value to HubSpot Deal stage names within a designated pipeline. We create the HubSpot pipeline before migration and apply stage name mappings per stage_id in Odoo's crm.stage table. Stage sequence order is preserved.

Odoo's crm.team records map to HubSpot user team assignments. Team members are resolved by email match against HubSpot users, ensuring that owner assignments translate correctly across platforms. Unmatched team assignments are flagged in the pre-migration audit report so the team can pre-create HubSpot users or assign a fallback owner before the migration run begins.

Odoo activities with category='call' migrate as HubSpot Call engagement records. Original call date, duration (x_duration in Odoo), summary (note field), and owner are preserved. Calls are associated to the corresponding HubSpot contact and deal via the Odoo's res.partner and crm.lead linkages.

Odoo email activities migrate as HubSpot Email engagement records. The email subject, body (mail.message body), timestamp, and direction (inbound/outbound) are mapped to HubSpot email properties. Thread associations from Odoo's mail.thread model are preserved via the HubSpot associations API, ensuring conversation continuity is maintained across the platform migration.

Odoo meeting activities map to HubSpot Meeting records with original start/end timestamps, title (summary field), and body preserved for complete meeting history. Odoo's calendar.event records (if used for scheduled meetings) are also mapped to HubSpot Meetings with the same property set, maintaining calendar context within the CRM.

Odoo notes and generic activities without a specific category migrate as HubSpot Notes, preserving the note body, author, and timestamp for historical reference. Notes are associated to the corresponding HubSpot contact, company, or deal record via the associations API after parent records are migrated.

Odoo quotations (sale.order in draft or sent state) map to HubSpot Quote records with line items, quantities, and pricing transferred from sale.order.line to HubSpot Quote line items. Odoo's discount fields and tax handling require value-mapping per product configuration to ensure pricing accuracy is maintained in the HubSpot quote records.

Odoo attachments on crm.lead and res.partner records migrate as HubSpot Files. We download each attachment from Odoo's filestore and re-upload to HubSpot's file storage, preserving filename, mime type, and original upload date. Files are associated to the target record after upload.

Odoo custom fields on crm.lead (x_studio_*, x_custom_*) migrate as HubSpot custom properties on Deal. Field type translation: char → string, integer/float → number, boolean → bool, date → date, datetime → datetime, selection → enumeration. Odoo many2one fields map to HubSpot string (ID reference) or require a lookup table.

Odoo custom fields on res.partner migrate as HubSpot custom properties on Contact or Company depending on whether the field is defined on individual contact records or company records. Selection fields become HubSpot enumeration properties with exact value lists preserved from the Odoo selection field options.

Odoo's mail.message records on crm.lead objects (internal notes and emails) migrate as HubSpot Notes or Email engagement records based on message type classification. Email subtype messages become HubSpot Emails with full body and headers preserved, while note subtype messages become Notes for internal reference. Author and create date are preserved on both record types.

Odoo's crm.lost_reason model stores named loss reasons per stage. These map to a HubSpot custom pick-list property (lost_reason__c) on the Deal object for consistent loss reason tracking. Each named Odoo reason becomes a HubSpot enumeration value so reporting on loss reasons remains consistent across the migrated dataset.