ERP change management prepares a business and its people for new processes, responsibilities and ways of working. Done well, it helps employees adopt the system, improve how work gets done and make better-informed decisions. Ultimately, success comes down to one question: has the ERP investment delivered measurable business value?
The groundwork for that return on investment is set in Phase Zero – the initial stage of ERP change management. In Phase Zero, leaders align on what the ERP must improve, who owns the change and what needs to be ready before teams are asked to work differently.
For mid-sized Australian and New Zealand businesses with lean teams managing day-to-day operations, a phased approach helps keep ERP change practical while protecting critical work.
Drawing on real examples from local mid-sized businesses implementing MYOB Acumatica, this guide explains a five-phase approach to ERP change management. It shows how to prepare people, build ownership and readiness, protect continuity, and support the operational change needed to realise a return from your ERP investment.
Key takeaways
Protect ERP ROI early. Phase Zero aligns the business outcomes, ownership and readiness needed to turn ERP investment into measurable return.
Design around real work. Focus on the processes, decisions, reports and workarounds the ERP must improve.
Prepare teams to change how work gets done. Role-based practice, reliable data and clear support help employees adopt the new way of working with confidence. Where AI features are part of the new process, test the relevant data and controls before the launch.
Protect business continuity through go-live. Plan how critical finance, compliance, and operational activity will continue while teams move to the new system.
Reinforce adoption after launch. Measure whether the ERP is being used to run critical processes, support decisions, and replace the manual workarounds that dilute ROI.
A five-phased ERP change management framework
An ERP change management plan should connect business readiness with technical delivery across five phases.
Phase | Business objective | What good looks like? |
|---|---|---|
Phase Zero: Align | Define what the ERP must improve, who owns the change and what needs to be ready | Outcomes, decision rights, readiness gaps and success measures are clear |
Phase One: Design | Design critical processes around the work, decisions and reporting the ERP needs to improve | Future workflows reflect real exceptions, controls, decision needs and reporting requirements |
Phase Two: Prepare | Prepare teams to perform role-specific work in the ERP, and prepare the data and controls needed for AI-supported work | People can complete relevant tasks, data is validated and support routes are clear |
Phase Three: Transition | Keep critical finance, compliance and operational activity moving during the transition | Responsibilities, escalation paths, continuity plans and output checks are clear |
Phase Four: Reinforce | Embed the ERP as the system of record for critical work and decisions | Teams use the ERP consistently, workarounds reduce and information is trusted |
Phase Zero: align outcomes, ownership and readiness
Phase Zero is the discovery, alignment, and readiness stage before software configuration and data migration begin. ERP change needs a clear business reason that leaders can communicate, and teams can act on. Without that shared direction, implementation can become a system project rather than a business change.
Most businesses don't have a technology problem. They have an alignment problem. The challenge is rarely whether teams can see the issue. It's whether the organisation is aligned enough to act on it.”
During Phase Zero, leaders align the business by defining what success looks like, mapping how work happens today, and assessing whether the business has the ownership and readiness to support the change.
1. Define success in business terms
“Implement a new ERP” is a project output, not a business outcome. Decide what should improve: perhaps less manual work, clearer financial and operational visibility, stronger control or more consistent processes.
Ask:
What should become faster, easier, or more reliable?
Which decisions should be better informed?
Which risks should be reduced?
What should employees no longer have to do?
How will we know the investment is working?
The answers should guide decisions throughout implementation and adoption.
2. Map how work happens today
Document the systems, spreadsheets, approvals, duplicate data entry, and informal knowledge that hold key processes together.
Not every workaround is wrong. Some preserve a genuine business requirement; others are simply familiar. Ask which requirements the future process must preserve and which workarounds should no longer be necessary.
3. Assess readiness and establish ownership
ERP readiness is the business’s ability to support the people, process, data and governance changes required for implementation and adoption. Before moving forward, leaders should be clear on three things: who owns the outcome, whether teams have capacity to support the change, and whether the data and decisions needed for implementation are ready.
Readiness depends on clear ownership and the right support around the business. A senior sponsor should own the outcome and help resolve cross-functional issues, while process owners, internal champions and the implementation team should be clear on their roles from the start.
For mid-sized businesses in Australia and New Zealand, MYOB Acumatica’s accredited partner community can bring local industry, regional and workflow expertise to help guide decisions about process design, data, rollout and support before implementation pressure builds.
Phase One: design the future way of working
Once outcomes and readiness gaps are clear, design should focus on the work the ERP needs to improve. For each critical process, clarify the business result, required controls, key decisions, exceptions and where manual effort, delays, or duplicate handling should be reduced.
For example, Residentia moved from Xero for financial management and Unleashed for inventory to MYOB Acumatica after rapid growth exposed gaps between finance, stock control and order handling. Designing the future way of working meant connecting electronic trading, inventory forecasting and live reporting, so teams could reduce spreadsheet workarounds, improve stock visibility and make supply-chain decisions from more reliable information.
The key is to involve the people who do the work before decisions are locked in. They can highlight exceptions, approval delays, duplicated data and workflow friction that may otherwise be missed. This helps ensure the future process design is practical, adoptable and able to support the return expected from your ERP investment.
Phase Two: prepare people, processes and data
Preparing employees for ERP change means giving them the context, practice and support they need to perform their real work in the new system. A finance user, warehouse manager, project lead and executive will each use the ERP differently, so role-based preparation should focus on the transactions, decisions, exceptions, reports and support routes that matter to each role.
Use realistic scenarios and representative data. If AI-assisted processes are part of the future operating model, preparation should also cover the data quality, governance, and controls needed to make outputs reliable. Leaders should be confident that the information feeding reports, recommendations, alerts or automated actions is accurate, well-structured and appropriately controlled. Teams should also confirm who owns data cleansing, validate migrated records, and test complete workflows using outputs that matter to business decisions. Poor-quality data, weak configuration, and poor integrations can undermine trust in ERP outputs, slow adoption and reduce the value of the change.
Before launch, appoint trusted champions and peer supporters who can help teams practice new workflows and raise adoption issues early.
In practice, these trusted supporters often become the first people colleagues turn to with questions about workflows, reporting, exceptions or day-to-day system use. That local support helps reinforce confidence long after formal training has finished.
Want to understand how peer support helps ERP adoption move beyond go-live? Read How change champions and peer support can improve ERP user adoption
Phase Three: protect the business through go-live
Business continuity during ERP go-live means protecting critical operational, financial and compliance activity while moving to the new system. A staged rollout may spread change across functions, locations, or brands. An all-at-once rollout may shorten the transition but concentrates activity around launch. Choose the sequence your business can absorb, based on dependencies, capacity, complexity, operational peaks, and the consequences of interruption.
For example, when Signature Hospitality Group introduced MYOB Acumatica, CFO Andrew Spittal managed the rollout brand by brand while keeping business-as-usual activity moving. He understood that go-live pressure is not only technical; it also affects people, capacity, and momentum.
The hardest part is the change management with the team and managing BAU with UAT. Burnout is real, project fatigue is very real."
That is why go-live planning needs to make responsibilities, support routes and decision points clear before launch. Employees should know who owns critical decisions, where support requests go, how issues will be escalated and how important outputs will be checked.
For Australian and New Zealand businesses, this should cover critical finance, payroll, compliance and operational processes, such as financial close, GST/BAS, Single Touch Payroll, customer orders, inventory movements and project billing.
Phase Four: reinforce ERP adoption after go-live
ERP adoption means people consistently use the new system to run the work, make decisions, and trust the outputs it produces. After go-live, the priority shifts from launching the ERP to embedding the behaviours, expectations and support needed for the ERP investment to keep delivering value.
As Joel Ramirez, Head of Partner Growth and Ecosystems at MYOB Acumatica, explains:
“Phase Zero is still critical. It's where you align on the why, map current state and set up governance. But adoption must be led and reinforced well beyond go-live. That means sustained executive sponsorship, ongoing training and a clear expectation that the ERP is the system of record, not an optional extra.”
If employees return to spreadsheets, side processes, or familiar workarounds, treat it as a signal rather than a failure. It may point to unclear processes, poor data confidence, gaps in training, integration issues, or unresolved ownership. The response should be practical: identify why the workaround exists, fix the underlying issue, and reinforce the agreed way of working.
To understand how adoption drift can undermine ERP value after go-live, read: Leadership lessons from 5 ERP implementation failures.
Are you ready for Phase Zero?
Phase Zero is a critical part of ERP change management. It is your key opportunity to align on the outcomes, ownership and operating changes needed to turn your investment into measurable outcomes.
Phase Zero is the time to answer the questions that determine whether the business is ready to support implementation, drive adoption and achieve ROI:
What business outcomes must the ERP investment support?
Which processes, decisions, and reports need to improve?
Which workarounds should disappear, and which business requirements must be preserved?
Who owns the outcome, process decisions, and readiness gaps?
What data, capacity, or governance issues could put implementation or adoption at risk?
Which critical operations need protection during go-live?
How will adoption be reinforced and measured after launch?
The aim is not to remove every risk. It is to identify the risks most likely to weaken ROI early, so leaders can make clear decisions, assign ownership, protect critical operations, and keep adoption moving after go-live.
Frequently asked questions
What is ERP change management?
ERP change management is the structured work of preparing and supporting an organisation and its people as they adopt the new processes, responsibilities and ways of working introduced by an ERP implementation.
What is Phase Zero in an ERP project?
Phase Zero is the discovery, alignment and organisational-readiness stage before configuration and migration. It defines business outcomes, maps the current state, identifies gaps and establishes ownership.
Why does ERP adoption fail?
ERP adoption can break down when the system or process doesn’t support real work, employees don’t trust the data, preparation isn’t relevant to their roles, ownership is unclear or old workarounds remain easier.
Who should own ERP change management?
A senior sponsor should be accountable for the outcome, but delivery should be shared across the project lead, process owners, managers, champions, employees and implementation partner.
How do you prepare employees for ERP change?
Involve employees in validating workflows, explain how and why their work will change, provide role-based training using realistic scenarios and offer clear support before and after launch.
Information provided in this article is of a general nature and does not consider your personal situation. It does not constitute legal, financial, or other professional advice and should not be relied upon as a statement of law, policy or advice. You should consider whether this information is appropriate to your needs and, if necessary, seek independent advice.
This information is only accurate at the time of publication. Although every effort has been made to verify the accuracy of the information contained on this webpage, MYOB disclaims, to the extent permitted by law, all liability for the information contained on this webpage or any loss or damage suffered by any person directly or indirectly through relying on this information.
Contributors
MYOB Subject Matter Experts