ERP modernisation starts before platform selection

Define the reason for change

An ERP programme is easier to steer when the business can explain why it is needed. Slow reporting, fragmented inventory visibility and manual reconciliations are different problems. Each calls for a different definition of success.

Translate broad ambitions such as modernisation into operational outcomes. Identify the process owners who can explain the current constraints and who will be accountable for improvements.

Understand the process beneath the workaround

Spreadsheets, email approvals and local applications often compensate for gaps in the existing process. Replacing the ERP without understanding those workarounds can recreate the same problems in a new interface.

Map a few critical end-to-end processes before producing a detailed feature list. Trace handoffs between functions, identify exceptions and distinguish necessary business variation from accidental complexity.

Treat data as a programme workstream

Master data decisions affect migration, integration, reporting and daily operations. Establish who owns key records, which source is authoritative and how quality will be assessed.

Migration planning should include reconciliation and acceptance criteria, not only field mapping. Decide how the business will confirm that opening balances, orders and other critical records are complete and usable.

• Name business owners for critical data.
• Agree quality and reconciliation checks.
• Plan trial migrations before cutover.
• Define how historical information will be accessed.

Evaluate platforms against a shared baseline

A requirements baseline helps compare platforms consistently. Include operational fit, integration needs, deployment constraints and the support capabilities your organisation will need after launch.

Use representative business scenarios in evaluations. Ask how the platform handles the exceptions that matter, not only the standard flow. Record where a requirement needs configuration, custom development or a process change.

Design for adoption and continuity

Testing and training are more useful when they follow real business roles. Involve users in validating the workflows they will own, and provide a route for resolving issues after go-live.

Sequence delivery around readiness and dependencies. A clear cutover decision, an agreed support model and practical fallback arrangements can matter as much as the platform choice itself.