Blog · Rescue

Signs your ERP implementation needs a rescue

22 April 2026 · Shivanand Banahatti

Most “failed” ERP programmes I take over are not missing software — they are missing a frozen scope, an honest cutover plan, and an internal owner with authority. If several of the patterns below sound familiar, you are not alone; a stabilisation phase can still be shorter than restarting from zero.

Red flags

UAT never finishes — every demo raises new “small” requirements; go-live date keeps sliding.
Parallel spreadsheets — teams still trust Excel for stock or sales because the ERP numbers feel unreliable.
No single product owner — IT, finance, and ops each expect someone else to decide.
Customisation without tests — scripts landed in production without documented acceptance criteria.
Data migration deferred — “we will enter opening later” while expecting full GST reporting.

What a rescue engagement usually does first

Inventory the live system: version, apps, custom apps, critical DocTypes, integrations.
Define a minimum go-live slice: which transactions must be native to ERPNext on day one.
Fix master data and tax templates; reconcile a pilot warehouse or branch before scaling.
Backlog everything else with dates — so scope creep becomes visible, not ambient.

When a full re-implementation is justified

Rare. It happens when the data model is wrong for the business (e.g. wrong company structure) or when technical debt blocks upgrades. More often, hardening and phased cutover recover the investment already made.