Skip to content
Get a quote

Odoo CRM to HubSpot migration

Moving from Odoo CRM to HubSpot consolidates your sales and marketing stack into a single platform built for inbound growth. FlitStack AI maps every crm.lead, res.partner record, pipeline stage, and activity to HubSpot contacts, companies, deals, and engagement logs — preserving original create dates, owner assignments, and stage-transition history so your HubSpot reports show the full customer journey from day one.

Short answer

FlitStack AI migrates companies, contacts, deals, deal pipeline stages and team / user assignments from Odoo CRM to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records with clean, standard Odoo data.

By

Source Odoo CRM
DestinationHubSpot
CompanyContactDealDeal Pipeline StageTeam / User Assignment
Mapped field by field · sample run · one-click rollback

What moves from Odoo CRM to HubSpot?

Odoo CRM stores contacts and companies in a single res.partner model with a type flag distinguishing individuals from organizations.

Read the full summary

Deals live in crm.lead with a kanban-stage field that maps directly to HubSpot deal pipelines and stages. HubSpot separates contacts and companies into distinct objects, requires a primary company association per contact, and models deals with a mandatory pipeline + stage pair and a closedate field. We extract Odoo data via the XML-RPC / JSON-RPC external API (available on Odoo Enterprise; Odoo Community uses direct PostgreSQL reads), then map res.partner records into HubSpot contacts and companies, crm.lead records into HubSpot deals, and crm.activity records into HubSpot engagement logs (calls, emails, meetings, tasks, notes). Custom fields on crm.lead and res.partner migrate as HubSpot custom properties. Odoo workflow rules, automation actions, and server actions do not migrate — those must be rebuilt in HubSpot's workflow builder. Our migration runs a sample pass against a HubSpot sandbox before committing the full load, and a 24–48 hour delta-pickup window captures any records modified in Odoo during the cutover.

direct

res.partner (is_company = True) → Company

Odoo companies stored in res.partner with is_company=True map directly to HubSpot Company records.

How it maps

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.

direct

res.partner (is_company = False) → Contact

Odoo individual contacts (is_company=False) map to HubSpot Contact records.

How it maps

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.

merged

crm.lead (type = 'lead' or 'opportunity') → Deal

Odoo's crm.lead serves both lead and opportunity records.

How it maps

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.

value_mapping

crm.stage → Deal Pipeline Stage

Odoo stage names (New, Qualified, Proposal, Won, Lost, etc.) map value-by-value to HubSpot Deal stage names within a designated pipeline.

How it maps

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.

transformed

crm.team → Team / User Assignment

Odoo's crm.team records map to HubSpot user team assignments.

How it maps

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.

direct

crm.activity (category = 'call') → Call

Odoo activities with category='call' migrate as HubSpot Call engagement records.

How it maps

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.

What moves15 objects
Odoo CRMHubSpot
  • res.partnerCompany1:1
  • res.partnerContact1:1
  • crm.leadDealmerged
  • crm.stageDeal Pipeline Stagetransformed
  • crm.teamTeamtransformed
  • crm.activityCall1:1

+ 9 more in the mapping below

How Odoo CRM and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionOdoo CRMHubSpot
Contact-company modelOdoo stores contacts and companies in one res.partner table with a 'is_company' boolean flag. Individual contacts are linked to parent companies via parent_id.HubSpot uses separate Contact and Company objects. Contacts must have a primary CompanyId lookup; multi-company associations require HubSpot's Company Contacts association model.
Lead/opportunity handlingOdoo's crm.lead object serves as both lead and opportunity. A boolean 'type' field (lead/opportunity) and stage_id determine the record state.HubSpot has no split lead/contact model — all people land as Contacts. Deals (Opportunities) are separate objects with their own pipeline and stage.
Pipeline stagesOdoo uses crm.stage records with a sequence number and name. Stages are team-scoped but not formally tied to a named pipeline object.HubSpot requires a named Deal Pipeline. Stages within a pipeline are pick-list values scoped to that pipeline. Multiple pipelines require multiple deal records with pipelineId specified.
Custom field suffixOdoo stores custom field definitions in ir.model.fields. API field names follow Odoo's dot-notation (x_studio_field_name or x_custom_field).HubSpot custom properties use internal names like hs_derived_current_LOB or custom_text_field without a formal __c suffix. The HubSpot API exposes them in the properties bag.
Activity loggingOdoo activities live in crm.activity linked to crm.lead records. Activity types are defined in crm.activity.type with name and category (call, email, meeting, etc.).HubSpot models engagements as Calls, Emails, Meetings, Tasks, and Notes as first-class objects with their own properties and timestamps, linked to contacts and deals via associations.
Data export methodOdoo Enterprise exposes a full XML-RPC / JSON-RPC external API. Odoo Community lacks a standard external API — data extraction requires direct PostgreSQL database reads.HubSpot accepts data via the Contacts API (up to 100 upserts per batch), Companies API, Deals API, and Associations API. Bulk import via CSV is also supported for high-volume loads.
Pricing modelOdoo uses per-user, per-module pricing. A team using CRM, Accounting, and Inventory pays for each app separately. Custom Plan (€17.90/user/month) unlocks the external API.HubSpot prices per-seat per-hub with contact-volume-based billing on the marketing side. Professional and Enterprise tiers unlock custom objects, workflow automation, and API access.

Odoo CRM to HubSpot field mapping

The 30 most-used fields of 50 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
Odoo CRMHubSpot
  1. nameres.partner firstnameContact
  2. nameres.partner lastnameContact
  3. emailres.partner emailContact
  4. phoneres.partner phoneContact
  5. mobileres.partner mobilephoneContact
Odoo CRM fieldHubSpot fieldMappingNote
res.partner.nameContact.firstnametransformedOdoo's single name field splits into firstname and lastname. We attempt to split on space; unparseable names land in lastname with firstname blank.
res.partner.nameContact.lastnametransformedSee firstname mapping — unparseable single-name records land here.
res.partner.emailContact.emaildirect
res.partner.phoneContact.phonedirect
res.partner.mobileContact.mobilephonedirect
res.partner.functionContact.jobtitledirect
res.partner.streetContact.addressdirect
res.partner.cityContact.citydirect
res.partner.state_idContact.statevalue_mappingOdoo state_id is a many2one to res.country.state. We resolve to the state code string for HubSpot.
res.partner.country_idContact.countryvalue_mappingOdoo country_id maps to HubSpot country by ISO code string.
res.partner.zipContact.zipdirect
res.partner.websiteContact.websitedirect
res.partner.commentContact.notes_last_contacteddirect
res.partner.create_dateContact.original_create_date__ccustom_field_requiredHubSpot sets Createdate at import time. Original Odoo create_date is preserved as custom datetime field.
res.partner.write_dateContact.lastmodifieddatedirect
res.partner.idContact.source_system_partner_id__ccustom_field_requiredOdoo res.partner integer ID stored for traceability and delta-run deduplication.
res.partner.parent_idContact.associatedcompanyidtransformedOdoo parent_id on a non-company res.partner maps to HubSpot associatedcompanyid. The parent must be migrated as a HubSpot Company first.
res.partner (is_company).nameCompany.namedirect
res.partner (is_company).websiteCompany.websitedirect
res.partner (is_company).phoneCompany.phonedirect
res.partner (is_company).streetCompany.addressdirect
res.partner (is_company).cityCompany.citydirect
res.partner (is_company).country_idCompany.countryvalue_mappingOdoo country_id maps to HubSpot country by ISO code string.
res.partner (is_company).industry_idCompany.industryvalue_mappingOdoo industry_id (many2one to res.partner.industry) maps to HubSpot industry pick-list values.
res.partner (is_company).employee_countCompany.numberofemployeesdirect
res.partner (is_company).idCompany.source_system_company_id__ccustom_field_requiredOdoo res.partner integer ID stored on the company for traceability.
crm.lead.nameDeal.dealnamedirect
crm.lead.partner_idDeal.associations__contact_idtransformedOdoo partner_id (res.partner) resolves to the migrated HubSpot Contact ID and associates via HubSpot's Deals-Contacts association.
crm.lead.expected_revenueDeal.amountdirect
crm.lead.probabilityDeal.hs_deal_probabilitydirect

What to watch for in a Odoo CRM to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

res.partner N:N associations collapse to primary CompanyId in HubSpot

Odoo permits a contact to have multiple parent companies via multiple res.partner records linked to the same contact through parent_id, or via an intermediate link table.

How we handle it

HubSpot's Contact-Company association model supports multiple companies per contact through the associations API, but the import must be sequenced: we migrate all Company records first, then associate each Contact to its companies. If Odoo stores a contact-company relationship only as a shared crm.lead (the contact is linked to a deal which is linked to a company), we surface this during the mapping audit and provide a manual association plan.

high

Odoo Community lacks an external API — extraction requires direct database access

Odoo Enterprise exposes a full XML-RPC and JSON-RPC external API with search_read, read, and write methods.

How we handle it

Odoo Community does not expose this API — only Odoo Online on a Custom Plan ($17.90/user/month) unlocks external API access. For Odoo Community migrations, FlitStack reads directly from the PostgreSQL database. This requires read-only database credentials and a static database snapshot or read replica to avoid impacting a live Odoo instance. We disclose this limitation upfront and scope it as a separate technical workstream.

high

HubSpot's deal model requires a named pipeline before any deal can be created

HubSpot requires at least one Deal Pipeline to exist before Deals API calls will succeed.

How we handle it

If no pipeline is pre-created in the HubSpot portal, the migration will fail all deal upserts. We create the target pipeline in HubSpot before running any deal migration, using Odoo's crm.stage records as the stage definition source. Teams with multiple Odoo sales teams (multiple crm.team records) must decide whether to map them to a single HubSpot pipeline with stage scoping or multiple pipelines — this is a schema decision made during the mapping audit.

medium

Original create dates cannot be set in HubSpot — only preserved as custom properties

HubSpot's Createdate timestamp is set by the platform at record creation time during import and cannot be backdated via API.

How we handle it

Odoo's create_date on res.partner and crm.lead records cannot be replicated as the actual created date in HubSpot. We preserve the original Odoo create_date as a custom datetime property (original_create_date__c) on both Contact and Deal records. Odoo's write_date maps directly to HubSpot's lastmodifieddate. Historical reporting that relies on original create date must query the custom property rather than the system timestamp.

medium

Odoo lost_reason_id on crm.lead requires pre-existing HubSpot pick-list values

HubSpot custom pick-list properties must have their allowed values defined before records are imported.

How we handle it

If Odoo's crm.lost_reason records contain values not yet added to HubSpot's closed_lost_reason__c custom property, the import will silently drop those values or error depending on the API configuration. We audit Odoo's crm.lost_reason values during the mapping phase, create the corresponding HubSpot enumeration values before the migration run, and flag any mismatches as a manual decision item.

How the migration runs

  1. Audit Odoo data model and extract schema

    FlitStack connects to Odoo (via external API for Enterprise/Custom Plan, or via read-only PostgreSQL access for Community) and pulls the complete schema: all res.partner fields, all crm.lead fields, crm.stage definitions, crm.team records, crm.activity types, and ir.model.fields for custom field names and types.

    What this step covers

    We generate a data audit report showing record counts per object, custom field inventory, blank/null rates, and parent-child relationship depth. This audit identifies Odoo Community database access requirements and flags any fields that cannot be extracted via standard API methods.

  2. Map schema and configure HubSpot destination

    We translate Odoo's object model to HubSpot objects (res.partner → Contact + Company, crm.lead → Deal, crm.activity → Call/Email/Meeting).

    What this step covers

    Custom fields from Odoo are created as HubSpot custom properties with appropriate type translations. We create the HubSpot Deal Pipeline and stages using Odoo's crm.stage names as the source. Owner resolution by email is configured: Odoo user IDs are matched against HubSpot user emails, and unmatched owners are flagged with a fallback assignment recommendation.

  3. Migrate companies first, then contacts, then deals

    HubSpot requires Companies to exist before Contacts can associate via associatedcompanyid, and Contacts to exist before Deals can associate contact roles.

    What this step covers

    We sequence the migration: (1) all res.partner records where is_company=True migrate as HubSpot Companies, (2) all res.partner records where is_company=False migrate as HubSpot Contacts with primary company associations resolved, (3) all crm.lead records migrate as HubSpot Deals with contact associations and stage mapping. Activities and attachments migrate after parent records are in place, maintaining referential integrity throughout.

  4. Run a sample migration with field-level verification

    A representative slice — typically 200–500 records covering the range of contact types, deal stages, and activity categories — migrates to a HubSpot sandbox or test portal.

    What this step covers

    We generate a field-level diff report comparing Odoo source values against the migrated HubSpot values for every mapped field. You review the diff and confirm field mapping correctness, lost-reason value coverage, owner resolution rates, and date preservation before the full run commits.

  5. Execute full migration with delta-pickup cutover window

    The full dataset migrates to HubSpot with real-time progress tracking and QA checkpoints after each object batch.

    What this step covers

    During the migration, your Odoo team continues working. After the primary migration completes, a 24–48 hour delta-pickup window captures any Odoo records created or modified during the cutover, applying the same field mappings and transformations. An audit log records every upsert, association, and transformation. If reconciliation identifies issues, one-click rollback reverts the HubSpot environment to the pre-migration state.

  6. Post-migration validation and workflow rebuild handoff

    FlitStack runs automated validation scripts comparing record counts, field completeness, and association integrity between the Odoo snapshot and HubSpot state.

    What this step covers

    Spot-check verification covers deals at each stage, contacts with attachments, and activity logs. We deliver an export of your Odoo workflow and automation definitions as a structured reference document for your HubSpot admin to use when rebuilding rules in HubSpot's workflow builder. A 30-day post-migration support window covers any data discrepancies discovered after go-live.

Odoo CRM HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 25,000 records with clean, standard Odoo dataTypical, smaller accounts
7–14 days for 100,000+ records or Odoo setups with extensive custom fields, multi-company structures, or heavy crm.activity historyLarge or heavily customised accounts

Costs scale up when Odoo's res.partner table has deep parent_id hierarchies requiring HubSpot company-contact association rebuilding, when crm.activity history is extensive (hundreds of thousands of logged calls and emails), or when Odoo custom fields on crm.lead number more than 30 and need individual HubSpot custom property creation. Schema complexity and custom object count drive the final scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Odoo CRM to HubSpot →

Why teams move from Odoo CRM to HubSpot

  • Odoo's res.partner-based model conflates contacts and companies in one table, forcing custom reporting workarounds to separate customer types. HubSpot's separate Contact and Company objects provide clearer segmentation, especially for B2B teams managing accounts with multiple stakeholders. This architectural difference simplifies segmentation queries and enables more precise pipeline reporting without complex filtering logic.
  • Integrating Odoo CRM with external email (Gmail, Outlook) requires additional configuration and often drops threads or loses association links. HubSpot's native email tracking, logging, and conversation view are built into the CRM without add-ons, reducing the risk of fragmented communication history and ensuring that every email interaction is automatically attached to the correct contact and deal record.
  • Odoo pricing scales per-module and per-user — teams that started on CRM find costs escalating as they add Sales, Accounting, or Inventory. HubSpot's unified platform model reduces per-module overhead at mid-market scale, consolidating sales, marketing, and service tools under a single subscription with predictable per-seat pricing that avoids the compounding cost structure of modular licensing.
  • Reporting in Odoo requires navigating separate apps for CRM versus Accounting versus Inventory, creating data silos that slow down analysis. HubSpot's reporting hub, revenue attribution, and forecasting tools sit within one CRM, giving sales leaders faster access to pipeline analytics without cross-application context switching or manual data reconciliation between disconnected systems.
  • Teams adopting Odoo often discover that its open-source flexibility creates dependency on specific developers or partners for customizations and updates. HubSpot's no-code configurability and established partner ecosystem reduce long-term lock-in risk for growing sales teams, allowing internal administrators to maintain and extend the system without specialized developer resources.

Questions, answered

Odoo CRM to HubSpot migration questions

How long does an Odoo CRM to HubSpot migration take?

Most Odoo CRM to HubSpot migrations complete within 48–72 hours for under 25,000 total records. Larger datasets with 100,000+ records, extensive crm.activity history, or Odoo Community setups (which require direct PostgreSQL extraction) extend to 7–14 days. The longest single step is typically the mapping audit and HubSpot pipeline configuration, which precedes data movement. Odoo Community database extraction requires a static snapshot or read replica to avoid impacting a live database.

Will my Odoo CRM workflows and automation rules migrate to HubSpot?

No. Odoo server actions, automated actions, workflow rules, and base.automation records do not migrate to HubSpot. They must be rebuilt in HubSpot's workflow and automation builder. We extract your Odoo workflow definitions as a structured reference document (action names, trigger conditions, assigned activities, and stage-change rules) so your HubSpot admin has a rebuild blueprint. Email templates and inbox rules from Odoo's mail.channel model also do not migrate and must be recreated in HubSpot's email sequences and inbox settings.

What happens to Odoo crm.lead stages in HubSpot?

Odoo's crm.stage records (New, Qualified, Proposal Sent, Won, Lost, etc.) become HubSpot Deal Pipeline stages. We create a named HubSpot Deal Pipeline before migration and map each Odoo stage name to a corresponding HubSpot stage. Stage sequence, probability percentages, and stage IDs are preserved. If your Odoo setup has multiple crm.team records with different stage sets, we discuss whether to use a single HubSpot pipeline with filtered views or multiple pipelines with separate stage configurations.

Can I migrate Odoo custom fields on crm.lead to HubSpot custom properties?

Yes. Odoo custom fields defined on crm.lead (x_studio_* or x_custom_* naming in the database, or custom fields created via Studio) migrate as HubSpot custom properties on Deal. Field types are translated: Odoo char/text maps to HubSpot string, integer/float to number, boolean to bool, date/datetime to date/datetime, and selection fields to HubSpot enumeration with exact value lists. Odoo many2one fields (e.g., a custom field pointing to res.partner) are mapped as string fields containing the Odoo record ID and require a manual review if they represent a meaningful reference that should be preserved as a HubSpot association.

How does FlitStack handle Odoo Community database access for migrations?

Odoo Community does not expose the external API — only Odoo Enterprise and Custom Plan do. For Odoo Community migrations, FlitStack connects directly to the PostgreSQL database using read-only credentials. We work from a static database snapshot or a read replica to avoid impacting a live system. We read ir.model.fields for schema definitions, res_partner for contacts and companies, crm_lead for deals, crm_activity for activities, and ir_attachment for files. This approach is disclosed in the scoping document and adds a separate technical workstream to the migration plan.

Does the migration affect my Odoo account during cutover?

No. FlitStack uses read-only access on Odoo during migration — your team continues working in Odoo throughout the process. For Odoo Enterprise with external API access, we use search_read calls only, which do not write to Odoo. For Odoo Community via PostgreSQL, we connect to a read replica or static snapshot. A delta-pickup window (typically 24–48 hours after the primary migration) captures any records created or modified in Odoo during the cutover window and applies the same field mappings to those records in HubSpot.

What happens to Odoo quotations and sale orders in HubSpot?

Odoo quotations (sale.order records in draft or sent state) migrate as HubSpot Quote records with line items, pricing, and discount information. We map sale.order.line records to HubSpot Quote line items. Odoo sale orders that have been confirmed (state = 'sale') are migrated as HubSpot Quotes with a closed status reflecting the confirmed state. Recurring subscription or rental orders from Odoo's sale_subscription or sale_rental apps do not have a direct HubSpot equivalent — these are preserved as custom properties on the associated Deal for manual rebuild in HubSpot's subscription tools.

Get a quote

Moving from Odoo CRM to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote