The most expensive ERP is the one nobody uses. Across enterprises, the pattern repeats: a large platform is procured, configured to the vendor's reference model, and then quietly worked around because it does not match how the business actually moves goods, money and people. The spreadsheets come back. The ERP becomes a system of record nobody trusts.
Fit comes before features. Before any module is switched on, the work is to map how your organisation actually runs — procurement cycles, approval chains, how cash moves, where exceptions happen. An implementation that starts from your processes will be adopted; one that starts from a template will be resisted.
Integration is where most value is won or lost. An ERP that cannot talk to your payroll, your bank or your reporting stack is just another silo with a bigger price tag. APIs and middleware turn a new system into part of your estate rather than a fragment of it.
Data migration deserves real respect. The legacy data you carry in is the data your people will judge the new system by on day one. Plan the migration as its own piece of work — clean, map, validate and reconcile before go-live.
Then instrument and hand over. A live ERP should be observable, and runnable without the implementer in the room. Capacity-building is not an add-on; it is what makes the investment durable.