What a great ERP implementation actually looks like

Everyone has heard an ERP horror story: the project that took two years, the system nobody uses, the consultant invoices that never stopped. After 14 years and hundreds of rollouts, we can tell you the uncomfortable truth, the failures are rarely about the software. They're about how it was implemented.

Why ERP projects fail

Three patterns account for most disasters. First, buying from a demo: demos show the software at its best, not your business at its messiest. Second, customising on day one: bending the system to replicate every old habit, including the bad ones, before anyone has used the standard flow. Third, treating data migration as an afterthought, then discovering at go-live that the masters are garbage.

Discovery before demos

A serious partner starts by mapping how your business actually works, every register, approval and exception, before showing you a single screen. Discovery produces two things: a process map you'll recognise as your own, and a scope document that says what happens in phase one and, just as importantly, what doesn't.

If a vendor's first meeting is a demo and their second is a quotation, you're buying their sales process, not an implementation.

Configure first, customise later

Modern ERPs like Odoo cover 80–90% of a typical business's needs out of the box. The discipline is to go live on configured standard flows, run them for a cycle or two, and only then customise the gaps that proved real. Customisations written before go-live are guesses; customisations written after are engineering.

Data migration is the project

Charts of accounts, customer and vendor masters, item lists, open invoices, opening balances, cleaning and migrating these is routinely half the effort, and it's the half that determines whether people trust the new system on day one. Budget for it. Test it with a parallel run. Reconcile to the rupee before switching off the old books.

Training, go-live and hypercare

Train people by role, on their own data, days before go-live, not with a generic manual a month early. Go live at a natural boundary (a month or quarter start). Then plan for hypercare: two to four weeks where the implementation team answers within minutes, fixes small gaps daily and holds a short review with your leads every evening. This is where adoption is won.

How to judge a partner

• They ask about your processes before showing screens.
• They give a phased scope with dates, and say "no, not in phase one" at least once.
• They talk about data migration and reconciliation unprompted.
• They commit to named people for hypercare, not a ticket queue.
• They've implemented for your industry, ask to speak to one reference.

This is exactly the playbook behind our ERP & SaaS Implementation service, discovery, configuration, migration, training, go-live and hypercare, done right the first time.