How long does an Odoo Marketing Automation to HubSpot migration take?

Small Odoo CRM setups with under 25,000 contacts and standard fields typically complete in 2–3 days. Mid-size migrations with custom fields, marketing activity history, and campaign data extend to 1–2 weeks. Large Odoo instances spanning CRM, marketing automation, and ERP modules with 250,000+ records require 4–8 weeks for full discovery, mapping, testing, and execution. The Odoo XML-RPC API rate limit (~1 request/second) is the primary throughput constraint on large datasets.

Will my Odoo marketing automation workflows migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Odoo marketing automation workflows, email templates, campaign traces, and marketing activity records do not have structural equivalents in HubSpot. They must be rebuilt in HubSpot's workflow builder and email template editor. We export your Odoo workflow definitions and email template content as structured documentation so your HubSpot admin can use them as a step-by-step rebuild specification. This export covers campaign enrollment rules, trigger conditions, time delays, and action sequences.

What does my Odoo lead status and opportunity stage become in HubSpot?

Odoo lead status (new, assigned, qualified, lost, won) maps to HubSpot's lifecycle_stage contact property. Unconverted Odoo leads land as HubSpot contacts with lifecycle_stage set to 'lead' or 'MQL' depending on the Odoo stage value. Odoo opportunities with a won stage land with lifecycle_stage set to 'customer'. The original Odoo stage name is preserved in a custom property for reference. Probability values and forecast categories are taken from HubSpot's stage definitions and applied during the deal migration.

Can I migrate Odoo custom fields and custom models to HubSpot?

Yes. Odoo custom fields created via Studio or ir.model.fields map to HubSpot custom properties on the standard CRM objects (Contact, Company, Deal). Odoo custom models with their own data tables require HubSpot custom objects, which are available on the Enterprise tier. N:N relationships between Odoo custom models map to HubSpot associations or junction custom objects. We document every custom field and model during discovery and include them in the field mapping deliverable before the migration runs.

What happens to my Odoo email templates and campaign data?

Odoo email templates (mail.template model) cannot be imported into HubSpot's template format — the template HTML, dynamic fields, and styling are platform-specific. We export the template content and structure as a reference document for your HubSpot team to recreate in HubSpot's email template editor. Odoo campaign records migrate as HubSpot campaign objects (for reporting containers) and campaign enrollment history is preserved as a custom contact property listing each campaign name and enrollment date.

Does the migration affect my Odoo account during the cutover?

No. FlitStack AI uses scoped read access on Odoo's XML-RPC external API — your team continues working in Odoo throughout the migration. No write operations are performed on Odoo. A delta-pickup window of 24–48 hours after the full migration run captures any contacts, deals, or activities created or modified in Odoo during the cutover so HubSpot reflects Odoo's final state at go-live. All operations are logged in an audit trail with record-level timestamps.

What happens to my Odoo lost-deal reasons in HubSpot?

Odoo deal loss reasons (lost_reason_id on crm.lead) migrate to a custom HubSpot deal property called lost_reason. This property must be created in HubSpot before migration because HubSpot does not have a native loss-reason field on deals. We map each Odoo loss reason value to the HubSpot custom property value-by-value. After migration, your team can use the loss reason data in HubSpot deal reports to identify patterns in lost opportunities and adjust the sales process accordingly.

Odoo Marketing Automation to HubSpot Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Odoo Marketing Automation operates as one module within the broader Odoo ERP suite, where CRM contacts, leads, and opportunities share a unified object model with marketing campaigns and activity logs. HubSpot splits these into its own CRM object model: contacts with lifecycle_stage properties, companies, and deals with per-pipeline stages. The migration carries everything Odoo stores natively — contacts, companies, opportunities, activity history, campaign membership records, and custom fields — into HubSpot's object graph. HubSpot has no equivalent to Odoo's marketing automation workflows, email templates, or campaign activity traces; those must be rebuilt in HubSpot's workflow builder using FlitStack's exported definitions as a reference guide. We use Odoo's XML-RPC external API (available on the Custom plan at 1 request/second) and HubSpot's CRM API (5 requests/second) to extract and land the data, sequencing imports so foreign-key relationships resolve correctly before deals land against resolved contact and company records. Our migration methodology ensures referential integrity by loading parent records before children, mapping Odoo's unified object structure to HubSpot's segmented schema while preserving all business-relevant data relationships and historical context.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Object mapping

How Odoo Marketing Automation objects map to HubSpot

Each row shows how a Odoo Marketing Automation object lands in HubSpot, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Odoo Marketing Automation

res.partner (Contact type)

maps to

HubSpot

Contact

1:1

Fully supported

Odoo partners of type 'contact' map directly to HubSpot contacts. The email address is the primary key for de-duplication and owner resolution. Unmatched emails are flagged before migration so your team can clean up duplicates in Odoo before the export runs.

Odoo Marketing Automation

res.partner (Lead type)

maps to

HubSpot

Lead / Contact

1:many

Fully supported

Odoo leads that have not converted to opportunities land as HubSpot contacts with lifecycle_stage set to 'lead'. Odoo leads that have converted to opportunities land with lifecycle_stage set to 'customer' since the Odoo opportunity record implies a won or active deal.

Odoo Marketing Automation

crm.lead (Opportunity)

maps to

HubSpot

Deal

1:1

Fully supported

Odoo opportunities map to HubSpot deals. The deal name, amount, expected close date, and stage are migrated directly. Pipeline and stage names require value-by-value mapping since Odoo stage names are free-text while HubSpot stage names are scoped per pipeline. We preserve the Odoo stage sequence and probability weights to maintain reporting continuity in your HubSpot dashboards.

Odoo Marketing Automation

crm.lead.team

maps to

HubSpot

HubSpot team / Sales team

1:1

Fully supported

Odoo sales teams map to HubSpot sales teams. If your Odoo instance uses team-based assignments, those resolve to HubSpot team ownership on deals. Teams must be created in HubSpot before migration or records land without a team association. This ensures proper deal ownership distribution across your sales organization after cutover.

Odoo Marketing Automation

crm.stage

maps to

HubSpot

Deal pipeline stage

1:1

Fully supported

Odoo CRM stages map to HubSpot deal stage values. Each Odoo stage receives a corresponding HubSpot stage within the mapped pipeline. Probability values, forecast categories, and stage-entered timestamps are preserved as HubSpot deal properties for reporting continuity. The mapping ensures your pipeline analytics reflect the same stage progression as your original Odoo setup.

Odoo Marketing Automation

crm.lead (Lead status field)

maps to

HubSpot

Contact lifecycle_stage property

1:1

Fully supported

Odoo lead status values (new, assigned, qualified, lost, won) map to HubSpot lifecycle_stage values. HubSpot's default lifecycle stages (subscriber through evangelist) are used; Odoo-specific stage labels are mapped to the closest HubSpot equivalent or stored as a custom property for reference.

Odoo Marketing Automation

res.partner (Company type)

maps to

HubSpot

Company

1:1

Fully supported

Odoo company-type partners map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue migrate directly. HubSpot requires at least one contact to associate with a company — contacts without a primary company in Odoo are attached to a default placeholder company in HubSpot.

Odoo Marketing Automation

marketing.marketing (Campaign)

maps to

HubSpot

Campaign

1:1

Fully supported

Odoo marketing campaigns map to HubSpot campaigns. Campaign name, description, and state are migrated. HubSpot campaign membership (which contacts enrolled in which campaign) is preserved as a custom contact property, since HubSpot campaigns track UTM source attribution rather than workflow enrollment history.

Odoo Marketing Automation

marketing.trace.emails / marketing.trace.sms

maps to

HubSpot

Engagement / Timeline notes

1:1

Fully supported

Odoo marketing activity traces (email opens, clicks, bounces, SMS sends) migrate as HubSpot engagement records or timeline notes on the associated contact. Original activity timestamps and campaign attribution are preserved. Note that HubSpot's engagement model differs from Odoo's trace model — the mapping preserves the fact of the interaction rather than the full trace record.

Odoo Marketing Automation

mail.message / mail.activity

maps to

HubSpot

Engagement / Timeline

1:1

Fully supported

Odoo email history and logged activities map to HubSpot engagements. Calls, emails, meetings, and notes on Odoo contacts and opportunities become HubSpot engagements on the equivalent contact or deal record. Original timestamps, subjects, and owner assignments are preserved to maintain complete activity history in your HubSpot timeline.

Odoo Marketing Automation

ir.attachment

maps to

HubSpot

Files

1:1

Fully supported

Odoo file attachments linked to CRM records are downloaded and re-uploaded to HubSpot's file manager. Original filenames and URLs are preserved. File size limits apply — HubSpot's file upload limit is 250 MB per file. Inline images in Odoo notes are extracted and re-hosted in HubSpot's content delivery system.

Odoo Marketing Automation

Custom Odoo models (x_*)

maps to

HubSpot

Custom properties / custom objects (Enterprise)

1:1

Fully supported

Odoo custom fields and custom models defined via Studio or ir.model.fields migrate as HubSpot custom properties on the standard objects (for simple custom fields) or as HubSpot custom objects (for complex models, available on Enterprise tier). N:N relationships between custom models in Odoo require HubSpot junction objects or associations.

Odoo Marketing Automation

marketing.automation.activity

maps to

HubSpot

No equivalent (workflow rebuild required)

1:1

Fully supported

Odoo marketing automation activities (workflow triggers, conditions, actions) have no HubSpot equivalent and do not migrate. We export the workflow definitions as structured documentation so your HubSpot admin can rebuild them in HubSpot's workflow builder using the original Odoo logic as a reference.

Odoo Marketing Automation	HubSpot	Compatibility
res.partner (Contact type)	Contact1:1	Fully supported
res.partner (Lead type)	Lead / Contact1:many	Fully supported
crm.lead (Opportunity)	Deal1:1	Fully supported
crm.lead.team	HubSpot team / Sales team1:1	Fully supported
crm.stage	Deal pipeline stage1:1	Fully supported
crm.lead (Lead status field)	Contact lifecycle_stage property1:1	Fully supported
res.partner (Company type)	Company1:1	Fully supported
marketing.marketing (Campaign)	Campaign1:1	Fully supported
marketing.trace.emails / marketing.trace.sms	Engagement / Timeline notes1:1	Fully supported
mail.message / mail.activity	Engagement / Timeline1:1	Fully supported
ir.attachment	Files1:1	Fully supported
Custom Odoo models (x_*)	Custom properties / custom objects (Enterprise)1:1	Fully supported
marketing.automation.activity	No equivalent (workflow rebuild required)1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Odoo Marketing Automation gotchas

High

External API access is gated behind the Custom plan

High

Automation rules with Python server actions cannot replay on non-Odoo destinations

Medium

No native conversion tracking within Marketing Automation

Medium

Two dependent apps must both be installed for full feature access

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

Odoo Marketing Automation gotchas		HubSpot gotchas
Severity	Issue	Severity	Issue
High	External API access is gated behind the Custom plan	High	Marketing Contacts billing model is migration-critical
High	Automation rules with Python server actions cannot replay on non-Odoo destinations	High	Feature tier gating is not visible until onboarding
Medium	No native conversion tracking within Marketing Automation	Medium	Mandatory onboarding fees inflate year-one cost
Medium	Two dependent apps must both be installed for full feature access	Medium	HubSpot CSV importer cannot migrate engagements or attachments
		Medium	Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

Odoo lifecycle stage has no native HubSpot equivalent — custom property required

Odoo does not have a native lifecycle_stage property; contact progression is tracked via lead status fields, opportunity stage, and custom fields. HubSpot's lifecycle_stage (subscriber, lead, MQL, SQL, opportunity, customer, evangelist) is a built-in contact property. We map Odoo's lead status and opportunity stage combination to derive a HubSpot lifecycle_stage value for each contact, preserving the final derived state. Odoo lead history that would populate HubSpot's lifecycle stage change log requires custom datetime fields on the contact record — the original timestamps of stage transitions are stored as custom properties for reporting continuity.
Odoo campaigns map to HubSpot contacts as membership properties, not HubSpot campaign records

Odoo's marketing campaigns store enrollment traces on contacts (which contacts enrolled in which campaign, with which activities). HubSpot's campaign object tracks UTM source attribution and email performance rather than per-contact enrollment history. We preserve Odoo campaign membership as a custom contact property listing campaign names and enrollment dates. HubSpot campaign records are created for each Odoo campaign to serve as reporting containers, but the per-contact enrollment logic must be rebuilt as HubSpot workflow enrollment rules using the exported Odoo campaign definitions as a reference.
Odoo stage names are free-text; HubSpot stage values are scoped per pipeline

In Odoo, CRM stage names are defined per stage record and applied globally across all opportunities. In HubSpot, deal stage values are scoped to a specific pipeline object — changing the pipeline changes the available stage values. We map each Odoo stage to a HubSpot stage within the destination pipeline, preserving stage probabilities and forecast categories from HubSpot's stage definition. Teams with multiple Odoo sales teams sharing one stage set need to decide whether to map all teams to one HubSpot pipeline or create separate pipelines per team before migration.
Odoo marketing automation workflows and email templates do not migrate

Odoo marketing automation workflows (defined via the marketing.automation.record model) and email templates (mail.template model) are platform-native constructs that have no structural equivalent in HubSpot. Workflow triggers, conditions, time delays, and actions must be rebuilt in HubSpot's workflow builder. Email templates must be recreated in HubSpot's email template editor. We export Odoo workflow definitions and email template content as structured documentation so your HubSpot admin can rebuild them step-by-step, using the original Odoo logic as a specification.
Odoo API rate limit of ~1 request/second constrains migration throughput

Odoo's XML-RPC external API is rate-limited to approximately 1 request per second on standard Custom-plan setups. HubSpot's CRM API allows 5 requests per second. For Odoo instances with 50,000+ records, this speed differential means the Odoo export is the bottleneck. We handle this by batching Odoo reads into large page sizes (using Odoo's offset/limit pagination), caching responses where safe, and running parallel HubSpot writes against the buffered results. The delta-pickup window is sized accordingly to account for the slower source read rate on large datasets.

Migration approach

Six steps for a successful Odoo Marketing Automation to HubSpot data migration

Extract Odoo CRM and marketing data via XML-RPC API

We connect to Odoo's XML-RPC external API using your Custom-plan credentials and pull all CRM and marketing objects: res.partner (contacts and companies), crm.lead (leads and opportunities), crm.stage, mail.activity, mail.message, marketing.campaign, marketing.trace records, and ir.attachment for files. Custom models defined via ir.model.fields are enumerated separately. We validate record counts against Odoo's database counts and flag any objects that return zero records — those may indicate a module not installed or an access rights gap.
Configure HubSpot properties and custom objects before data lands

HubSpot's property schema must exist before data can be written. We create the custom lifecycle_stage__c property on contacts, campaign_membership__c for campaign enrollment history, original_create_date__c for create-date continuity, source_system_id__c for traceability, and any Odoo custom field equivalents identified in the audit. For Odoo custom models that require HubSpot custom objects (Enterprise tier), we create the custom object schema with its primary key and relationship properties before the migration run.
Resolve owners by email and sequence the import order

Odoo responsible users and sales team leaders are resolved to HubSpot users by email match. Unmatched owners are flagged with the Odoo user name and email so your team can create or invite those HubSpot users before the migration commits. We sequence the import so that company records land before contact records (contacts require a parent company_id), and contacts land before deal records (deals reference contacts via association). Odoo internal record IDs are preserved in HubSpot source_system_id__c fields for post-migration reconciliation.
Run sample migration with field-level diff

A representative slice of 100–500 records migrates first, covering contacts, companies, deals, and activities across multiple Odoo stages. We generate a field-level diff between the source Odoo payload and the landed HubSpot records, so you can verify lifecycle stage mapping, stage-value mapping, owner resolution, and company association before the full run commits. Any value-mapping errors in pick-list fields are corrected before the full migration executes.
Execute full migration with delta-pickup window

The full migration runs against HubSpot. A delta-pickup window of 24–48 hours captures any Odoo records created or modified during the cutover. Your team continues working in Odoo throughout. An audit log records every operation (read, write, update, skip, error) with timestamps and record IDs. If reconciliation finds discrepancies, one-click rollback reverts the HubSpot instance to its pre-migration state so the run can be corrected and re-executed.

Platform deep dives

Context on both ends of the pair

Odoo Marketing Automation

Source

Strengths

Native integration with the broader Odoo suite (CRM, Sales, eCommerce, Inventory, Accounting) means automation can act on transactional data without ETL.
Transparent per-app pricing is far cheaper than per-contact platforms (HubSpot, Marketo) for large contact databases — a structural advantage for high-volume senders.
Drag-and-drop email editor and visual workflow builder usable without coding knowledge once the Odoo learning curve is cleared.
Multi-channel support: email, SMS, and social media campaigns orchestrated from one platform.
Open-source codebase (Community Edition) provides a no-licence path for teams with internal Odoo developers.

Weaknesses

Steep learning curve for the Odoo UI — reviewers consistently note beginners struggle to orient versus purpose-built marketing tools like Mailchimp or ActiveCampaign.
Segmentation depth is limited compared to dedicated marketing automation platforms; complex predicate logic requires technical or developer help.
Automation workflow flexibility is rigid for non-standard scenarios; multi-branch logic and dynamic content insertion are weaker than HubSpot or Klaviyo.
Reporting and analytics are basic — most teams add Odoo Studio reporting or external BI tools (Power BI, Metabase) for executive-grade dashboards.
Third-party integration out of the box is limited to the Odoo connector ecosystem; bespoke integrations require Odoo development.

HubSpot

Destination

Strengths

Genuinely useful free CRM tier with no seat limit on contact records.
All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
Workflow automation triggers across contacts, deals, and tickets with a visual builder.
API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

	Odoo Marketing Automation Source	HubSpot Destination
Strengths	Native integration with the broader Odoo suite (CRM, Sales, eCommerce, Inventory, Accounting) means automation can act on transactional data without ETL. Transparent per-app pricing is far cheaper than per-contact platforms (HubSpot, Marketo) for large contact databases — a structural advantage for high-volume senders. Drag-and-drop email editor and visual workflow builder usable without coding knowledge once the Odoo learning curve is cleared. Multi-channel support: email, SMS, and social media campaigns orchestrated from one platform. Open-source codebase (Community Edition) provides a no-licence path for teams with internal Odoo developers.	Genuinely useful free CRM tier with no seat limit on contact records. All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration. Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews. Workflow automation triggers across contacts, deals, and tickets with a visual builder. API coverage for all standard objects including custom objects at Enterprise tier.
Weaknesses	Steep learning curve for the Odoo UI — reviewers consistently note beginners struggle to orient versus purpose-built marketing tools like Mailchimp or ActiveCampaign. Segmentation depth is limited compared to dedicated marketing automation platforms; complex predicate logic requires technical or developer help. Automation workflow flexibility is rigid for non-standard scenarios; multi-branch logic and dynamic content insertion are weaker than HubSpot or Klaviyo. Reporting and analytics are basic — most teams add Odoo Studio reporting or external BI tools (Power BI, Metabase) for executive-grade dashboards. Third-party integration out of the box is limited to the Odoo connector ecosystem; bespoke integrations require Odoo development.	Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×. Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation. Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page. API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing. Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Odoo Marketing Automation to HubSpot

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision