Odoo CRM
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Odoo SA · www.odoo.com
Compare with Zoho CRM → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Odoo CRM at a glance
- Vendor
- Odoo SA
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates Odoo CRM 2.5/5, the mean of 6 judges. Odoo CRM is the CRM app of an open-source business suite from Odoo S.A., a Belgian vendor; the picture is lopsided. how scores are made
- As of
- Vendor pages captured 11 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Odoo CRM is the CRM app of an open-source business suite from Odoo S.A., a Belgian vendor; the picture is lopsided. Data portability is its strongest score, flat at 8 — a complete database backup exportable from the control panel at any time, and LGPLv3 code with an on-premise option on the Custom plan. Sovereignty scores split 5 to 7: higher scores credit a Belgian contracting entity, a selectable Europe region on named OVH and Google infrastructure, published subprocessors and retention caps, while lower scores weigh the additional Canada-based backup for EU-hosted customers on versions before Odoo 19.0 until Q4 2026, Clearbit enrichment in the chain, and no public information on a data processing agreement. Weakest are sales pipeline and integrations, both 3 to 4: forum captures report monthly subscriptions missing from the sales forecast and revenues booked as lump sums, and the External API is a Custom-plan feature. Pricing transparency scores 5 to 6: public tiers run from €0 to Custom at €35.90 per user per month, but Odoo.sh hosting costs are excluded from plan prices.
Speaks for it
- A complete database backup exportable from the control panel at any time, plus self-service database deletion
- LGPLv3-licensed code with an on-premise option on the Custom plan, so the software leaves with the data
- A Belgian contracting entity, a selectable Europe region, and a published subprocessor list with purposes
- Public per-user pricing on every tier, including One App Free at €0 with unlimited users and no credit card required
- Unlimited support, hosting and maintenance included in all plans
Held against it
- The External API is a Custom-plan feature, so scripted integration sits behind the top tier
- Captured forum threads report monthly subscriptions missing from the sales forecast and revenues booked as lump sums
- Odoo.sh hosting costs are excluded from plan prices with no published figure
- We found no public information on duplicate detection or record merging
- EU-hosted customers on versions before Odoo 19.0 keep an additional Canada-based backup until the transition completes in Q4 2026
Best for
- You want a strong exit before committing customer data — a complete database export at any time plus self-hostable LGPLv3 code
- You are a European buyer who prioritises a Belgian contracting entity, a selectable Europe region and a published subprocessor list
- You want all apps for a single per-user fee and can start on One App Free at €0 with unlimited users and no credit card required
- You run a simple visual Kanban pipeline and value portability and price over forecasting depth
Avoid if
- You sell on monthly subscriptions and need them in your sales forecast — captured forum answers report they do not come back in it
- Your revenue stack needs the external API on a Standard plan — the External API is a Custom-plan feature
- You plan to use Odoo.sh hosting and need a computable budget — ask the vendor: the public pages we read do not show it
- You are an EU-hosted customer on a version before Odoo 19.0 and cannot accept an additional Canada-based backup until Q4 2026
The scores
| Criterion | Panel median |
|---|---|
| Contact & data model | 2 of 5 |
| Pipeline & forecasting | 1.5 of 5 |
| Automation & workflows | 2 of 5 |
| Integrations & API | 2 of 5 |
| European sovereignty | 3.5 of 5 |
| Import, export & exit | 4 of 5 |
| Pricing transparency | 3 of 5 |
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records: contacts, companies and deals linked to each other, custom fields, activity history on the record, import hygiene and deduplication.
0 — Not a CRM data model; the product is an address book or mailing list with no companies or deals.
3 — Contacts, companies and deals linked to each other, with a few custom fields and notes on the record.
5 — Custom fields on contacts, companies and deals, an activity timeline (emails, calls, meetings, notes) on each record, and duplicate detection or merging of records.
8 — Custom objects or relationships beyond the standard model, field types with validation and required fields, bulk merge and deduplication tooling, and field-level permissions.
10 — A modelable system of record: custom objects with their own relations, pipelines and permissions, field-level change history, data-quality tooling (enrichment, bulk cleanup, rules) documented, and the model exposed completely through the API.
The Solo Seller
Contacts link to companies (via External ID on import) and custom fields on contacts are confirmed, with incoming email landing on the pipeline and group-based record visibility — but the captured help threads describe a three-part import procedure with admin toggles and technical settings, and I found no public information on duplicate detection or merging records. As someone who sets up in an afternoon, that import dance worries me more than the model itself. 1 4 5 6
The Data Protection Officer
Contacts imported and linked to companies through external identifiers, custom fields on contacts, and opportunities with quotations are all documented, with record visibility governed by sales access-right groups and incoming emails attached to the pipeline. We found no public information on duplicate detection or merging tooling, so the model sits between the basics and full record hygiene. 1 4 5 6 7
The Sales Ops Lead
Contacts, companies and opportunities are linked — imports tie people to employers through external identifiers and an "Is a Company" flag — and custom fields on contacts are confirmed, though created through code. Visibility of other users' records is governed by sales access-right groups rather than left open, which is the right discipline. We found no public information on duplicate detection, merging, or field-level change history, and that import hygiene is exactly what a 40-seat team needs on day one. 1 4 5 6
The RevOps Integrator
Contacts link to companies and opportunities move through a staged Kanban pipeline, custom fields on contacts can be imported and exported, and group-based access rights control who sees which records. The community pages show the friction: linking persons to companies during import takes a multi-part procedure with External IDs, and custom fields are handled via code. We found no public information on duplicate detection, merging, or an activity timeline on the record. 1 4 5 6
The Migrator
Contacts link to companies through import using external identifiers, custom fields on contacts survive import and export, and deals run in a Kanban pipeline with incoming mail landing on the record; permission groups control who sees whose records. I found no public information on duplicate detection or bulk merge tooling, and that silence is exactly what bites on day one of a migration, so I hold this just above the basic linked model. 1 4 5 6 7
The Skeptic
Contacts, companies and opportunities are linked — import maps persons to companies through an external identifier, incoming email lands on the record, and custom fields on contacts are confirmed — though most of this comes from forum threads rather than the vendor's own pages. We found no public information on duplicate detection, record merging, custom objects or field-level permissions. 1 4 5 7
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
How deals move through a sales process and what the pipeline reports: pipelines and stages, probabilities, forecasts, goals or quotas, win/loss analysis and sales reporting.
0 — No deals or pipeline; the product manages contacts or tickets only.
3 — A visual pipeline of deals with stages and amounts, and a pipeline overview or simple sales report.
5 — Several pipelines with stage probabilities or a weighted value, a revenue forecast view, sales goals or targets, and standard sales reports or dashboards.
8 — An enforceable process (required fields or stage gates per stage), win/loss reasons captured and reported, a custom report builder, and forecasts by team and period with quota or goal attainment.
10 — Forecasting a CFO signs: weighted and commit-based forecast categories, historical snapshots of the pipeline, attainment tracking per rep and team, and a report builder that combines any objects and fields.
The Solo Seller
A Kanban pipeline with drag-and-drop stages, quotations and planned or probable revenue insight is documented, but the captured forum pages describe revenues booked as lump sums and monthly subscriptions not appearing in the sales forecast. I found no public information on stage probabilities, goals, or win/loss analysis. 1 7
The Data Protection Officer
A Kanban pipeline with stages and drag-and-drop moves, probable-revenue insight from opportunities and quotations, and per-group pipeline visibility are documented. Community answers record subscriptions missing from the sales forecast and revenues booked as lump sums, and we found no public information on stage probabilities, weighted forecasts or goals. 1 6 7
The Sales Ops Lead
The Kanban view moves opportunities through stages with drag and drop, quotations feed a planned-or-probable revenue view, and record rules control who sees whose pipeline — a real stage pipeline, but nothing more. We found no public information on stage probabilities, multiple pipelines, quotas or goal attainment, and a captured forum discussion reports that monthly subscriptions do not come back in the sales forecast, with revenues booked as lump sums. I could not take that to a CFO review. 1 6 7
The RevOps Integrator
A Kanban pipeline with drag-and-drop stages and an insight into planned or probable revenue is documented, and sales access-right groups control visibility of other users' opportunities. The forum threads we read describe revenues booked as lump sums and subscriptions that do not return in the sales forecast. We found no public information on stage probabilities, goals, win/loss analysis or a custom report builder. 1 6 7
The Migrator
A Kanban pipeline with drag-and-drop stages is documented, quotations feed a planned or probable revenue view, and access-right groups govern pipeline visibility. Community threads note revenues are booked as lump sums and monthly subscriptions stay out of the sales forecast; I found no public information on stage probabilities, weighted values, or goals, so this reads as a solid visual pipeline with thin reporting. 1 6 7
The Skeptic
A drag-and-drop Kanban with stages, quotations and a probable-revenue view is documented, but the only forecasting evidence is forum users reporting that subscriptions don't come back in the sales forecast and that revenue books as lump sums. We found no public information on stage probabilities, multiple pipelines, sales goals or a custom report builder. 1 6 7
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant: workflow rules, email sequences, task creation and lead assignment.
0 — No automation of any kind; every step is done by hand.
3 — Trigger-based automations on records (a field change or stage change creates a task, sends an email or updates a field), or email templates with scheduled follow-ups.
5 — A visual workflow builder with triggers, conditions and actions, email sequences or cadences with delays, and automatic assignment of leads or deals.
8 — Multi-step workflows across objects with branching and webhooks or custom code as steps, round-robin and rule-based routing, sequence analytics, and automation limits stated per tier.
10 — Automation as infrastructure: versioned workflows with per-run logs and error handling, test or sandbox runs, and limits generous enough that the feature is not its own upsell — all documented.
The Solo Seller
Automation rules with documented triggers (On Save, with On Create deprecated in Odoo 17 plus a workaround), automated lead creation, team assignment and scheduled activities cover my basics. Only admin-level users with settings access can create automated actions — fine when I am the admin — and I found no public information on email sequences, branching or stated limits per tier. 1 8 9
The Data Protection Officer
Automated lead creation, team assignment and scheduled activities, plus automation rules firing on save, are documented — but only administrator-level users with settings access can create them. We found no public information on a visual workflow builder, email sequences, or per-tier automation limits. 1 8 9
The Sales Ops Lead
Automation rules with save-based triggers, automated lead creation, team assignment and scheduled activities are documented, and there is a stated workaround for create-only triggers using the creation date. Two cautions for a roll-out: only admin-level users in the settings group can create automated actions, and we found no public information on email sequences, branching, round-robin routing or per-tier automation limits. 1 8 9
The RevOps Integrator
Trigger-based automation is real — automation rules with an 'On Save' trigger, plus named capabilities for lead creation, team assignment and scheduled activities. Creating automated actions is restricted to Admin-level users in the Administration / Settings group, and the On Create trigger is deprecated in favor of a workaround. We found no public information on email sequences or cadences with delays. 1 8 9
The Migrator
Automated lead creation, team assignment and scheduled activities are claimed on the product page, and record-level automation rules exist with an On Save trigger. The captured discussions show create-only automation needs an official workaround and that automated actions sit behind the Administration/Settings group — real, but rough enough that I would budget consultant time. 1 8 9
The Skeptic
Trigger-based rules exist for lead creation, team assignment and scheduled activities, yet the forum record shows a create-trigger deprecated in favour of an official workaround, and automated actions are restricted to Administration/Settings-level users. We found no public information on email sequences, branching, routing logic, automation limits or per-run logs. 1 8 9
Integrations & API
Show reasoningHide reasoning
How this is scored
Email and calendar sync, native connections, an integration marketplace, and an API that treats external systems as first-class.
0 — No integrations and no API; the product stands alone.
3 — Email logging (BCC or plug-in) or a calendar connection, a handful of named integrations or a Zapier/Make connector.
5 — Two-way email and calendar sync with Google and Microsoft, a documented REST API, and a directory of native integrations.
8 — A marketplace of named native integrations for the revenue stack, webhooks, OAuth apps for third parties, API rate limits stated, and API coverage of all core objects.
10 — An ecosystem: a public API covering everything the UI does, event streams or webhooks for every object, SDKs and a sandbox, and two-way sync with named ERP, support and marketing systems documented.
The Solo Seller
Email, live chat, SMS and VoIP are named channels, incoming email flows into the pipeline automatically, and an XML-RPC channel exists for external tools. But on the hosted plans the external API appears as a Custom-plan feature, and I found no public information on two-way Google or Microsoft sync, a REST API, or a third-party integration directory — gating the API behind the top tier is exactly the hostage-taking I reject. 1 10 13 2
The Data Protection Officer
Email, live chat, SMS and VoIP channels are named, an XML-RPC channel lets external tools feed data through, and the external API appears as a Custom-plan feature. We found no public information on two-way Google or Microsoft sync, a native integration directory, or stated API rate limits. 1 13 2
The Sales Ops Lead
Incoming email lands in the pipeline automatically, SMS, VoIP and live chat are named channels, and captured forum threads reference an XML-RPC channel that external tools can feed. The external API is listed as a feature of the top Custom plan only, and we found no public information on two-way Google or Microsoft calendar sync, an integration marketplace, or API rate limits. 1 13 2
The RevOps Integrator
Named channels are Email, Live chat, SMS and VoIP, with incoming emails automatically added to the pipeline — capture, not two-way sync — and we found no public information on Google or Microsoft two-way email and calendar sync, webhooks, or a directory of native integrations. An XML-RPC channel for external tools is referenced in old community material, but the pricing pages list the External API under the top Custom plan only; for a revenue stack where the CRM must talk to billing and marketing as a peer, a tier-gated API is a closed-ecosystem signal I penalize. 1 2 13 2
The Migrator
Email, live chat, SMS and VoIP channels are named, incoming mail is added to the pipeline automatically, and an XML-RPC channel lets external tools feed data through. The External API is a Custom-plan extra rather than part of every tier — a scripted exit path behind the top plan is a lock-in smell I do not forgive cheaply — and I found no public information on Google or Microsoft two-way sync or an integration marketplace. 1 2 13 2
The Skeptic
Email, live chat, SMS and VoIP channels are named on the product page, and an XML-RPC channel is described in forum threads — but the pricing page puts the external API in the Custom tier, which prices the API out of the standard plans. We found no public information on an integration marketplace, webhooks, rate limits, or two-way Google or Microsoft email and calendar sync. 1 13 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, email and calendar sync, telephony, enrichment, AI features), and the data processing agreement. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or hosting is non-EU with an EU option on request or on top tiers.
5 — EU hosting stated (as default or selectable), a data processing agreement and a subprocessor list published; parts of the chain (email sync, enrichment, AI, support) may run through non-EU providers.
8 — EU contracting entity and EU hosting on named infrastructure, subprocessors listed with their locations, retention and deletion controls documented, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including AI and sync providers, deletion documented as complete, and certifications published with their scope.
The Solo Seller
A Belgian contracting entity, a selectable Europe region in production on France and Belgium with named providers like OVH, a published subprocessor list, data-center certifications including ISO 27001, SOC 2 and SecNumCloud, retention caps, and self-service database deletion are all proven. Dents: EU customers on versions before Odoo 19 get an additional Canada-based backup until a stated 2026 transition, enrichment runs through Clearbit with no stated location, and the customer-facing data processing agreement is left unknown. 3 2 3
The Data Protection Officer
A Belgian contracting entity, a selectable Europe region with production in France and Belgium, a published subprocessor list naming French providers with data-center certifications, documented retention caps, self-service database deletion and export, and a copyleft-licensed on-premise option make a serious European showing. Three things temper it: we found no public information on a customer-facing data processing agreement, EU-hosted customers on versions before Odoo 19.0 keep an additional Canada-based backup until Q4 2026, and Clearbit enrichment retrieves business information on visitors for prospection while deleted personal data can persist in backups for up to 12 months. 3 2 3
The Sales Ops Lead
The strongest suit: a Belgian contracting entity, a Europe production region on named OVH and Google Cloud EMEA infrastructure with France, Belgium, Netherlands and Sweden backup locations, a published subprocessor list with purposes, specific data processing contracts and Standard Contractual Clauses, twelve-month retention caps, self-service database deletion, and an on-premise option on the top plan. Two deductions: EU-hosted customers still receive an additional Canada-based backup until the transition completes (Q4 2026), and the ISO 27001 and SOC 2 certifications are stated for the hosting providers Google Cloud and OVH — we found no public information on certification of Odoo itself. 3 2 3
The RevOps Integrator
Odoo S.A. contracts from Belgium, the Europe region runs production in France and Belgium on named OVH and Google infrastructure, and a detailed subprocessor list with purposes is published alongside retention limits, Standard Contractual Clauses and self-service database deletion. The ISO 27001 and SOC 2 certifications stated belong to the hosting subprocessors rather than Odoo's own scope, customers cannot select their subprocessor, and EU-only backups apply only to new customers on Odoo 19 or later, with other EU customers keeping a Canada-based backup until Q4 2026. Enrichment through Clearbit and other US providers remains in the chain. 3 3
The Migrator
The privacy policy names Odoo S.A. at a Belgian address, the customer chooses a hosting region with Europe (FR, BE) production on named Google and OVH infrastructure, a subprocessor list with locations and data-center certifications is published, and Standard Contractual Clauses bind subsidiaries. The data processing agreement and contracting-entity jurisdiction are not stated on the captured pages, and parts of the chain run through US providers (Clearbit enrichment, trial recordings) plus a Canada backup for EU customers until the stated 2026 transition; the on-premise option on the top plan is the real sovereignty lever. 3 2 3
The Skeptic
The core is genuinely strong: a Belgian contracting entity, a selectable Europe region on named infrastructure (OVH, Google Cloud EMEA), a published subprocessor list with data processing contracts for each, documented retention and self-service database deletion. But the footnote says EU-hosted customers not yet on version 19 keep an additional Canada-based backup until the transition completes in late 2026, several captured subprocessors carry a purpose with no location, and the ISO 27001 and SOC 2 certifications belong to the hosting providers rather than Odoo itself. 3 2 3
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything: self-service import with field mapping, migration from other CRMs, export of records, activities and files, and API access for the rest. The anti-lock-in criterion.
0 — No import or export in the product; data enters and leaves only through the vendor's support.
3 — Self-service CSV or Excel import with field mapping and a CSV export of contacts and other main lists.
5 — Import with field mapping and duplicate handling, an import or migration path from named CRMs, and export of all main objects (contacts, companies, deals, activities) to CSV or Excel.
8 — A complete self-service export of all objects with activity history, notes and files in open formats, migration tooling or a migration service from named competitors, and an API sufficient to copy the whole database.
10 — Exit as a feature: a documented full-fidelity export (all objects, relations, history and files) on demand, import with dry-run, and data-return and deletion terms written into the contract.
The Solo Seller
I can export a complete backup of the database from the control panel at any time, delete the database myself, import CSVs with a validation step, and export lists to CSV — and with the code published open source I can even take the software with me. I found no public information on migration tooling from named competing CRMs; a forum capture only mentions a paid migration service without naming sources. 3 4 12 13 3
The Data Protection Officer
A complete database backup exportable at any time from the control panel, alongside self-service database deletion, is the strongest form of exit documentation, and CSV import with a validation step, list-view export applying across the data model, a migration service and an XML-RPC channel support it. We found no public information on migration paths from named competitor CRMs or data-return terms written into the contract. 3 4 12 13 3
The Sales Ops Lead
Exit is engineered rather than grudging: a complete database backup is exportable from the control panel at any time, CSV import maps fields through external identifiers with a validation pass before commit, list-view CSV export works across records, and the whole stack is self-hostable under an open-source licence. A migration service is confirmed to exist, though the captured pages tie it to no named competitor systems; on cancellation the database is destroyed after a three-week grace period. 3 12 13 3
The RevOps Integrator
Exit is unusually strong for a hosted CRM: a complete database backup is exportable from the control panel at any time, whole-database deletion is self-service with a three-week grace period before destruction, the lead import runs a Validate step before committing, and LGPL-licensed code with an on-premise option means the software leaves with the data. The community pages report re-import errors and a three-part import procedure for linking contacts to companies, the External API sits in the top plan, and we found no public information on migration from named competing CRMs. 3 4 12 13 2 3 15
The Migrator
This is the exit clause I look for: at any time you can export a complete backup of your database from the control panel in order to transfer it, database deletion is self-service with a three-week grace period before destruction, backups are destroyed automatically within a stated maximum, and CSV import runs across objects with a validation step and external-ID field mapping. The knocks are that the External API sits in the Custom plan — scripted copying is an upsell — and community reports describe errors when re-importing exported data. 3 4 12 13 2 3
The Skeptic
Exit is close to a feature here: a complete self-service backup of the database from the control panel at any time, explicitly offered 'in order to transfer it', plus CSV import with a validate-before-commit step and a paid migration service. Against that, the API sits in the Custom tier, and forum users report errors re-importing their own exports and a three-part procedure just to link contacts to companies. 3 4 12 13 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone: tier prices, billing periods, seat minimums, add-ons, usage meters and onboarding fees.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier; the other tiers or the per-seat scaling are not public.
5 — Public per-tier prices per seat or per account with the billing period (monthly or annual) stated, and the main inclusions of each tier listed.
8 — Every tier priced publicly with the annual/monthly split, seat minimums, limits and overage rules, add-ons priced, and VAT treatment stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter, onboarding fee and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
Standard is published at € 19.90 discounted (€ 24.90 list) per user per month with all apps included, Custom at € 35.90 (€ 44.90 list), and a One App Free plan at € 0 with unlimited users — no seat minimum stated, monthly or yearly billing, unlimited support included. But the discount runs 12 months for initial users only, Odoo.sh hosting costs are excluded without a published price, and I found no public information on VAT treatment, so I can estimate my card bill but not compute the renewal invoice to the cent. 1 2 2
The Data Protection Officer
Every plan is public per user per month — One App Free at € 0, Standard at € 19.90 against a € 24.90 list price, Custom at € 35.90 against € 44.90 — with billing options, the twelve-month discount scope, plan inclusions and a twenty-user cost calculator stated. Odoo.sh hosting costs are excluded from the plan prices with no public figure given, and we found no public information on VAT treatment or overage rules. 2 2 14
The Sales Ops Lead
Every plan carries a public per-user monthly price — One App Free at €0, Standard at €19.90 discounted and €24.90 list, Custom at €35.90 and €44.90 — with yearly and monthly billing options, the discount's 12-month validity on initial users, and all apps included for a single fee. Two gaps stop a two-minute invoice computation: Odoo.sh hosting cost is explicitly excluded from plan prices with no public figure given, and we found no public information on seat minimums or VAT treatment. 1 2 2
The RevOps Integrator
All plans are public — One App Free at €0 with one app and unlimited users, Standard at €19.90 per user per month discounted (€24.90 list) and Custom at €35.90 (€44.90 list), both including all apps — and the yearly/monthly split and the 12-month discount rule for initial users are stated. Odoo.sh hosting costs are explicitly excluded from the plan price, and we found no public information on seat minimums, VAT treatment, or usage limits and overage rules. 1 2 2
The Migrator
Every paid tier is priced publicly per user per month with yearly and monthly billing options, the discount is explicitly scoped to 12 months on initial users, a free one-app tier with unlimited users is clear, and a cost calculator with a worked 20-user example is published. Odoo.sh hosting costs are excluded from plan prices with no figure given, and I found no public information on VAT treatment or seat minimums, so the invoice for the self-hosted route cannot be computed from these pages. 1 2 2
The Skeptic
Two paid tiers are priced publicly per user per month — €19.90 discounted against €24.90 list for Standard — with a free tier, inclusions listed and yearly or monthly billing named, but the headline carries a footnote: the discount runs twelve months and covers only the initial users ordered, so the invoice at renewal is not computable from the page. Odoo.sh hosting is excluded from the plan price and carries no figure in these captures, and the optional in-app-purchase services are acknowledged without any public pricing. 1 3 2 2
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?The Data Location section it points to is not in the excerpt, and no specific regions, EU locations or defaults are named, so the existence of an EU region is only implied by the choice of hosting region and the EU hosting provider OVH S.A.S. in the truncated subprocessor table. |
— | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?The on-premise deployment option is shown for the Custom plan only, and Odoo.sh hosting costs are excluded from the plan price. |
1/1 pts | 2 Report an error |
| Open source |
Open source (copyleft)
unverified
Why unverified?The licence is named in a repository commit message and applies to the public code repository; the vendor also distributes a separate Enterprise edition whose licence is not named in these excerpts. |
1/1 pts | 15 Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Odoo CRM
Is Odoo CRM European?
Yes. whats-best.ai classifies Odoo CRM as EU-Made.
Where does Odoo CRM store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Odoo CRM have a free plan?
Yes. Odoo CRM has a free plan, per the vendor’s page captured 16 Nov 2026.
What are the best alternatives to Odoo CRM?
As of 20 Nov 2026, the panel rates Pipeliner CRM (3.5/5), Attio (3/5) and HubSpot Sales Hub (3/5) highest among the other 57 CRM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Attio (UK / wider Europe, United Kingdom). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Odoo CRM alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Open source. The licence is named in a repository commit message and applies to the public code repository; the vendor also distributes a separate Enterprise edition whose licence is not named in these excerpts.
- Weak sourcing — Hosting location. The Data Location section it points to is not in the excerpt, and no specific regions, EU locations or defaults are named, so the existence of an EU region is only implied by the choice of hosting region and the EU hosting provider OVH S.A.S. in the truncated subprocessor table.
- Weak sourcing — Hosting options. The on-premise deployment option is shown for the Custom plan only, and Odoo.sh hosting costs are excluded from the plan price.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 16 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor product page www.odoo.com Checked 16 Nov 2026 Details →
- 2 Vendor pricing page www.odoo.com Checked 16 Nov 2026 +2 earlier captures: 15 Sep 2026, 11 Sep 2026 Details →
- 3 Privacy policy www.odoo.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 4 Contact & data model — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 5 Contact & data model — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 6 Pipeline & forecasting — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 7 Pipeline & forecasting — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 8 Automation & workflows — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 9 Automation & workflows — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 10 Integrations & API — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 11 Integrations & API — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 12 Import, export & exit — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 13 Import, export & exit — found from sitemap www.odoo.com Checked 16 Nov 2026 Details →
- 14 Self-hosting / on-premises installation docs — found from the homepage www.odoo.com Checked 16 Nov 2026 Details →
- 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Nov 2026 Details →
- 16 Structured-data backfill: markup only, no text or screenshot www.odoo.com Checked 8 Nov 2026 Details →