ERP Implementation Stages Every Company Should Know

Once the project mandate and budget are approved, teams often still lack a clear process map: where to start, what the phases are, and when the system will be ready to use. This situation is common in companies implementing ERP for the first time, including those migrating to the cloud. This article summarises the six project stages, the standard methodology used, and duration estimates based on the latest industry data.

In short, ERP implementation is the process of rolling out an Enterprise Resource Planning system across company operations, from planning, requirements analysis, configuration, and data migration through to testing, go-live, and post-implementation support. A project usually consists of six stages following the SAP Activate methodology, and success depends more on the readiness of processes and people than on the software.

Six ERP Implementation Stages from Planning to Post Go-Live

The six ERP implementation stages are: planning and requirements discovery, project preparation, fit-to-standard analysis, configuration and testing (build), go-live together with cutover, and post go-live support. Each stage produces a measurable output, allowing management to track progress incrementally and avoid risk piling up at the end.

The table below maps these six stages to the official phases of the SAP Activate methodology, based on SAP Learning documentation (accessed July 2026).

The third stage is the main differentiator in cloud-era projects. In a fit-to-standard workshop, business processes are aligned to the best practices available in the system rather than customising the system to fit legacy processes. Requirements not yet met are recorded as gaps in the backlog. A basic understanding of SAP systems allows the business team to take an active part in the workshop instead of simply following the consultant's lead.

Three important terms are worth understanding from the outset: UAT (user acceptance testing) is the final round of testing by business users, cutover is the controlled switch from the old system to the new one, and hypercare is the period of intensive support after go-live. In practice, delays most often occur during data cleansing and migration rather than configuration.

What Is the SAP Activate Methodology and Why Is It the Reference for ERP Projects?

SAP Activate is SAP's official implementation methodology for SAP S/4HANA and its cloud solutions, and the successor to the ASAP and SAP Launch methodologies. Its six phases, namely Discover, Prepare, Explore, Realize, Deploy, and Run, provide a consistent framework for companies, implementation partners, and SAP, with clear deliverables at every phase.

The methodology rests on 3 pillars: SAP Best Practices content in the form of ready-to-use business processes, guided implementation and configuration tools, and a modular, agile project methodology framework. The Realize phase is run iteratively as well; functionality is built incrementally from the backlog rather than through a rigid waterfall model that stacks all the testing at the end.

Deliverables per phase also allow management to hold the implementation partner to measurable progress. Methodology is no guarantee, though; execution discipline, data quality, and change management remain the deciding factors.

How Long Does ERP Implementation Take and Why Do So Many Overrun?

The median project timeline is 9 months according to The 2026 ERP Report from Panorama Consulting, a survey of 170 responding organisations. Actual duration depends on module scope, the number of entities, and data quality; nearly a quarter of projects still run past schedule, and the most frequent cause is organisational rather than technical.

The same report notes that more than a quarter of organisations exceed budget, while an intense focus on organisational change management was reported by fewer than a quarter of respondents. Those two figures explain each other: projects overrun in the area that receives the least investment.

A Gartner projection adds further context. Through 2027, more than 70% of newly implemented ERP initiatives are projected to fall short of fully meeting their original business case (business value justification). This does not mean the projects fail outright; the system generally still runs, but the value promised to the board is not fully realised.

For that reason, change management and data ownership need to enter the plan from the very first stage rather than being patched in after go-live. Choosing an experienced implementation partner with a proven methodology is the single biggest risk lever you can control from the start.

FAQ (Frequently Asked Questions)

What are the stages of ERP implementation?

Six stages: planning and requirements discovery, project preparation, fit-to-standard analysis, configuration and testing (build), go-live together with cutover, then post go-live support. This sequence aligns with the six phases of SAP's official SAP Activate methodology (Discover, Prepare, Explore, Realize, Deploy, Run), the reference point for modern SAP projects.

How long does ERP implementation take?

It depends on module scope, the number of entities, and data quality. As a benchmark, The 2026 ERP Report from Panorama Consulting recorded a median project timeline of 9 months across 170 responding organisations. Nearly a quarter of projects still run past schedule, generally due to organisational rather than technical issues.

Why do ERP implementations fail?

Gartner projects that more than 70% of newly implemented ERP initiatives will not fully meet their original business case through 2027. The dominant causes are rooted in people and process: Panorama Consulting (2026) records organisational issues such as governance, resistance to change, and process redesign as the most frequent reasons projects overrun.

Conclusion

A map of the six stages, a named methodology, and honest risk figures are the three minimum essentials before a project contract is signed. As an SAP Platinum Partner through its United VARs membership, with experience dating back to 1998, Soltius guides companies through ERP implementation using the SAP Activate methodology, from planning to post go-live support. If the project mandate is already in your hands, start with a readiness assessment rather than software selection.

To discuss applying SAP Activate to your company's ERP implementation plan, visit soltius.co.id.