Implementing Odoo in an SME: budget, timeline and steps
The numbers, without having to pick up the phone
You want to know what an Odoo project really costs and how long it takes. You have probably landed on a series of pages answering "it depends on your needs, contact us". That's true, and it's also a convenient way of saying nothing.
This page gives the market's orders of magnitude and our field experience, including when the conclusion is that now isn't the right time. You should be able to estimate your project within a few tens of percent before speaking to anyone.
At KERN-IT, we implement Odoo from Brussels for SMEs in Belgium and France. We have also been a Python shop for over 14 years, which puts us in an unusual position: we don't need to sell you Odoo to have work.
How much does an Odoo implementation cost?
For an SME, expect between €15,000 and €40,000 of implementation work for a multi-module rollout with data migration and training. Below €10,000 the scope is necessarily limited to one or two modules. Above €40,000 there is custom development or several integrations.
This implementation budget is separate from licences, which you pay directly to the publisher, per user per month. That's the most common confusion: the price shown on Odoo's website covers the software only, never its rollout.
The four line items that make up the bill
Odoo licences
Paid to the publisher, per user per month, with volume discounts depending on commitment. This is a recurring cost, to be projected over three years in your business case, not just the first year.
Implementation
The bulk of the initial budget: audit, scoping, module configuration, accounting setup, workflows and access rights. This is the line that varies most from one provider to the next.
Data migration
From €2,000 to €10,000 depending on the state of your existing data. A clean export from a recent ERP costs little; fifteen years of Excel files with duplicates costs a great deal more. This is the most systematically underestimated line.
Integrations and training
Each connection to a third-party tool costs €2,000 to €15,000 depending on the quality of its API. Training is counted in days, and it's the line you must never cut: an ERP nobody masters is worthless.
How long does an Odoo implementation take?
From 2 weeks to 4 months, depending on scope. Here are the three formats we most often see in SMEs, and what genuinely separates them.
2 to 4 weeks: one or two modules
Typically CRM and quotations, or invoicing alone. Simple data, few users, no integrations. The right format to validate Odoo before committing the whole company, and one we often recommend.
4 to 8 weeks: standard SME rollout
Several connected modules (sales, purchasing, inventory, accounting), migration of your historical data and team training. This is the most common scenario, and the one most quoted budgets are based on.
8 to 16 weeks: with development
As soon as a custom module or an integration with your existing tools enters the scope. The development itself is rarely the longest part: it's the back and forth of business validation.
A counter-intuitive point: what stretches an Odoo project is almost never the configuration. It's the quality of your data and your teams' availability. A client who frees up two days a week for the project moves twice as fast as one who answers questions on Friday evening. Nobody tells you this during the sales phase.
Odoo Community or Odoo Enterprise?
Community if you have a technical team and simple needs, Enterprise in every other case. In practice, the vast majority of SMEs we work with go with Enterprise, for one specific reason: full accounting isn't in Community.
Odoo Community
Free, open source, no per-user licence. You host and maintain it yourself. No Studio, no official mobile app, no full accounting, no advanced MRP, no publisher support, and version upgrades are on you.
Relevant if you already have a technical team, a well-defined need (often CRM or inventory) and a genuine appetite for open source.
Odoo Enterprise
Paid per user per month. You get Studio, the mobile app, full accounting with VAT returns, advanced MRP, publisher support and the version upgrade service.
This is the default choice for an SME that wants to run its accounting and VAT in Odoo, and doesn't want to employ someone full-time to maintain its ERP.
They trust us
Which modules should you start with?
The ones costing you time today, not the ones that demo well. The classic mistake is switching everything on from day one: your teams drown, adoption collapses and the project drags.
In most SMEs, the order that works is this: first the sales cycle (CRM, quotations, orders, invoicing), because that's where the financial argument is most visible and where buy-in is won. Then purchasing and inventory if you handle physical products. Then accounting, often in coordination with your accountant. Finally the business modules: projects, timesheets, HR, maintenance.
If you bill time rather than products, the order changes: projects and timesheets come before inventory. This is exactly the kind of trade-off the initial audit has to settle.
Five pitfalls that derail Odoo projects
1. Recreating the old system exactly
If you ask Odoo to behave precisely like your previous software, you pay for development to recover your old flaws. An ERP project is a chance to simplify processes, not to fossilise them.
2. Underestimating data migration
The line that overruns most often. Duplicate customers, inconsistent product references, incomplete history: the cleanup happens before the import, and it's work nobody enjoys quoting.
3. Stacking Studio customisations
Studio is perfect for small adjustments. But a stack of unversioned customisations quickly becomes unreadable and fragile at upgrade time. Past a certain threshold, a real module is cheaper to maintain.
4. Skimping on training
The first line cut when budgets tighten, and the leading cause of failure. A perfectly configured ERP that teams work around with parallel spreadsheets is a failed project, not an ongoing one.
When Odoo is not the right choice
No integrator's page will tell you this, so it may as well be said here. Odoo is excellent at classic management processes: selling, buying, stocking, invoicing, accounting. Yet there are situations where imposing it is an expensive mistake.
When your core business is genuinely specific. If your competitive advantage rests on a process nobody else has, bending it to fit a generalist ERP costs you precisely what sets you apart. A dedicated tool, connected to Odoo by API for the management side, is often healthier and cheaper to maintain.
When you are too small. Below a handful of users, with no inventory or manufacturing complexity, a good invoicing tool and online accounting are more than enough. An ERP mostly adds friction.
When the real problem is organisational. If your processes aren't clear, no software will clarify them. It will freeze them in their current disorder, and you will pay for that. Scoping must come before tooling.
We also build custom software: when we tell you Odoo is the right choice, it isn't because it's the only thing we know how to sell.
Business & ERP projects we've delivered
Articles liés
Frequently asked questions about Odoo implementation
Two separate lines. Licences: Enterprise is billed per user per month, so for 10 users you are looking at a few hundred euros monthly, with discounts depending on commitment. Implementation: between €15,000 and €40,000 for a standard multi-module rollout, less if you start with a reduced scope. Always check current licence pricing on Odoo's website, it changes.
Technically yes, and some companies manage it on a simple scope with a motivated internal profile. In practice, unsupported projects most often fail on three points: accounting setup, data migration and team adoption. A middle path works well: we scope and configure the foundation, your teams take it from there.
Market observations put the break-even point between 12 and 18 months for an SME, mainly through eliminating re-entry, faster invoicing and better inventory visibility. That's an average: a poorly adopted project never reaches it, which is why we insist so much on training.
No, and this is one of the best savings levers in the project. Migrate the live data (customers, suppliers, products, stock, open items) and only the history you need operationally or legally. The old system can stay available read-only for the mandatory retention period. Migrating fifteen years of invoices into a new ERP is expensive and almost never useful.
Odoo releases one major version per year. On Enterprise, the publisher offers a migration service. What causes trouble is never the standard: it's the customisations. Hence the importance of writing real versioned, tested modules rather than a Studio stack. A well-written module is upgraded in a few days; a fragile stack can strand you on an obsolete version for years.
Yes, as long as the tool exposes an API. We build bidirectional integrations between Odoo and your e-commerce, your website, your business software or your accounting. Expect €2,000 to €15,000 per connector, the range depending mainly on the quality of the API on the other side and the volume of data to synchronise.
In Belgium, yes, and they are significant: the digitalisation grant in Brussels, chèques-entreprises in Wallonia, the KMO-portefeuille in Flanders. A management tool like Odoo falls within eligible spending. In France, schemes are mostly regional. Conditions change regularly: check the official portal before building your budget around them. See our Odoo integrator in Brussels page for the Belgian detail.
Want a real number for your project?
Describe your processes and your context. We reply with a scope, an order of magnitude and a schedule, including if our conclusion is that you should wait or do it differently.