ERP Migration & SelectionFree referencePDF, Excel, Word export

ERP Implementation Methodology Phases Reference (SAP Activate, AIM, Sure Step and More)

Every large ERP vendor publishes an implementation methodology, and each names its phases differently. This table lines them up so a project manager can map a vendor plan to an internal PMO template, or explain to a steering committee what Realize or Transition means.

Download:

Methodology	Vendor	Phase #	Phase name	Typical focus
SAP Activate	SAP	1	Discover	Understand the solution, build the business case and decide on scope and approach.
SAP Activate	SAP	2	Prepare	Project kickoff, team, governance, plan and system landscape setup.
SAP Activate	SAP	3	Explore	Fit-to-standard workshops, gap list and backlog definition.
SAP Activate	SAP	4	Realize	Configuration, extensions, integration build and iterative testing.
SAP Activate	SAP	5	Deploy	Cutover, final data load, production readiness and go-live.
SAP Activate	SAP	6	Run	Operate, support and continuous improvement after go-live.
ASAP	SAP	1	Project Preparation	Scope, organization, standards and project plan.
ASAP	SAP	2	Business Blueprint	Document business processes and requirements to be implemented.
ASAP	SAP	3	Realization	Configure the system against the blueprint and test.
ASAP	SAP	4	Final Preparation	End user training, final testing, cutover rehearsal.
ASAP	SAP	5	Go-Live and Support	Production start and early life support.
Oracle AIM	Oracle	1	Definition	Project scope, objectives, approach and plan.
Oracle AIM	Oracle	2	Operations Analysis	Gather and analyze business requirements and map to the application.
Oracle AIM	Oracle	3	Solution Design	Design the solution, gaps and extensions.
Oracle AIM	Oracle	4	Build	Set up, customize and test components.
Oracle AIM	Oracle	5	Transition	Data conversion, training and production cutover preparation.
Oracle AIM	Oracle	6	Production	Live operation and stabilization.
Oracle Unified Method (OUM)	Oracle	1	Inception	Agree vision, scope and feasibility.
Oracle Unified Method (OUM)	Oracle	2	Elaboration	Reduce key risks and baseline the architecture.
Oracle Unified Method (OUM)	Oracle	3	Construction	Build and test the solution in iterations.
Oracle Unified Method (OUM)	Oracle	4	Transition	Deploy to production and hand over to support.
Oracle Unified Method (OUM)	Oracle	5	Production	Operate and maintain the live solution.
Sure Step	Microsoft	1	Diagnostic	Assess fit, readiness and the business case.
Sure Step	Microsoft	2	Analysis	Requirements and fit-gap analysis.
Sure Step	Microsoft	3	Design	Solution design and technical architecture.
Sure Step	Microsoft	4	Development	Configure, develop and test.
Sure Step	Microsoft	5	Deployment	Data migration, training and go-live.
Sure Step	Microsoft	6	Operations	Support and ongoing improvement.
Success by Design	Microsoft	1	Initiate	Vision, scope, team and governance.
Success by Design	Microsoft	2	Implement	Build the solution in iterative sprints with reviews.
Success by Design	Microsoft	3	Prepare	Testing, training, cutover rehearsal and go-live readiness.
Success by Design	Microsoft	4	Operate	Hypercare, support and continuous updates.

Phase names are the commonly published ones. Vendors revise their methodologies, so confirm against the current official documentation for your product and release.

Lifecycle review for your ERP program

Optional: send us your project plan and we will mark missing gates around data migration and cutover.

Optional. The tool and every export work without this. No spam.

How to use the table

Type a methodology name, a vendor or a phase word such as cutover into the search box to filter. Sort by phase number to read a methodology top to bottom. Export to Excel and add your own column for the deliverable or gate you require at each phase. Use it when a vendor proposal uses one vocabulary and your internal governance uses another, so you can map phases rather than argue about names.

What the methodologies have in common

Despite different names, almost all of them follow the same arc: define scope, understand requirements, design, build and test, transition to production, then support. The real differences are in how much is done iteratively and where the customer signs off.

Older waterfall style: ASAP, Oracle AIM, Sure Step
Iterative and agile leaning: SAP Activate, Oracle OUM, Success by Design
Fit-to-standard workshops replace blueprint documents in newer methods
Cutover and data conversion always sit in the late build or transition phase

Mapping to your own plan

Pick one internal lifecycle and map every vendor phase to it. For example, Explore, Business Blueprint, Operations Analysis, Solution Design and Analysis all map to a design stage with a requirements sign-off gate. Realize, Realization, Build, Construction and Development map to a build and test stage. Deploy, Final Preparation, Transition and Prepare map to cutover readiness. Keeping a single internal vocabulary makes status reports comparable across projects.

Common mistakes

The most frequent error is treating the methodology as the plan. A methodology is a framework; the plan still needs dates, owners and dependencies. Teams also skip the early phases on rollouts because the business case feels settled, then discover scope disagreements in testing. Finally, do not assume phase gates are identical across vendors: a sign-off in one methodology may be optional in another.

Frequently Asked Questions

Is SAP Activate replacing ASAP?

SAP Activate is the current methodology SAP promotes for S/4HANA and cloud products, and ASAP is the older approach used in classic ECC projects. Many existing programs still use ASAP vocabulary, so both are listed.

Do I have to follow the vendor methodology?

No. Most customers and integrators adapt it. What matters is that you cover the same concerns: scope, requirements, design, build, test, data migration, training, cutover and support, with clear sign-offs at each stage.

Where does data migration sit in these phases?

Data work should start in the design stage, not the last one. Mapping and cleansing begin early, trial loads happen during build, and the final load is part of cutover in the deploy or transition phase.

Which methodology suits a mid-size manufacturer?

It depends mostly on the ERP you choose. Within the vendor ecosystem use the vendor method, but keep the gates light: fit-to-standard workshops, two or three test cycles, one mock cutover and a defined hypercare period.

If you want a lifecycle plan that reflects your actual ERP and plant structure, Netray can review it and flag missing gates for data migration and cutover.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Back to All Tools