Typical timelines
| Project type | Typical apps | Timeline |
|---|---|---|
| Small business | Accounting, Invoicing, Sales, basic Inventory | 4–8 weeks |
| Mid-size company | + Purchase, multi-warehouse, POS, e-invoicing, 1–2 integrations | 8–16 weeks |
| Multi-company or manufacturing | + MRP, consolidation, approvals, several integrations | 4–9 months |
The phases
- Discovery and design (15–20% of the effort): process workshops, a fit-gap list and a signed solution design.
- Configuration (30–40%): chart of accounts, taxes, journals, warehouses, routes, price lists, approvals and reports.
- Data migration (10–20%): master data and opening balances, loaded and reconciled twice, once to test and once for go-live.
- Testing and training (15–20%): end-to-end scenarios run by your own key users.
- Go-live and hypercare (10%): cut-over, the first month-end close, and fixes.
What drives effort and cost
- Customisation. Every custom module adds build, testing and upgrade cost. We use standard Odoo first and customise only where it pays back.
- Integrations, such as Shopify, Salla, banks, payment gateways and e-invoicing platforms.
- Data quality. Duplicate customers, wrong costs and unreconciled balances must be fixed before migration.
- Decision speed. One owner who can approve within three days saves weeks.
- Edition and hosting. Odoo Online, Odoo.sh or on-premise affects what you can customise and how upgrades work.
How to keep it on time
- Go live with the core apps first, then add the rest in phase 2.
- Migrate open items and balances, not years of transaction history.
- Close the first month in Odoo with your accountant before calling the project done.
Starting from scratch? Read What is an ERP, and how does an Odoo implementation work? or see our Odoo services.
Need professional assistance?
KasemCPA can review your numbers, build the model properly or set it up in Odoo.