The Complete Guide to Odoo in 2026: Implementation, Customisation, Integration, Migration and Cost

What Odoo actually is

Odoo is a suite of business applications built on a shared database — CRM, sales, inventory, manufacturing, accounting, HR, website, point of sale, and several dozen more. The applications are modular. You switch on the ones you need and leave the rest off.

The architectural point that matters: because everything sits on one data model, a sales order confirming automatically creates the delivery, reserves the stock, and drafts the invoice. There is no synchronisation layer between your CRM and your inventory because they are the same system.

That is the entire value proposition, and it is a real one. Most mid-sized businesses run a CRM, a separate accounting package, a spreadsheet for stock, and a fourth thing for projects — plus a person whose actual job is reconciling them.

Odoo comes in two editions:

Community is open source and free to license. It covers the core operational apps. You pay for hosting and for anyone who helps you set it up.

Enterprise is a paid subscription. It adds accounting depth, studio-based customisation tools, mobile apps, several integrations, and official support. Most businesses running Odoo commercially end up here.

You can start on Community and move to Enterprise later, and plenty of businesses do. Moving the other direction is harder.

Versions and support in 2026

This section matters more than people expect, because version choice constrains everything downstream.

Odoo provides standard support for the three most recent major versions — helpdesk access, bug fixes, and security updates. Beyond that window, extended support is available for a mandatory additional fee, covering helpdesk and bug fixes subject to feasibility.

A new major version ships roughly annually. When it does, the oldest supported version rolls off.

Where things stand in August 2026:

Version	Released	Status
Odoo 19	September 2025	Supported — current
Odoo 18	Late 2024	Supported
Odoo 17	Late 2023	Supported until Odoo 20 releases
Odoo 16	2022	End of life (September 2025)
Odoo 15 and earlier	2021 and prior	End of life

Odoo 20 is expected at Odoo Experience 2026 in Brussels, 24–26 September. Odoo 17 leaves the standard window on that release.

If you are choosing a version today, choose Odoo 19. It has been in production since September 2025, its third-party modules are ported, its bugs are documented, and it gives you until roughly late 2028 before the next forced decision. Odoo 20 will be brand new — being an early adopter and running an implementation simultaneously stacks two risks on one deadline.

One constraint worth knowing early: you can only upgrade to a supported version, and the most recently retired version stays usable as an upgrade target for six months past its end of life. Fall far enough behind and a single upgrade becomes a sequence of them.

We cover this in depth in our Odoo 17 end of support migration checklist.

Should you use Odoo at all?

An honest section, because the answer is not always yes.

Odoo fits well when

You are running four or more disconnected systems. This is the strongest signal. The integration burden you are already carrying is the cost Odoo removes.

Your processes are reasonably standard. Odoo’s out-of-the-box workflows reflect how most businesses actually operate. If yours look broadly like everyone else’s, you will spend little on customisation.

You want to own your data and your deployment. Open source, self-hostable, no vendor lock on the database. For businesses with data residency requirements, this matters.

You are growing and adding functions. Starting with CRM and sales, then adding inventory, then manufacturing, works cleanly. Adding a fourth separate SaaS tool does not.

Odoo fits badly when

Your core process is genuinely unusual. If your competitive advantage lives in a workflow no standard ERP models, you will customise heavily, and heavy customisation in Odoo means every upgrade becomes a rebuild. Sometimes a purpose-built application is the cheaper answer over five years. We compared this directly in Odoo vs custom ERP.

You need deep vertical-specific compliance. Pharmaceutical batch genealogy, aerospace traceability, certain regulated financial workflows — specialist systems exist for good reasons.

You have no internal owner. ERP projects fail on people, not software. If nobody internally owns the project, has authority to decide, and has time allocated, the implementation will stall regardless of platform.

You want it live next month with 200 users. Possible, but not well.

Implementation: what it really involves

The software installs in an afternoon. The implementation is everything else.

Realistic timelines

Scope	Typical duration
Single app, under 10 users, standard config	2–4 weeks
3–4 apps, 10–50 users, light customisation	6–12 weeks
Full suite, 50–200 users, integrations, custom modules	3–6 months
Multi-company, multi-currency, heavy customisation	6–12 months

The variable that moves these numbers most is not user count. It is how many of your processes need to change to fit the system, versus how much of the system needs to change to fit your processes.

The phases

Discovery. Document how you actually work now — not how the process document says you work. Where the current system fails. What genuinely cannot change. Two weeks, minimum, and skipping it is the most common cause of overrun.

Configuration. Set up the standard system to match. Chart of accounts, warehouses, product categories, pricelists, user roles, approval rules. Most requirements that feel like they need custom code are configuration once you know where to look.

Data migration. Customers, suppliers, products, opening balances, open orders, historical transactions. Cleaning is the work; importing is trivial. Decide deliberately how much history to bring — most businesses need far less than they think, and every extra year slows every future upgrade.

Customisation. Only what discovery proved necessary. See the next section.

Testing. Real users running real workflows end to end. Not the IT team clicking around.

Training and go-live. Train by role, not by module. Your warehouse team does not need the accounting screens.

Post-go-live support. Budget four to six weeks of active support after launch. Things surface.

Our Odoo implementation services cover this full sequence.

The two mistakes that cost the most

Customising during implementation instead of after. You do not yet know what genuinely does not work. Go live on standard Odoo, run it for a quarter, then customise the things that are still painful. Half the list will have disappeared.

Migrating all your history. Ten years of transactional data slows every subsequent upgrade, inflates your database, and gets consulted approximately never. Bring open items and two years of closed ones. Archive the rest where you can still query it.

Customisation: where budgets die

Odoo is highly customisable. That is a feature and a trap.

The four levels, cheapest first

1. Configuration. Settings, pricelists, approval rules, automated actions, email templates. No code. Survives upgrades untouched. Solves more than people expect.

2. Studio. Odoo Enterprise’s low-code builder — add fields, modify views, build simple automations, design reports. Faster than development, and generally upgrade-safe. The tool most under-used by teams who jump straight to developers.

3. Custom modules. Proper Python and XML development. Unlimited capability. Every module written is a module you must maintain and rebuild at each major version.

4. Core modification. Changing Odoo’s own code. Don’t. It breaks upgrades permanently and there is almost always another way.

The rule that saves the most money

Before approving any customisation, ask what happens if you simply do it Odoo’s way.

Sometimes the answer is genuinely unacceptable. Frequently the answer is “it’s slightly different from how we did it in the old system” — and that is not a business case, that is habit with a budget attached.

Every custom module you avoid is one you never rebuild, never debug after an upgrade, and never explain to a new developer.

When customisation is clearly right

• A pricing model your industry requires and Odoo does not model
• Regulatory reporting in a format Odoo does not produce
• A high-volume operation where a small workflow gain compounds
• Integration logic no connector covers

Our Odoo customisation services start with whether the customisation is necessary, because the cheapest module is the one nobody writes.

Integrations that matter

Odoo replaces a lot, but not everything. These are the connections that come up most.

E-commerce

Shopify. The most common request. Orders flow into Odoo, stock levels flow back, customers and fulfilment sync. The decisions that matter: which system owns product data, how you handle refunds and partial shipments, and whether stock syncs in real time or on a schedule. See our guides on connecting Shopify to Odoo and choosing a Shopify-Odoo connector.

WooCommerce. Similar shape, more variation, because WooCommerce installations differ wildly. Payment gateway handling is the usual complication. Our WooCommerce to Odoo guide covers the setup.

The general principle for e-commerce: decide the system of record for each object before you build anything. Products in one place, stock in one place, customers in one place. Bidirectional sync without a clear owner produces conflicts you will be resolving manually forever.

CRM and marketing

HubSpot. Common where marketing has invested in HubSpot and does not want to move. Contacts and deals sync; Odoo handles fulfilment and invoicing. Field mapping is where these break — decide early which system owns the contact record. See connecting HubSpot to Odoo.

Mailchimp. Lighter integration, usually list sync plus campaign results back into Odoo. Covered in our Odoo Mailchimp connector guide.

Business intelligence

Power BI. Odoo’s built-in reporting is competent for operational questions and limited for analytical ones. Power BI on top of Odoo data gives you proper analysis. The connection points at Odoo’s data model directly — which means it survives upgrades better than most integrations, but requires someone who understands the schema. Our Odoo to Power BI setup guide walks the configuration.

Authentication and infrastructure

Single sign-on via Microsoft Azure, printing, IoT devices for warehouse and manufacturing floors. Less glamorous, high daily impact.

Our Odoo integration services cover custom connector development where no standard option fits.

AI and Odoo in 2026

This moved from marketing language to shipped functionality faster than most predicted.

Odoo 19 includes native AI capability — AI fields that generate content from record context, AI agents that act on defined triggers, document sorting, live chat handling, and text generation inside email templates. These use API keys you supply, which means you control the model and the cost.

The practical uses that hold up:

Document handling. Vendor bill digitisation and document classification remove genuine manual work with measurable accuracy.

First-line support. AI-assisted live chat handles repetitive questions and escalates the rest.

Drafting. Product descriptions, email responses, and summaries — reviewed by a human, but starting from something rather than nothing.

The uses that do not hold up yet: anything where a wrong answer is expensive and unverified. Do not let AI post journal entries.

MCP and Odoo

Model Context Protocol is the standard that lets AI assistants connect to external systems in a structured way. Applied to Odoo, it means an assistant like Claude or ChatGPT can query and act on your ERP data directly, without a bespoke integration for each tool.

This is early and genuinely useful. It is also where the technology is moving fastest. We covered the fundamentals in what is Odoo MCP Server and the broader protocol in model context protocol explained.

For a fuller treatment of AI inside Odoo operations, see how AI agents transform Odoo ERP operations and our Odoo AI integration guide.

Migration and upgrades

Two different projects that get the same name.

Migration means moving from another system into Odoo — from SAP, from QuickBooks, from spreadsheets. That is an implementation with a data-transfer phase attached.

Upgrade means moving between Odoo versions. That is a technical project with a business testing phase attached.

Upgrading between Odoo versions

The compressed version of our full migration checklist:

1. Audit. Every custom module, every integration, data volumes, hosting type. Two weeks. Do not skip.
2. Choose the target. Usually the current stable version, not the newest.
3. Rebuild custom modules. This is where the budget goes. Test each in isolation.
4. Test migration on a copy. Two or three runs is normal. Never first-run against production.
5. User acceptance testing. Real workflows, real users, written sign-off.
6. Reconnect integrations. Test in both directions.
7. Cutover. Low-activity window, verified backup, keep the old instance read-only for 30 days.

Typical duration: 8–14 weeks for a single-version move with moderate customisation. Multi-version jumps take substantially longer.

Migrating into Odoo from another ERP

The data work is larger and the process work is smaller — you are mapping unfamiliar structures rather than rebuilding known ones. Budget heavily for data cleaning. In most projects the extraction and cleaning consumes more time than the loading.

Our Odoo migration services cover both directions.

What Odoo costs

Nobody can quote your implementation from a description. But the cost structure is knowable, and knowing it is how you evaluate a quote.

The five components

1. Licensing. Community is free. Enterprise is per user per month, with app-based pricing on top. Published on Odoo’s site and largely non-negotiable at small scale.

2. Hosting. Odoo Online (managed, least flexible), Odoo.sh (managed, developer-friendly, supports custom modules), or self-hosted (most control, most responsibility). Cost rises with control.

3. Implementation. Partner time for discovery, configuration, data migration, testing and training. The largest first-year line for most businesses.

4. Customisation. Development time. The most variable component and the one you have most control over.

5. Ongoing. Support, upgrades, additional development. Plan for a meaningful annual figure, not zero.

What actually moves the number

Driver	Low	High
Custom modules	0–3 simple	15+ interconnected
Integrations	1–2 standard	6+ including bespoke
Users	Under 20	200+
Data volume	Under 100k rows	Millions
Process change tolerance	High — will adapt	Low — system must adapt

That last row is the one nobody quotes on and everybody pays for. A business willing to adopt standard Odoo workflows implements at a fraction of the cost of one that insists the software match its existing habits exactly.

How to get a useful quote

Do the audit first. Bring a written list of your apps, your integrations, your data volumes, your user count by role, and your genuinely non-negotiable processes. A partner working from that gives you a fixed price. A partner working from a conversation gives you a range, and the range will be wide for good reason.

Choosing an Odoo partner

Six questions that separate real partners from resellers:

“What would you talk me out of?” A partner who agrees with every requirement is selling hours, not outcomes. The right answer includes at least one “you probably don’t need that.”

“Show me an implementation like mine.” Not a logo wall — a comparable business, comparable scope, and what went wrong on it.

“Who actually does the work?” Sales lead, delivery lead, developers. Find out whether the person in the meeting is the person on the project.

“What happens after go-live?” Support model, response times, upgrade handling. The relationship lasts longer than the project.

“How do you handle upgrades on custom modules?” This reveals whether they think about your total cost of ownership or just this quarter’s invoice.

“What is your certification status?” Odoo’s partner tiers reflect certified staff and completed implementations. Not everything, but a floor.

Zehntech is a certified Odoo partner with 600+ implementations across 12+ countries. If you want a scoped assessment before committing to anything, talk to our team.

Frequently asked questions

Is Odoo free?

Odoo Community is open source and free to license, but you still pay for hosting, implementation and any development. Odoo Enterprise is a paid subscription priced per user with app-based pricing. Free licensing is not the same as free ERP.

Which Odoo version should I use in 2026?

Odoo 19 for most businesses. It has been in production since September 2025, its ecosystem has caught up, and it stays supported until roughly late 2028. Choose Odoo 20, expected late September 2026, only if it contains a feature you specifically need.

How long does an Odoo implementation take?

Two to four weeks for a single app with a handful of users. Six to twelve weeks for three or four apps with light customisation. Three to six months for a full suite with integrations. Heavy customisation or multi-company setups run longer.

Is Odoo good for small businesses?

Yes, particularly where a small business is already juggling several disconnected tools. Start with one or two apps rather than the full suite — the modular structure means you are not forced to adopt everything at once.

Can Odoo replace SAP or Microsoft Dynamics?

For many mid-market businesses, yes, at substantially lower total cost. For large enterprises with deep vertical compliance requirements or extremely complex multi-entity structures, the comparison is more nuanced and depends heavily on which specific modules you rely on.

How much does Odoo customisation cost?

It depends entirely on scope, and any figure quoted without seeing your requirements is guesswork. The drivers are the number of custom modules, their complexity, and how much they touch core models. The reliable way to control it is to run standard Odoo for a quarter before approving any customisation.

Does Odoo integrate with Shopify, HubSpot and Power BI?

Yes, all three, with well-established approaches for each. Shopify and WooCommerce integrations handle order and stock sync. HubSpot syncs contacts and deals. Power BI connects to Odoo’s data model for analytics. The complexity lies in field mapping and deciding which system owns which record.

What happens when my Odoo version reaches end of life?

The software keeps running, but you stop receiving security patches, bug fixes and helpdesk support. Odoo offers extended support for Enterprise customers for an additional fee. Staying on an unsupported version also compounds your eventual upgrade cost, because multi-version jumps are considerably harder than single ones.

Can I move from Odoo Community to Enterprise later?

Yes, and it is a common path. Moving from Enterprise back to Community is more difficult, because Enterprise-only features and modules do not exist in Community.

Does Odoo have AI features?

Odoo 19 includes native AI capability — AI fields, AI agents, document sorting, live chat assistance and text generation — using API keys you provide. Model Context Protocol support additionally allows AI assistants to interact with Odoo data directly.

Where to start

If you are evaluating Odoo, the highest-value thing you can do is write down your current systems, your genuine non-negotiables, and the processes you would be willing to change. That document determines your cost more than any other factor.

If you are already on Odoo and on version 17 or older, check your support status this month. The upgrade window is narrower than it looks.

Deep dives on each section:

• Odoo 17 End of Support: 2026 Migration Checklist
• Odoo Migration Guide 2026
• Odoo vs Custom ERP in 2026
• Odoo AI Integration: Complete Guide
• What Is Odoo MCP Server?
• Connecting Shopify to Odoo
• Connecting HubSpot to Odoo
• Connecting Odoo to Power BI

Our Odoo services:
Implementation · Customisation · Integration · Migration · Mobile app development

Talk to our Odoo team for a scoped assessment.