ERP implementation: what are the 8 key steps of the project?
A successful ERP project is not won at the moment you pick the software, but in the way you roll it out. Scoping, requirements, configuration, data migration, training, go-live: here are the 8 key steps of an ERP implementation, with the duration and budget benchmarks, and the pitfalls that derail projects.
TL;DR, the essentials
- An ERP implementation is structured in 8 steps: scoping, requirements, solution selection, configuration, data migration, training and change management, go-live, then stabilization (hypercare).
- Typical duration runs from 6 to 18 months depending on size and scope: 3 to 9 months for a well-scoped SMB, 12 to 18 months for a multi-site mid-market company.
- The software is only 10 to 25% of the budget: most goes to integration, data migration, training and maintenance.
- The two major causes of failure: an underestimated data migration and neglected change management.
You have decided to move to an ERP, or you are about to, and you want to know what the project actually looks like. Good news: an ERP implementation follows a proven path, split into clear steps. Bad news: each one hides a pitfall that can derail the whole thing. Below we detail the 8 key steps, the duration and budget benchmarks, and the mistakes to avoid. For the upstream step, selecting the software, our guide on how to choose an ERP completes this one.
Why does method matter more than the software?
An ERP is a company transformation project, not a simple software purchase. It touches every process, working habit and data set. That is why the quality of the rollout weighs more on success than the choice of vendor itself: a great piece of software poorly deployed produces a failure, a decent one well deployed produces a success.
Concretely, the software is only 10 to 25% of the total budget of an ERP project. The rest, the bulk of it, goes to integration (configuration), data migration, training and maintenance. This split, commonly observed in projects, should steer your attention and your budget toward the support, not only toward the license.
In one sentence
An ERP’s success is 80% about the rollout and the teams adopting it, and 20% about the choice of software.
What are the 8 steps of the rollout?
Here is the project path, from the initial diagnosis to stabilization after launch. The order matters: each step prepares the next.
Scoping and diagnosis
You take stock of current processes and needs, build the project team, appoint a project manager and an executive sponsor, and set measurable goals. This is the foundation: a poorly scoped project drifts continuously afterward.
Writing the requirements
The reference document to approach vendors: processes to cover ranked by priority, functional requirements per module, technical constraints, volume of data to migrate, target timeline and budget. The more precise it is, the more comparable the quotes.
Choosing the solution and the integrator
You compare offers, sit through demos on your own use cases, and check sector references. The choice of integrator, who will support you for months, matters as much as the software itself.
Configuration and setup
The ERP is configured with the integrator based on the scoping decisions: structure, workflows, permissions, reports. Here you arbitrate between standard and custom development, the latter to be limited because it is costly and heavy to maintain.
Data migration
You transfer customers, suppliers, items, bills of materials, history and stock from the old systems. That first requires cleaning this data: duplicates, inconsistencies, formats. A time-consuming and underestimated phase, the number-one cause of delays.
Training and change management
Beyond training on the screens, you have to explain the why of the change, bring the teams on board, and appoint key users. This is what makes the difference between adoption and rejection.
Testing and go-live
You test the whole system on test data (acceptance testing), fix issues, then switch over to the new system. The go-live can be global (big bang) or gradual (by module or by site), depending on the acceptable level of risk.
Stabilization (hypercare) and follow-up
After launch, a stabilization period, often called hypercare, of one to three months, during which the integrator stays mobilized to fix anomalies and adjust the configuration. You then measure results against the scoping goals.
Data migration is prepared early
Do not wait until the end of the project to deal with data. A large share of delays comes from a poorly anticipated migration: dirty data, mixed formats, incomplete history. Start the cleanup as soon as scoping begins, in parallel with the rest.
Not chosen your ERP yet?
Our comparison ranks the best ERP software of 2026 on price, modules and the quality of implementation support.
How much time and budget should you plan for?
Duration depends above all on the size of the organization and the breadth of the scope. The commonly observed benchmarks:
| Profile | Indicative duration |
|---|---|
| SMB, targeted and well-scoped | 3 to 9 months |
| SMB or mid-market, broad scope | 6 to 12 months |
| Multi-site mid-market, high complexity | 12 to 18 months |
These ranges are orders of magnitude, not guarantees: a controlled scope and rigorous scoping clearly shorten the project. On budget, remember the golden rule: the software weighs 10 to 25%, and the rest splits between integration, data migration, training and recurring maintenance. The choice between cloud and on-premise ERP also shapes the cost structure, subscription versus license and infrastructure.
Good reflex
Prefer phasing over a risky big bang. Starting on a narrow scope (one module, one site), stabilizing, then extending, cuts the risk and lets teams build skills gradually. A gradual rollout is often the safest for an SMB.
Which pitfalls cause ERP projects to fail?
ERP projects that go off the rails share recurring causes. Knowing them is already defusing them:
- Sloppy scoping: without clear goals or a defined scope, the project keeps widening (scope creep) and the budget blows up.
- An underestimated data migration: the number-one cause of delays. Uncleaned data, poorly anticipated volume, incomplete history.
- Neglected change management: without team buy-in, the ERP is bypassed, misused, and the expected gains never come.
- Too much custom development: each bespoke tweak adds cost, delays the project and complicates future updates. Favor the standard, adapt your processes where you can.
- No executive sponsor: an ERP project needs a champion at the top to arbitrate and hold the course against resistance.
- A rushed go-live: switching over without enough testing or a planned stabilization period exposes you to serious operational blockages.
The good news is that these pitfalls are avoidable with method and solid support. That is also why the quality of the integrator, and not only of the software, should weigh in your ERP choice.
Ready to choose your ERP?
We compared the main ERPs on price, modules and the quality of support, to secure your rollout.
The next step
To go further, read our comparison of the best ERP software 2026, our guide on how to choose an ERP, or our comparison of cloud versus on-premise ERP that weighs heavily on the rollout.
Frequently asked questions
What are the steps of an ERP implementation?
An ERP implementation is structured in eight steps: scoping and diagnosis, writing the requirements, choosing the solution and the integrator, configuration, data migration, training and change management, testing and go-live, then stabilization (hypercare) and follow-up of results. The order matters, each step preparing the next.
How long does it take to implement an ERP?
Typical duration runs from 6 to 18 months depending on size and scope. A well-scoped SMB with a targeted scope can aim for 3 to 9 months, while a multi-site, highly complex mid-market company should plan for 12 to 18 months. Rigorous scoping and a controlled scope clearly shorten the project.
What share of the budget is the software?
The software is usually only 10 to 25% of the total budget of an ERP project. Most goes to integration (configuration), data migration, training and recurring maintenance. That is why you should focus your attention and budget on the support, not only on the license or subscription.
Why is data migration so critical?
Because it is time-consuming and often underestimated, which makes it the leading cause of delays in ERP projects. It means transferring customers, suppliers, items, bills of materials, history and stock, but above all cleaning that data first: removing duplicates, fixing inconsistencies, standardizing formats. It should be started as soon as scoping begins.
Is a big bang or a gradual go-live better?
It depends on the acceptable level of risk. The big bang switches everything at once, faster but riskier. A gradual rollout, by module or by site, is often safer for an SMB: it lets you stabilize a narrow scope before extending, and build team skills without exposing everything at the same time.