Change Management: Getting Your Team to Adopt a New ERP

A company can select the perfect ERP system, configure it flawlessly, and migrate its data cleanly, and still fail. The reason is almost always the same: the people who were supposed to use the new system never truly adopted it. Software does not change a business; people using software differently changes a business. That is why change management, the deliberate work of guiding an organisation and its employees through a transition, is not a soft add-on to an ERP project but the discipline that determines whether the investment pays off. This guide explains how to get your team to embrace a new ERP rather than resist it, from the first announcement through the months after go-live.

Why adoption is the real finish line#

Project teams often celebrate go-live as the finish line, but a system that is technically live yet poorly used has delivered none of its promised value. The real finish line is adoption: the point at which employees use the new ERP correctly, confidently, and by default, without reaching for the old spreadsheet or the workaround. Until then, the company is paying for capability it is not receiving. Adoption is also fragile in the early days, when frustration is highest and old habits are strongest. Recognising adoption rather than launch as the goal reframes the entire effort, because it forces the project to keep investing in people well past the moment the software switches on, which is exactly when most teams mistakenly declare victory and walk away.

Start before the software: build the case for change#

Resistance grows in the absence of a reason. When employees do not understand why a familiar system is being replaced, they fill the silence with anxiety and rumour, and they conclude that the change is being done to them rather than for them. The antidote is to build and communicate a clear case for change long before go-live. Explain the problems with the current way of working, the concrete benefits the new system will bring to each group, and what will happen if nothing changes. Crucially, frame the benefits in terms that matter to the people doing the work, less duplicate data entry, faster approvals, fewer month-end fire drills, not abstract corporate goals. People support what they helped justify, and a case for change made early turns passive recipients into willing participants.

Secure visible executive sponsorship#

Employees take their cues from leadership, and nothing signals that a change is optional faster than an absent executive. A strong executive sponsor does more than approve a budget; they show up, communicate personally, remove obstacles, and settle disputes between departments that would otherwise stall the project. When a respected senior leader clearly states that the new ERP is the future of how the company works and holds people accountable for the transition, resistance loses its cover. When sponsorship is delegated to a junior manager or the IT department, employees rightly sense that leadership is not fully committed, and they hedge their own commitment accordingly. Sponsorship must be visible and sustained, not a single kick-off speech followed by silence. The sponsor's continued presence is one of the strongest predictors of successful adoption.

Identify and empower change champions#

Change spreads through peers more effectively than through mandates. Every department has respected individuals whose opinions colleagues trust, and enlisting these people as change champions or super-users turns them into a distributed engine of adoption. Champions are trained earlier and more deeply, they help shape the configuration so it fits real work, they answer questions from colleagues in plain language, and they surface problems back to the project team before those problems fester. Their influence is credible precisely because they are insiders, not consultants or executives. Choose champions for their standing among peers and their genuine interest, give them time away from their normal duties to do the role properly, and recognise their contribution publicly. A well-supported network of champions reaches corners of the organisation that formal training and top-down messaging never will.

Communicate early, often, and honestly#

Communication is the connective tissue of change management, and it fails most often by being too little, too late, or too polished to be believed. Effective communication starts early, repeats consistently, and travels through multiple channels because no single message reaches everyone. It is two-way: employees need forums to ask questions and voice concerns, and they need to see those concerns acknowledged and acted upon. Honesty matters enormously. If the new system will be harder in some ways, or if certain features will not arrive until a later phase, say so plainly; people forgive difficulty they were warned about but resent surprises that feel like broken promises. Tailor the message to each audience, tell people specifically what will change for them, and repeat the why far more often than feels necessary, because the audience is hearing it far less often than the project team is saying it.

Design training around roles, not features#

Training that marches through every screen and feature overwhelms people and teaches them little about their actual job. Effective training is organised around roles and the tasks each role performs: a warehouse clerk learns to receive and pick, an accounts-payable specialist learns to process invoices, and neither is forced to sit through the other's material. Use realistic scenarios drawn from the company's own work rather than generic demonstrations, and give people hands-on practice in a training environment where mistakes are safe. Timing matters too: training delivered months before go-live is forgotten, while training delivered just before launch stays fresh. Reinforce it with quick-reference guides, short videos, and the champion network so that when someone is stuck at their desk on day three, help is close at hand rather than a distant memory of a classroom session.

Support the go-live and the productivity dip#

No matter how well prepared a team is, the first weeks on a new ERP are hard, and productivity almost always dips as people learn. This dip is normal and temporary, but if it is not anticipated and supported, it breeds panic and blame that can permanently sour attitudes toward the system. Plan for it. Provide intensive on-the-floor support during go-live, with champions and consultants visible and available to answer questions in real time. Set realistic expectations with leadership so that a temporary slowdown is understood as part of the plan rather than evidence of failure. Track and rapidly resolve the issues that emerge, because a problem fixed quickly builds confidence while a problem left festering confirms every skeptic's fears. The goal is to make the difficult first weeks feel supported rather than abandoned.

Measure adoption and act on resistance#

You cannot manage what you do not measure, and adoption is measurable. System usage data reveals who is logging in, which transactions are being processed in the ERP versus routed around it, and where old workarounds persist. Combine these metrics with direct feedback from champions and surveys to build an honest picture of where adoption is strong and where it is faltering. When resistance shows up, treat it as information rather than insubordination: a team clinging to a spreadsheet may be signalling that the new process genuinely does not work for them, or that they were never properly trained. Diagnose the cause and respond, whether that means fixing a configuration, delivering more training, or addressing a legitimate concern. Persistent, willful resistance eventually requires accountability, but most resistance dissolves once its underlying cause is understood and addressed.

Sustain adoption after go-live#

Change management does not end when the go-live support team packs up. New employees join and need training, staff turn over and take knowledge with them, the business evolves and requires new processes, and the vendor releases features that could add value if anyone adopts them. Without ongoing attention, hard-won adoption decays and old habits creep back. Sustaining adoption means embedding ERP training into onboarding, keeping a smaller champion network alive, maintaining up-to-date reference materials, and periodically revisiting how well the system serves the business. Celebrate and share the wins the ERP delivers, because visible benefits reinforce the behaviours that produced them. Treat the system as a living capability to be continuously improved rather than a project that concluded at launch, and the adoption you worked so hard to build will hold and deepen over time.

Frequently asked questions#

When should change management start? As early as possible, ideally at the very beginning of the ERP project rather than as a rush near go-live. The case for change, executive sponsorship, and the champion network all take time to establish, and early involvement gives employees a sense of ownership that late communication can never manufacture. Change management that starts only when training begins has already missed its most valuable window.

How do we deal with employees who refuse to adopt the new system? First understand why. Much apparent resistance is really a signal of a real problem, missing training, a broken process, or a legitimate concern that was never heard. Address those causes and most resistance fades. For the few who refuse despite genuine support, accountability becomes necessary, backed clearly by leadership, because allowing a visible holdout to keep using the old way tells everyone else that adoption is optional.

Conclusion#

The technical success of an ERP means little if the people it was built for do not embrace it. Adoption is the true measure of return, and it is won not by chance but by deliberate change management: building the case for change early, securing visible executive sponsorship, empowering peer champions, communicating honestly, training around real roles, supporting people through the difficult first weeks, measuring adoption, and sustaining it long after launch. Each of these is a choice a project can make or neglect, and together they separate the ERP investments that transform a business from the expensive systems that gather dust. Put people at the centre of the effort, and the technology will finally deliver what it promised.