IMX impromatrix

Home / Insights / Implementation timeline

GUIDE · UPDATED JULY 2026

How long does an Odoo implementation take?

By the Impromatrix consulting team – Odoo since 2020, ERP since 2011

For a typical SME: 6–16 weeks from kick-off to go-live. Services companies land near the bottom of that range, manufacturers near the top. Here is the phase-by-phase breakdown – and what a one-month go-live actually requires.

Phase by phase (typical SME, 10–50 users)

Phase
What happens
Duration
Scoping & audit
Processes mapped, module list fixed, success criteria and cutover date agreed.
1–2 weeks
Configuration
Standard modules set up on a test database, iterated weekly with your key users.
2–6 weeks
Data migration
Master data cleaned and imported; opening balances land last.
1–3 weeks, parallel
Custom development
Only what scoping proved necessary – ideally very little.
0–6 weeks, parallel
Testing & training
Key users run real scenarios end-to-end; fixes; then training everyone else.
2–3 weeks
Go-live
Cutover on a weekend; hypercare support while the dust settles.
1 weekend + 2–4 weeks

By company profile

Profile
Total duration
Usual long pole
Services company, 5–15 users
4–8 weeks
CRM habits, timesheet discipline
Wholesale / trading, 10–40 users
6–12 weeks
Stock data quality, barcode processes
Manufacturing, 20–80 users
10–16+ weeks
BoMs, routings, costing method decisions

These assume a decision-maker who answers within a day and key users with real weekly hours for the project. Doubling every estimate is not pessimism if neither is true.

Can we go live in a month?

Yes, under strict conditions: standard processes you are willing to adopt as-is, one legal entity, clean data, and a decision-maker inside the project. CRM plus invoicing in 2–4 weeks is routine; a full trading-company ERP in 4 weeks only works with near-full-time client involvement.

What actually causes overruns?

Rarely the technology. The classics: key users with no time allocated, data cleaning discovered too late, scope additions mid-project ("while we’re at it…"), and accounting cutover pushed across a fiscal-year boundary. A fixed scope and a named decision-maker prevent most of it.

Big bang or phased rollout?

Under ~50 users, big bang usually wins: one cutover, no months of double entry. Phased per module makes sense for manufacturing (logistics first, MRP second) or multiple entities. Running old and new systems fully in parallel doubles everyone’s workload – avoid it beyond one accounting month.

When should we start to hit a specific date?

Count backwards: go-live needs a quiet period, not your season peak. A fiscal-year start makes accounting cleanest, but January slots fill up first – a mid-year cutover with imported opening balances works just as well and books far easier.

Want a realistic timeline for your case?

Tell us your modules, user count and data state – we will map it week by week, honestly, free.

Book a free consultation