How do you encourage users to let go of old processes during an ERP implementation?
Consulting Business Information Framework: Process
Resistance to Change in ERP Implementations
One of the most common and persistent challenges encountered during Enterprise Resource Planning (ERP) implementations is resistance to change. This resistance often stems from stakeholders who have grown accustomed to their existing ways of working. These legacy processes may have evolved over time to meeting specific departmental needs. As such, they are often viewed as tried-and-tested methods uniquely suited to the current organisational structure. For many employees, these familiar processes bring a sense of control, predictability, and comfort. Consequently, when “As-Is” Process mapping begins during the initial stages of the ERP project, there is frequently a strong inclination among stakeholders to preserve these established workflows rather than explore opportunities for transformation.
Risks of Replicating Legacy Processes
This reluctance to change can manifest as a desire to replicate current processes with the new ERP system. While this may appear to be a lower-risk approach, it actually undermines the strategic benefits that ERP solutions are designed to deliver. The true value of ERP lies in its ability to standardise and streamline operations, introduce good modern methodologies, and enable cross-functional integration. Insisting on customising the new system to mimic legacy processes not only reduces these benefits but also increases the complexity of the implementation. Customisations can be costly, time-consuming, and difficult to maintain, often resulting in higher long-term costs and reduced flexibility for future upgrades or improvements.
The Role of Change Management
To address this challenge, effective change management must be embedded throughout the ERP project lifecycle. Change management is not a one-off activity, it requires continuous communication, education, and engagement with all stakeholders. It begins with clearly articulating the rationale for change: Why is the organisation investing in a new system? What are the expected benefits? How will these changes support both organisational goals and individual roles? By providing this context early in the process, organisations can begin to shift mindsets from fear of loss to anticipation of improvement.
Involving Stakeholders in the “To-Be” Processes
Equally important is involving stakeholders in the design of the “To-Be” processes. When individuals feel that their insights and concerns are heard and valued, they are more likely to become active participants in the change rather than passive resisters. Demonstrating how the new system can improve efficiency, increase data visibility, reduce manual effort, and support better decision-making helps build a compelling case for change. Additionally, offering training, resources, and support throughout the transition period ensures that users feel confident and prepared for their news ways of working.