"How much will Odoo cost us?" has an honest answer: licenses are the smallest part. The real budget goes into analysis, configuration, data migration, integrations, training and the first months of support. Companies that budget only for subscriptions are the ones that end up with a half-implemented ERP and a team back in spreadsheets. This article breaks an Odoo implementation into cost components, gives realistic ranges by company size and lists the hidden costs we see most often.
The five components of an Odoo budget
- Subscription — Odoo Enterprise licenses per user, or zero for Community.
- Hosting — included in Odoo Online, a separate subscription on Odoo.sh, or your own servers.
- Implementation work — analysis, configuration, customization, data migration, integrations and testing, usually by a partner.
- Internal time — your key users and project owner. Rarely budgeted, always spent.
- Ongoing costs — support, upgrades every one to three years and continuous improvements.
1. Subscription
At list prices in the euro zone, Odoo Enterprise costs €11.90 per user per month on the Standard plan and €22.90 on the Custom plan when billed yearly. Custom is required for Studio, multi-company, external API access and hosting on Odoo.sh or on-premise (Odoo pricing). Community has no license fee but lacks full accounting, Studio and the upgrade service; we compare the two in detail in Odoo Community vs Enterprise.
| Users | Standard, per year | Custom, per year |
|---|---|---|
| 10 | ≈ €1,430 | ≈ €2,750 |
| 30 | ≈ €4,280 | ≈ €8,240 |
| 100 | ≈ €14,280 | ≈ €27,480 |
2. Hosting
- Odoo Online — included in the subscription; standard apps and Studio only, no custom Python modules.
- Odoo.sh — Odoo's platform for custom code, with staging branches, backups and Git-based deployment, priced by workers and storage on top of licenses (Odoo.sh pricing).
- On-premise or your cloud — servers, PostgreSQL administration, backups and monitoring are yours. Sizing guidance is in Odoo's deployment documentation (Odoo: deploying on-premise) and in our article on Odoo performance tuning.
For most mid-market companies with a few custom modules, Odoo.sh is the pragmatic default.
3. Implementation work, phase by phase
This is where 60–80% of the first-year budget goes. A typical project for a mid-sized company:
| Phase | Share of effort | What happens |
|---|---|---|
| Discovery and analysis | 10–15% | Process mapping, requirements, fit-gap against standard Odoo |
| Configuration | 15–20% | Companies, chart of accounts, warehouses, routes, pricelists, users and access rights |
| Customization | 20–35% | Custom modules, reports, Studio changes, automation |
| Data migration | 10–20% | Cleaning, mapping and importing master data and open balances |
| Integrations | 10–20% | Banks, carriers, marketplaces, payment providers, BI |
| Testing and training | 10–15% | Scenario testing, user acceptance, training materials |
| Go-live and hypercare | 5–10% | Cutover, first-weeks support, fixes |
The biggest driver is the fit-gap result. Every process you adapt to standard Odoo is configuration; every process Odoo must adapt to is development, testing and upgrade cost for years. Typical integration work for Ukrainian e-commerce is described in Integrating Odoo with Nova Poshta and monobank.
Budget ranges by company size
These are the ranges we see for partner work in Central and Eastern Europe, excluding licenses and hosting:
| Company profile | Typical scope | Duration | Implementation budget |
|---|---|---|---|
| Small (up to 30 users) | Sales, inventory, invoicing or accounting, website | 3–4 months | €25,000–€45,000 |
| Mid-market (30–150 users) | Plus manufacturing or multi-warehouse, several integrations, custom reports | 5–7 months | €60,000–€150,000 |
| Large (150+ users) | Multi-company, complex manufacturing, many integrations, data warehouse | 8+ months | from €200,000 |
Migrating from 1C adds data and process work specific to that system; we describe the method in Migrating from 1C to Odoo.
4. Internal time: the cost nobody budgets
An ERP project needs a project owner with authority, roughly 30–50% of their time for the duration, and key users from each department for workshops, testing and training — typically 10–20% of their time, more around go-live. When this time is not available, the partner makes decisions the business should make, and the system reflects the partner's assumptions instead of your processes.
5. Ongoing costs after go-live
- Support and small changes — often 10–20% of the initial implementation budget per year.
- Upgrades — Odoo supports each major version for three years (Odoo: supported versions), so plan an upgrade at least every two to three years. The cost scales with the number of custom modules; see Odoo 17 vs Odoo 18.
- Continuous improvement — new reports, automation and integrations as the business changes.
Hidden costs we see most often
- Dirty data. Duplicated customers, inconsistent product units and years of unreconciled balances can double the migration phase.
- Recreating the old system. Asking Odoo to look and behave like the previous ERP multiplies customization and upgrade costs.
- Underestimated localization. Ukrainian tax reporting and payroll require partner modules or development in any edition.
- Integrations without an owner. Every integration needs monitoring, error handling and someone who fixes it when the other side changes its API.
- Training as an afterthought. Two hours of training before go-live leads to months of workarounds.
- No budget for the first year after launch. The first quarter always brings change requests.
How to keep the budget under control
- Standard first. Run a fit-gap workshop and challenge every customization: is this a real competitive advantage or a habit?
- Phase the rollout. Start with the processes that bring the most value; move accounting at the start of a period.
- Use Studio for simple changes and code only for real business logic.
- Fix the scope per phase with a change request process.
- Measure value. Agree on two or three business metrics — order processing time, inventory accuracy, closing time — before the project starts.
Example: a 40-user distributor
To make the ranges concrete, here is a typical first-year budget for a distributor with 40 users, two warehouses, a B2B portal and integrations with a bank and a carrier, on Odoo Enterprise Custom hosted on Odoo.sh:
| Item | First-year cost |
|---|---|
| Licenses: 40 users × €22.90 × 12 | ≈ €11,000 |
| Odoo.sh hosting (production plus staging) | €2,000–4,000 |
| Discovery and fit-gap | €6,000–9,000 |
| Configuration and customization | €25,000–40,000 |
| Data migration from the old ERP | €8,000–15,000 |
| Two integrations | €8,000–15,000 |
| Testing, training, go-live support | €8,000–12,000 |
| Total | ≈ €68,000–106,000 |
From the second year, costs typically drop to licenses, hosting and 10–20% of the implementation budget for support and improvements.
Questions to ask an implementation partner
- How many similar projects in our industry and country have you delivered, and can we talk to those clients?
- Which of our requirements will be configuration, which Studio, and which custom code?
- Who owns the code of custom modules, and where is it stored?
- How do you handle Ukrainian localization: own modules, third-party modules or development?
- What does your upgrade process look like, and how do you estimate it?
- What is included in support after go-live, and what are the response times?
Where we would not cut costs
If the budget is tight, reduce scope — fewer modules in phase one, fewer custom reports — rather than cutting discovery, data cleaning, testing or training. Those four phases decide whether people actually use the system after go-live.
FAQ
Can we implement Odoo ourselves? Small companies with simple processes and a technically strong owner sometimes do. For accounting, manufacturing or integrations, an experienced partner usually saves more than it costs.
Fixed price or time and materials? Fixed price works for well-defined phases after discovery. For discovery itself and evolving requirements, time and materials with a cap is more honest.
How long until return on investment? It depends on the processes automated. We typically see payback within 12–24 months when the project removes manual data entry and duplicate systems.
Is Odoo cheaper than SAP Business One or Microsoft Dynamics? Licenses are usually lower, and the open-source core keeps you less dependent on one vendor. Implementation costs depend more on scope than on the product.
Is Odoo.sh worth it compared to our own server? For most mid-sized companies with custom modules, yes: staging branches, backups and upgrades come built in. Self-hosting makes sense with strict data residency rules or an in-house operations team.
How do we budget for the unknown? Add a contingency of 15–20% to the implementation budget. Change requests after users see the system for the first time are normal, not a sign of failure.
Sources
- Odoo. Pricing.
- Odoo. Odoo.sh pricing.
- Odoo. Deploying Odoo on-premise.
- Odoo. Standard and extended support.
- Odoo. Studio documentation.