An ERP implementation is one of the most demanding projects an organisation can undertake, requiring significant investment, time and commitment from people across the business. Teams need to manage the project alongside their everyday responsibilities, while preparing for changes to how they work. Clear priorities, realistic planning and the right support from the outset give the implementation the best chance of success.
What helps an ERP implementation succeed
At Optimum PPS, we have supported more than 300 ERP and digital transformation projects across manufacturing, engineering, charities and other sectors. Our experience shows that successful implementations need clear business objectives and realistic plans, backed by leaders who stay involved. They also depend on giving people the time and support to prepare data, test processes and adopt new ways of working.
This guide sets out ten practical steps for CEOs, CFOs, COOs and technology leaders overseeing an implementation. It focuses on what to put in place and the evidence to review as delivery progresses.
The 10 steps at a glance
-
1Agree measurable business outcomesA clear definition of success that guides every decision
-
2Define scope and requirementsA shared baseline for design, testing and go-live
-
3Agree the change process before you need itChanges handled quickly, without derailing the plan
-
4Set decision-making responsibilitiesOpen decisions, owners and response deadlines
-
5Get the right people in place at the right timeExperienced decision-makers, without the business suffering
-
6Build a network of subject matter expertsProcesses that reflect reality, and support close to users
-
7Assign data migration ownershipClean, trusted data at go-live
-
8Test complete business processesCritical scenarios, defect impact and financial results
-
9Prepare users and rehearse the transitionTraining, cutover rehearsals and readiness evidence
-
10Plan for the weeks after go-liveSupport capacity, stability criteria and benefits progress
1. Agree measurable business outcomes
Before anyone talks about configuration, agree on what the business is trying to achieve. Faster month-end, reliable stock figures, better information for frontline teams, fewer spreadsheets: whatever the goals are, write them down and make them measurable.
Those outcomes become the test for every later decision. When a request for a new report or a workflow change comes in, the question is simple: does it help us get there? Our guide to building an ERP business case explains how to set outcomes and baselines.
Quick wins
- Agree three to five measurable outcomes and share them with the whole project team
- Record a baseline for each one now, so you can show improvement later
- Give each outcome a named owner in the business
2. Define scope and requirements
Outcomes say what you want to achieve. Scope and requirements say what the system will do to get you there. Agree which processes, sites, modules and integrations are in, which are out, and what each area needs the system to do.
Write it down and get it signed off by the people who will own the results. That agreed scope becomes the baseline for everything that follows: design, testing, training and, crucially, the go-live decision. “Ready” then has a clear meaning: the agreed scope has been delivered and tested, and the business is prepared to use it.
Quick wins
- Document what is in scope and out of scope, and get business sign-off
- Separate the requirements you must have at go-live from those that can follow later
- Use the agreed scope to set your go-live criteria, so readiness is judged on evidence, not the calendar
3. Agree the change process before you need it
As teams work through the detail of an ERP implementation, they may identify additional requirements or opportunities to improve a process. Each request needs careful consideration, as even a small adjustment can create extra work across configuration, testing and training.
Agree how the team will assess and approve changes before delivery begins. Each request should explain the business need, the expected benefit and the effect on budget, resources and timescales. Make approval responsibilities clear and record decisions so everyone understands what has changed and why.
This helps the team respond to new requirements while keeping control of the scope and delivery plan.
Quick wins
- Agree a simple change request form and a single place to log every change
- Assess each change against the agreed scope, cost, timescale and go-live date
- Set clear approval levels, so small changes move quickly and more complex changes get the right scrutiny
Key insight
A change process is not there to stop change. It is there to make sure every change is a conscious decision, with its impact understood before it is approved.
4. Set decision-making responsibilities
ERP projects generate multiple decisions across functions and suppliers. An unresolved process question can hold up configuration, data preparation and testing at the same time. Leaders need visibility of those consequences before the delays affect the wider timetable.
Name an executive sponsor with the authority and availability to resolve cross-functional issues. Agree what the project team can decide, what process owners must approve and what needs steering group intervention. Make supplier responsibilities clear too.
Set response times according to urgency. A decision blocking critical testing may need an answer much sooner than an optional reporting improvement. Keep a record of the decision, the reasoning and who approved it.
Quick wins
- Agree decision rights at the start: what the project team decides, and what goes to the steering group
- Keep a decision log and review it at every steering meeting
- Set a target turnaround for decisions, such as one week, and track it
Growtivation
When Growtivation, a UK supplier to the building, landscaping and horticultural sectors, implemented a cloud-based ERP, Optimum PPS supported the programme from requirements and selection through design, data migration, testing, cutover and go-live. Project governance was maintained throughout to keep stakeholders, suppliers and delivery activity aligned.
5. Get the right people in place at the right time
Your most experienced people are vital to the project, but they are also vital to the business. Take them out of their day jobs entirely and the business suffers. Leave them out of the project and decisions get made without the knowledge they need.
The answer is balance. Plan when each key person is needed, for design, decisions, testing or sign-off, and involve them at those points, while others carry more of the day-to-day project work. That creates a real opportunity: an implementation is a chance to upskill and develop people, giving them new knowledge of the system and the wider business that stays with the organisation long after go-live.
Quick wins
- Map when each key person is needed, by phase, rather than assigning them full time by default
- Pair experienced decision-makers with people who can take on more of the hands-on project work
- Treat the project as a development opportunity, and plan who will grow into new roles through it
- Bring in specialist support, such as project, data or change management, where you have gaps
Finsbury Food Group
At Finsbury Food Group, acquisitions had left eight UK manufacturing sites with their own systems and ways of working. Optimum PPS added specialists in project management, change management and data migration to Finsbury’s own team, and the group rolled out Infor M3 site by site, carrying the lessons from each site into the next.
6. Build a network of subject matter experts
Subject matter experts (SMEs) understand how their area of the organisation works. They help define requirements, review the design and test whether the system meets business needs. Bringing them together across departments helps identify gaps in processes and handovers before those gaps cause problems in live use.
Super users develop the system knowledge to train and support colleagues, answer everyday questions and raise issues with the project team. The same person can fulfil both roles, provided they have enough time and preparation.
Together, these roles help reduce avoidable rework during implementation and give staff practical support to keep day-to-day operations running after go-live.
Quick wins
- Name an SME for each key process area, chosen for their knowledge and the respect of their colleagues
- Hold a regular SME forum where experts from different areas share issues and ideas
- Prepare super users to support colleagues during training, go-live and the weeks afterwards
RoSPA
More than 70% of RoSPA’s staff took part in workshops during the early stages of a wide-ranging systems programme. That involvement helped build a clear picture of how information moved across the charity before the future approach was defined.
7. Assign data migration ownership
Data migration is one of the most underestimated parts of any implementation. Duplicate suppliers, inconsistent product records and out-of-date customer details all travel into the new system unless someone deals with them first.
The fix is ownership. Give each major set of data, such as customers, suppliers, products or employees, a named owner in the business. They decide what moves, what is archived and what “clean” looks like.
Quick wins
- Start profiling and cleansing data early, ideally before design is finished
- Run several trial migrations, and check the results each time
- Agree sign-off criteria for data quality before go-live
8. Test complete business processes
A system can process every transaction correctly and still fail to support a normal working day. Good testing follows real scenarios from start to finish, with real data, real roles and the awkward exceptions that happen in practice.
A food manufacturer might test batch traceability and quality holds alongside production and dispatch. An engineering business might check material issues, work in progress and job costs. A charity might test restricted-fund reporting and information transferred from other applications.
Check financial integrity as part of those scenarios. Finance should reconcile opening balances and confirm that operational transactions create the expected accounting entries, supporting accurate reporting, controls and audit requirements.
Quick wins
- Write test scenarios around real events, such as a customer order from receipt to invoice
- Reconcile opening balances, stock values and open items between the old and new systems
- Check that operational transactions, such as stock adjustments, post correctly to the finance ledgers
- Get finance to sign off the numbers, not just the processes, before go-live
- Review unresolved defects by business impact and record the results of retesting
CEDO
During CEDO’s multi-site ERP implementation, Optimum PPS supported scenario-based testing across data, integrations and business processes. This helped the team check that the system could support live business activity, not just complete isolated transactions.
9. Prepare users and rehearse the transition
People need to practise the tasks they will carry out in their roles and understand how their decisions affect colleagues. Build training around those tasks, using familiar examples and a suitable training environment.
Where someone needs more practice or a process remains unclear, address that before launch. Plan how shift workers, part-time colleagues and staff across different sites will receive support.
The transition itself needs a detailed cutover plan covering final data transfers, checks, responsibilities and communications. Rehearse critical activities so the team understands timings and dependencies. Agree contingency arrangements and the circumstances in which leaders would pause or defer launch.
Bring the evidence into the go-live decision
Consider these together:
Quick wins
- Organise training by role, using the scenarios from testing
- Explain the “why” behind process changes, not just the “how”
- Provide simple guides and a clear place to ask questions after training ends
Penumbra
For Penumbra, an Edinburgh-based mental health charity, Optimum PPS worked as an extension of the team, supporting governance, delivery, change management and solution management. The programme helped staff build confidence in new mobile and self-service ways of working, reducing reliance on paper information and improving access to service user records.
10. Plan for the weeks after go-live
The first weeks after launch need planned support and clear priorities. Agree how users will raise problems, who will assess them and when suppliers need to intervene. Keep enough internal capacity available to resolve issues affecting live work.
Plan this extra support, often called hypercare, before go-live. Once the system is stable, turn attention to the outcomes you set at the start, and to the requirements you agreed to deliver later, and keep improving.
Quick wins
- Keep the project team and SMEs available for the first few weeks
- Hold a short daily meeting to triage issues and agree fixes
- Schedule reviews of the outcomes established at the start of the project
Fern Plastic Products
Fern Plastic Products needed to get more value from its business system after moving from a make-to-order model to a supply chain-driven one. After Optimum PPS realigned and optimised its supply chain processes and system, customer delivery performance rose from 75% to 98%, supplier delivery performance from 75% to 95%, and additional transport costs fell by 75%.
Key insight
The value of an ERP system is not fixed at go-live. Organisations that keep reviewing and improving after launch get far more from the same investment.
Summary
A smooth ERP implementation comes from doing simple things well and consistently. Set clear outcomes, agree scope and how changes will be handled, decide quickly, get the right people involved at the right time, build a network of subject matter experts, own your data, test real days and make sure the numbers balance, train for real jobs and plan for life after go-live.
Optimum PPS: independent ERP implementation support
An ERP implementation can place significant demands on your team. Optimum PPS provides independent support across project management, change management and data, adding expertise and capacity where you need it.
We work alongside your people to resolve delivery challenges, prepare for go-live and keep the programme focused on the improvements your organisation needs.
Planning an ERP implementation?
Book a free 30-minute consultation
Opens a new email to Stephen Douglas, Business Development Manager
About the author
Martin Munsie, Consultant LinkedIn
Martin Munsie is an experienced consultant at Optimum PPS with a strong background in engineering and manufacturing. He specialises in system selection, implementation and process improvement, helping organisations strengthen their processes and get more from their business systems.
FAQs: ERP Implementation
How much staff time does an ERP implementation require?
Staff time depends on scope, complexity and the implementation approach. Estimate the commitment by role and phase, covering design, data, testing, training and cutover. Some roles may need substantial dedicated time. Agree cover for normal duties and revisit resource commitments as the plan develops.
Who should own ERP data migration?
Business owners should approve the quality, completeness and suitability of their data. The technical team manages extraction, transformation and loading, working with those owners to resolve problems. Finance should approve reconciliations of balances and transactions, with clear responsibility for other critical data areas.
What are subject matter experts in an ERP project?
Subject matter experts are staff who understand the processes and practical requirements of their area. They help shape the design, test the system and prepare colleagues for change. Some may also become super users who provide day-to-day system support.
What data do food manufacturers need for AI?
Document assistants need approved, current source material. Planning applications need orders, usable stock, batch expiry, quality holds, yields, capacity and promotional data. In every case, records need consistent definitions and clear ownership across systems.
How do you assess ERP go-live readiness?
Use agreed criteria covering critical processes, data reconciliation, integrations, user preparation, cutover and support. Review unresolved defects by business impact and confirm contingency arrangements. Record any remaining risks, the actions needed to manage them and who accepts them before approving launch.
What is ERP hypercare?
ERP Hypercare is a period of extra support immediately after go-live, typically a few weeks, when the project team stays close to users to fix issues quickly before normal support arrangements take over.
How do you measure benefits after ERP go-live?
Compare performance with the baselines and targets agreed before implementation. Use consistent measures, such as reporting time, stock accuracy, delivery performance or administrative effort. Business owners should review the results and agree corrective actions where expected improvements haven’t materialised.
