HubSpot to Odoo CRM migration
We migrate Contacts, Companies, Deals, and Activity history from HubSpot Sales Hub into Odoo CRM with the Contact-Company merge resolved during scoping, pipeline stages mapped to Odoo opportunity stages, and the HubSpot workflow and sequence inventory delivered as a written rebuild guide for Odoo Server Actions.
FlitStack AI migrates res.partners, crm.leads, crm.stages, crm.teams and product.products from HubSpot to Odoo CRM, 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: 3-5 weeks.

What moves from HubSpot to Odoo CRM?
Moving from HubSpot Sales Hub to Odoo CRM is an architectural shift from a marketing-first CRM with separate engagement tools to an ERP-embedded CRM where sales, accounting, inventory, and operations share a single database.
Read the full summary
HubSpot separates Contacts and Companies as distinct objects with a many-to-many relationship; Odoo merges these into a single Contact record with an optional company field and partner_id field that represents both the person and the organization. We extract Contacts and Companies from HubSpot, merge them on domain or name, and land them as Odoo Contacts with the appropriate partner_category and company_type set. HubSpot Deals map to Odoo CRM Opportunities plus calendar.Events for stage-change milestones. Activity history (calls, emails, meetings, tasks) migrates as chatters and mail.message records threaded to the correct res.partner record. We do not migrate HubSpot Workflows or Sequences as Odoo Server Actions or Automations because the trigger models differ; we deliver a written inventory of every automation requiring rebuild. Odoo custom objects are available through developer-defined models rather than a self-serve UI, so any HubSpot Enterprise custom objects require Odoo developer scoping before migration begins.
Contact → res.partner (company_type = 'contact')
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.
How it maps
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.
Company → res.partner (company_type = 'company')
HubSpot Companies map to Odoo res.partner with company_type='company'.
How it maps
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.
Deal → crm.lead (type = 'opportunity')
HubSpot Deals map to Odoo crm.lead records with type='opportunity'.
How it maps
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.
Deal Stage → crm.stage
Each HubSpot pipeline stage becomes an Odoo crm.stage record within the appropriate crm.team.
How it maps
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.
Pipeline → crm.team
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.
How it maps
Odoo supports unlimited teams at all tiers, removing the pipeline ceiling that HubSpot enforces at lower tiers.
Lead (Sales Hub Enterprise) → crm.lead (type = 'lead')
HubSpot Lead records (Enterprise-only, introduced 2023) map to Odoo crm.lead with type='lead'.
How it maps
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.
- Contactres.partner1:1
- Companyres.partner1:1
- Dealcrm.lead1:1
- Deal Stagecrm.stagetransformed
- Pipelinecrm.teamtransformed
- Leadcrm.lead1:1
+ 11 more in the mapping below
How HubSpot and Odoo CRM 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.
| Dimension | HubSpot | Odoo CRM |
|---|---|---|
| Contact and Company model | Separate Contact and Company objects with many-to-many association table | Single res.partner model with company_type = 'contact' or 'company' and optional parent_id for hierarchy |
| Lead vs Contact model | Single Contact object with Lifecycle Stage property | Opportunity and Lead object in Odoo CRM with stage pipeline, no explicit lead-convert split |
| Deal to Opportunity mapping | Deals as standalone objects with pipeline stage and probability | crm.lead as Opportunity with stage_id; deal-level scheduling maps to calendar.Event records |
| Custom objects | Enterprise tier only ($150/seat/mo + $3,500 onboarding) | Developer-defined ir.model records via Odoo Studio or Python models; no self-serve UI at any tier |
| Pricing model | Per-seat plus Marketing Contacts metering on the marketing layer | Per-user, per-module pricing: CRM Standard ~€11.90/user/mo, Custom ~€17.90/user/mo |
| Workflow automation | Property-triggered Workflows with visual builder, gated at Professional | Server Actions and Automated Actions via ir.actions.server; no workflow designer UI at Community tier |
| App ecosystem | HubSpot App Marketplace with ~1,700 listings | Odoo Apps Store with 40,000+ listings across ERP and CRM modules |
What to watch for in a HubSpot to Odoo CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
HubSpot custom objects require Odoo developer scoping
HubSpot Enterprise custom objects have no self-serve equivalent in Odoo.
How we handle it
Odoo's custom object model (ir.model) requires developer-level access to create, and the fields must be defined through Odoo Studio or Python code before records can be imported. Migrations with HubSpot Enterprise custom objects add 2-4 weeks of developer scoping and schema setup before any data movement begins. We flag this at scoping and scope it as a separate developer engagement if Odoo Studio is insufficient for the schema complexity.
HubSpot Workflows and Sequences do not migrate to Odoo Server Actions
HubSpot property-triggered Workflows and Professional-gated Sequences have a different trigger model from Odoo Server Actions and Automated Actions.
How we handle it
HubSpot Workflows react to property value changes on a record; Odoo Server Actions react to ir.cron scheduled events or ir.actions.server record-triggered events with different condition syntax. We do not migrate them as code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger, conditions, actions, and a recommended Odoo Server Action equivalent. The customer's Odoo admin or a certified Odoo partner rebuilds them post-migration.
HubSpot's marketing contact billing flag has no Odoo equivalent
HubSpot's Marketing Contacts billing model (a flag that determines whether a contact is counted against the marketing-priced contact tier) has no direct Odoo equivalent because Odoo does not have a contact-based billing model.
How we handle it
All migrated contacts land as standard Odoo res.partner records without a billing-tier flag. We preserve the HubSpot marketing contact status in a customChar field on res.partner for audit and reporting so that if the customer later evaluates marketing automation tools, the segmentation is preserved.
HubSpot's native CSV importer limits apply on the source side only
HubSpot's CSV importer cannot move calls, emails, meetings, tasks, or file attachments.
How we handle it
We use the HubSpot CRM API for these objects, respecting the token-bucket rate limits (100-200 req/10sec burst, 4 req/sec on search endpoint) with exponential backoff and jitter. For accounts with large engagement histories (over 300,000 activity records), this extraction phase can take 5-10 business days on its own. We scope the API extraction separately and include estimated extraction time in the project plan.
Odoo self-hosted deployments require additional migration scoping
If the destination is an Odoo self-hosted (on-premises) deployment rather than Odoo Online (SaaS), the migration involves additional steps: database provisioning, server access and credentials, SSL certificate setup, email domain configuration, and an outgoing mail server (SMTP) configuration.
How we handle it
We scope these as part of the discovery phase and include server setup verification in the pre-migration checklist. Migrations to Odoo Online (SaaS) are more straightforward but still require Odoo partner account setup and module installation on the target database.
How the migration runs
Discovery and HubSpot tier audit
We audit the source HubSpot portal across tier (Starter/Professional/Enterprise), custom properties, custom objects, pipeline count, active sequences, active workflows, and engagement volume.
What this step covers
We identify all HubSpot objects with data (Contacts, Companies, Deals, Leads, Products, Tickets, Engagements) and estimate record counts per object. We pair this with an Odoo readiness check: which Odoo apps are active in the target database (CRM, Sale, Project, Helpdesk), which Odoo tier the target is on (Community/Standard/Custom), and whether the target is Odoo Online or self-hosted. The discovery output is a written migration scope, record count estimate, and an Odoo module activation plan.
Schema design and Odoo field mapping
We design the destination schema in Odoo.
What this step covers
This includes activating the required modules (CRM, Sale, possibly Project and Helpdesk), creating custom fields on res.partner and crm.lead to capture HubSpot properties that have no direct Odoo equivalent, configuring crm.team records to match HubSpot pipelines, configuring crm.stage records with probability percentages aligned to HubSpot dealstage values, and defining any custom ir.model records for HubSpot custom objects. Custom fields are created via Odoo Studio or developer access before any data import.
Contact-Company merge logic and data cleaning
We extract HubSpot Contacts and Companies in parallel, build a domain-to-partner lookup table for the Company merge, and apply the merge logic: Contacts with an associated Company get company_type='contact' with parent_id pointing to the merged res.partner; Contacts without an association create standalone res.partner records.
What this step covers
We clean data in transit: duplicate email addresses, missing required fields (name, email), and invalid formats for fields that Odoo validates (email format, phone format). The cleaned output is a set of CSVs ready for Odoo XML-RPC import.
Owner reconciliation and user provisioning
We extract every distinct HubSpot Owner referenced on Contact, Company, Deal, and Engagement records and match by email against the Odoo target database's res.users table.
What this step covers
Owners without a matching user go to a reconciliation queue for the customer's Odoo admin to provision. Inactive HubSpot owners map to inactive Odoo users so that historical assignment is preserved even if the original rep is no longer active. Migration cannot proceed past this step because partner and opportunity assignment depends on resolved user records.
Production migration in dependency order
We run production migration in record-dependency order: res.partner (Companies first, then Contacts), crm.lead (Opportunities from Deals, Leads from HubSpot Leads), product.product (Products), sale.order.line (Line Items from Deals), mail.message (Activity history via XML-RPC in batches of 500-1000 records), calendar.event (Meetings), ir.attachment (File attachments), helpdesk.ticket (Tickets if Helpdesk is active), and custom object records (last, after ir.model schema is confirmed).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze HubSpot writes during the cutover window, run a final delta migration of any records modified during the migration period, then enable Odoo as the system of record.
What this step covers
We deliver the Workflow and Sequence inventory document to the customer's Odoo admin or certified Odoo partner. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild HubSpot Workflows as Odoo Server Actions inside the migration scope; that work is scoped as a separate engagement with an Odoo partner.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, the degree of Contact-Company merge required, and whether HubSpot custom objects need Odoo developer scoping. Odoo subscription cost (typically €11.90-€17.90 per user per month) and any Odoo Apps Store module purchases sit outside the migration fee. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for HubSpot to Odoo CRM →Why teams move from HubSpot to Odoo CRM
- HubSpot's per-seat plus Marketing Contacts billing model creates unpredictable costs as contact databases grow. A team with 20,000 contacts paying for Sales Hub Professional at $100/seat for 10 users is also paying for Marketing Hub contacts on top. Odoo CRM at ~€11.90/user/month for the standard CRM module has no contact-based metering and no separate marketing billing layer, making total cost more predictable for teams that have accumulated large contact databases over years.
- Teams using HubSpot alongside a separate ERP or accounting system (QuickBooks, Xero, NetSuite) migrate to Odoo to eliminate the dual-platform problem. Manual handoffs, duplicated data, and broken workflows between HubSpot CRM and a separate ERP create operational friction that a single Odoo instance resolves. Doodex migration consultants and Reddit reviewers cite consolidation and cost as the primary motivation for the switch.
- HubSpot's Workflow and automation tools require Professional tier at $100/seat and become increasingly complex to maintain as the sales process scales. Odoo Server Actions and Automated Actions are available at all tiers (Community through Enterprise) and offer equivalent record-triggered and scheduled automation without the per-seat gating. Teams that hit the workflow complexity wall at scale move to Odoo for the automation flexibility at a lower tier.
- HubSpot's native CSV importer cannot move calls, emails, meetings, tasks, or attachments, and HubSpot's API rate limits (100-200 req/10sec burst, 4 req/sec on search) restrict bulk migration without careful job queuing. Odoo receives HubSpot data through its XML-RPC API with configurable batch sizes and does not enforce HubSpot-style token-bucket limits on the outbound side, making the extraction from HubSpot the actual constraint rather than the destination write speed.
- Odoo's open-source architecture and self-hosted deployment option appeal to teams that want data residency control, no per-contact billing, and the ability to modify the source code. HubSpot is exclusively SaaS with no self-hosted option and enforces tier-based feature gating that forces upgrades when teams outgrow the base plan. Reviewers on G2 and Software Advice cite the SaaS-only model and lack of customization depth as reasons to evaluate Odoo.
Questions, answered
HubSpot to Odoo CRM migration questions
How long does a HubSpot Sales Hub to Odoo CRM migration take?
Most migrations land between three and five weeks for accounts under 20,000 Contacts and 5,000 Deals with no custom objects. Migrations with HubSpot Enterprise custom objects, complex multi-pipeline Deal structures, large engagement histories (over 300,000 activity records), or Odoo self-hosted deployment move to eight to fourteen weeks because of developer schema scoping, API extraction time from HubSpot, and Odoo Server Action rebuild documentation. Odoo self-hosted deployments add 1-2 weeks for server provisioning and environment setup.
Do my HubSpot Workflows and Sequences migrate to Odoo?
No. HubSpot Workflows and Sequences are not migrated as Odoo Server Actions or Automated Actions because the trigger models differ structurally. HubSpot Workflows react to property value changes with a visual builder; Odoo Server Actions use ir.actions.server with different condition syntax and cron-based scheduling. We do not migrate them as code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger, conditions, actions, and a recommended Odoo Server Action equivalent. The customer's Odoo admin or a certified Odoo partner rebuilds them post-migration.
Can we keep HubSpot for marketing while moving sales to Odoo CRM?
Yes. A hybrid stack is a common pattern. HubSpot Marketing Hub continues to handle inbound, email marketing, and lead capture; Odoo CRM handles the sales process from lead onward. We configure a HubSpot-to-Odoo integration (via Odoo Apps Store connectors or a custom API integration) during migration so that new HubSpot contacts flow into Odoo as res.partner records. The customer continues paying for HubSpot Marketing Hub at the marketing layer while moving sales seat licensing to Odoo. We scope the integration separately from the migration.
Do we lose historical engagement data (calls, emails, meetings, tasks)?
No. We migrate the full engagement history from HubSpot via the CRM API in chronological batches. Emails, calls, notes, and tasks land as Odoo mail.message records attached to the res.partner record via the chatter interface. Meetings land as calendar.event records with attendees resolved to res.partner records by email. Activity timeline ordering is preserved by setting mail.message.date to the original HubSpot timestamp. The chatter shows the full conversation history on each contact record in Odoo.
What happens to HubSpot's custom objects?
HubSpot custom objects (available on Sales Hub Enterprise) require Odoo developer scoping before migration because Odoo does not have a self-serve custom object UI. We create the ir.model definition and corresponding database table through Odoo developer tools or a Python migration script before importing any custom object records. This step adds 2-4 weeks of developer work for complex schemas. We scope this separately from the standard migration and coordinate with the customer's Odoo developer or certified Odoo partner.
How do we handle the HubSpot Marketing Contacts billing flag?
The Marketing Contacts billing flag is HubSpot-specific and has no Odoo equivalent because Odoo does not use contact-based billing. We preserve the HubSpot marketing contact status in a customChar field (e.g., hs_marketing_contact_status) on the migrated res.partner record so that the segmentation data is not lost. Email opt-in and opt-out preferences migrate to Odoo's mail.thread.optout field if the Odoo mass mailing module is active, allowing the customer's Odoo admin to manage email preferences without needing HubSpot.
Can FlitStack AI handle migration to Odoo Online and Odoo.sh (cloud)?
Yes. We migrate to both Odoo Online (SaaS) and Odoo.sh (Odoo's cloud development and hosting platform). For Odoo.sh, we provision access to the customer's GitHub-connected repository, run the migration in a staging branch, and deploy via Odoo.sh's CI/CD pipeline. For Odoo Online, we use XML-RPC API access to the customer's database. We confirm the deployment target during discovery and include the appropriate API access requirements in the pre-migration checklist.
Related migrations
Odoo implementation
Set up Odoo CRM and migrate into it as one engagement.
See the service → Odoo CRM to HubSpotThe same pair in reverse Jonas Enterprise Service & Construction Software to Odoo CRMMapping · history · rollbackMailchimp to Odoo CRMMapping · history · rollbackSuiteCRM to Odoo CRMMapping · history · rollbackPipedrive to Odoo CRMMapping · history · rollbackSalesforce to Odoo CRMMapping · history · rollbackZoho CRM to Odoo CRMMapping · history · rollback HubSpot to SalesforceMapping · history · rollbackHubSpot to Zoho CRMMapping · history · rollbackHubSpot to PipedriveMapping · history · rollbackSources: official documentation
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
- Data Cleaning — Odoo 19.0 documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
Get a quote
Moving from HubSpot to Odoo CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.
Get a quote