The ERP implementation process is one of the most important technology projects a growing business will take on, and one of the most misunderstood. Most of the anxiety around it comes from not knowing what actually happens, in what order, or what will be asked of your own team. This guide walks through every stage, from the first kick-off meeting to the month after go-live.
Whether you are replacing Sage, Xero or another finance system, knowing the shape of the project up front reduces uncertainty, improves planning and sets realistic expectations. Most of our projects reach go-live in eight to twelve weeks.
Why ERP implementation process has a bad reputation
The horror stories are real, but they usually share the same causes. Everything gets designed before anyone knows what they need. Training happens once, intensively, weeks before launch. Scope grows quietly. Nobody owns the decisions. And by the time the system goes live, the requirements it was built against are a year out of date.
None of that is inherent to ERP. It is a consequence of how the project is run. So before the stages, it is worth understanding the four principles we build every ERP implementation process around, because they exist specifically to remove those failure modes.
Pre-booked timelines. Workshops, meetings and training sessions are scheduled in advance to minimise diary conflicts and avoid the delays that quietly push a go-live date back by months.
Project blocks. Implementation and training are delivered in focused blocks rather than one intensive push. Users build confidence gradually, on strong foundations, before moving on to more advanced functionality.
A project board. Questions and requests that fall outside scheduled workshops go through the project support portal and project board, so communication stays organised and nothing gets lost in an email chain.
Deploy, then grow. Rather than attempting every possible feature on day one, the focus is on delivering the agreed solution successfully. Once your team is confidently using the system, further functionality comes as part of a continuous improvement roadmap.
You can see how this fits together, and why it makes ERP more accessible for a growing business, on our page.
The ERP implementation process, stage by stage
Every project is different, but most follow the same structured journey through nine stages.
1. Kick-off meeting
Every ERP implementation begins here. The session aligns expectations, introduces the methodology, confirms who is responsible for what, reviews timelines and milestones, and establishes how the two teams will communicate. It sounds administrative. It is the single biggest predictor of whether the rest of the project runs cleanly.
2. Configuration sessions
Configuration workshops design and build your agreed business processes in the system. Typical areas include sales processing, purchasing, finance setup, VAT configuration and core system settings. These continue until the agreed scope is complete.
3. Core data templates completed
While configuration is underway, your team completes the data templates. These capture what is needed to prepare your environment: customer records, supplier information, products, and opening balances where applicable. This is the stage that most often depends on you rather than us, so it is worth resourcing properly.
4. Core data imported
After review and validation, your data is imported. Getting it accurate and structured now pays off repeatedly later, something we cover in our guide to
Importing before training matters more than it appears. It means users learn in a system that reflects their own business, with their own customers and products in front of them, rather than a generic demonstration environment.
5. Training blocks
Training is delivered in structured blocks rather than one intensive session, so users learn progressively and retain it. Depending on your agreed scope, that may include the Kickstart block, Multi-Company, Inventory and Assembly, plus any additional modules your business needs.
6. User acceptance testing check-ins
As the build progresses, UAT lets your team validate that the system genuinely supports your agreed processes. Regular check-ins review progress, resolve outstanding questions, confirm processes work correctly and build confidence ahead of launch.
7. Go-live readiness
Before launch the project enters a dedicated readiness phase, confirming all agreed activities are complete and both teams are prepared for the transition.
8. Final checks
Final checks confirm data has been validated, users are prepared, processes have been tested and outstanding actions resolved.
9. Go-live
Once readiness is confirmed, the system becomes your live operational platform. This is the formal transition from your previous solution to your new ERP.
What happens after ERP implementation process timeline
Going live is the beginning of the journey, not the end, and this is where a lot of ERP projects are quietly abandoned by the people who delivered them.
Go-live check-ins. Scheduled sessions after launch provide guidance and get early questions answered quickly, while habits are still forming.
A month-end check-in. A dedicated review supports the finance team through the first month-end in the new system, which is the moment confidence is genuinely won or lost.
Handover to support. Once implementation activities are complete, you are formally introduced to the Business Applications Support team alongside our wider managed IT support. That structured handover gives you a clear route for ongoing help, future enhancements and long-term success, rather than wondering who to ring.
What affects an ERP implementation timeline
Every project follows a similar framework, but several factors move the overall duration:
The number of users involved. The complexity of your business processes. How much data needs migrating, and what state it is in. Any integrations with other systems, often built on the Power Platform. Custom development. Your team's availability for workshops and testing. And internal approvals.
The two most common causes of slippage are the two you control: data preparation and user availability. A well-planned project with engaged stakeholders keeps to schedule and minimises disruption.
Frequently asked questions
How long does the ERP implementation process take? Most of our implementations reach go-live in eight to twelve weeks. Duration depends on business complexity, data migration, integrations and user availability.
Why are project sessions booked in advance? Workshops are scheduled ahead of time to reduce diary conflicts, maintain momentum and minimise the delays that push out a go-live date.
How are questions handled during the project? Anything outside scheduled workshops goes through the project support portal and project board, so communication stays organised and traceable.
How is training delivered? Through structured project blocks rather than one long session, so users build knowledge progressively and actually adopt the system.
Can we add more functionality during the ERP implementation? We follow a deploy, then grow approach. The initial focus is delivering the agreed solution successfully, with further functionality introduced through later enhancement phases. This is deliberate: scope creep mid-project is one of the main reasons ERP implementations run over.
What happens after go-live? Structured support including go-live check-ins, a month-end review and a formal handover to the Business Applications Support team.
What does an ERP implementation cost? That is a separate question with three parts to it, and we have published our own prices in full in how much ERP software costs.
Thinking about an ERP implementation?
Tell us what you are running now, how many people need access, and what is breaking. We will tell you what the project would look like and what it would cost. Fixed scope. Fixed price. No scoping fee.
or