Odoo implementation: frequently asked questions

A focused first phase covering sales, invoicing or accounting, inventory and purchasing for a single company typically runs a few months from discovery to go live. Adding manufacturing, eCommerce, projects or several legal entities extends that. The largest factors are the number of processes, the state of your data and how much time your team can give the project. We give you a timeline with the roadmap and update it at every phase boundary.

Usually not. We recommend going live with the core apps first, because that is where the data flows connect, and adding further apps in later phases once the core is stable. For groups, roll out is typically entity by entity using the first as a template. A single big go live is possible when the business needs it, but it carries more risk and needs more preparation.

More than most people expect. A project lead needs at least two days a week. Each key user needs time for workshops, testing and training, which can add up to several days per module. We estimate these hours per role and per phase in the roadmap so that managers can plan for them.

Where there is a clear business case, yes. Our default is to configure standard Odoo first, use existing modules second and write code last. Every customisation is documented with the reason it exists, because each one adds cost at every future upgrade.

Per module and per role, close to the point of use. Key users are trained as each module is configured and they in turn test it. End users are trained before go live with sessions, recordings and short written guides that you keep. We avoid a single large session a week before launch.

A hypercare period with daily contact for the first weeks, followed by handover to our managed service if you want ongoing support, or to your internal team with documentation and a knowledge base.