The SAP Activate methodology gives every S/4HANA project the same proven structure. SAP Activate is SAP’s standard method for implementing S/4HANA. Knowing its six phases helps you understand what your partner is doing, what’s expected of your team and where projects usually go wrong.
- Six phases: Discover, Prepare, Explore, Realize, Deploy, Run.
- It starts from SAP’s best practices, not a blank page.
- Build happens in short, agile sprints.
- Your team’s time matters most in Explore and Realize.
SAP Activate methodology at a glance
Each phase in detail
Discover
Understand the value S/4HANA can bring, explore the solution and agree the business case and scope.
Prepare
Set up the project: plan, governance, team, systems and the starting point of SAP’s best-practice configuration.
Explore
Run fit-to-standard workshops: show how SAP’s standard processes work and agree where they fit and where gaps need a solution.
Realize
Configure, build extensions, migrate data and test in short iterations, with business users reviewing as you go.
Deploy
Final testing, user training, cut-over and go-live, followed by hypercare support.
Run
Operate, support and continuously improve the system, adopting new SAP releases over time.
A good methodology doesn’t slow a project down. It stops it from going in circles.
What your team does in each phase
| Phase | Your team’s main role |
|---|---|
| Discover / Prepare | Agree goals, scope and the project team |
| Explore | Join workshops, make process decisions quickly |
| Realize | Review builds, prepare data, test |
| Deploy | Train users, sign off, support cut-over |
| Run | Own the system, raise improvements |
Common mistakes to avoid with SAP Activate
Skipping Discover and Prepare
Rushing into build without agreed scope and governance causes rework later.
Weak decision-making in Explore
Fit-to-standard workshops need people who can make decisions. Delays here ripple through the plan.
Testing too late
SAP Activate builds in iterations so users can review early. Use those reviews.
Treating Run as an afterthought
Plan support, ownership and continuous improvement before go-live.
A worked example: a six-month project
This scenario is a composite of common situations, not a specific client.
A mid-size company plans a six-month S/4HANA Cloud project using the SAP Activate methodology. Discover and Prepare take a few weeks to agree scope, team and plan.
Explore runs fit-to-standard workshops by process, producing a short list of gaps. Realize builds and tests in sprints, with key users reviewing each one.
Deploy covers final testing, training and cut-over. In Run, the team owns the system with partner support, adopting new releases over time. The SAP Activate methodology keeps everyone clear on what comes next.
Checklist before you start an SAP Activate project
Use these questions with your team before you begin. Clear answers here make every later decision faster.
- A named business sponsor with authority to decide
- Process owners free to join Explore workshops
- Agreed scope, budget and timeline
- A data clean-up plan that starts in Prepare
- A support model for Run, agreed before go-live
Frequently asked questions
Is SAP Activate only for S/4HANA?
It’s SAP’s method for S/4HANA and many other SAP cloud solutions.
Is SAP Activate agile or waterfall?
It combines both: phases with clear gates, and agile sprints for building and testing in Realize.
Which phase takes longest?
Usually Realize, where configuration, extensions, data migration and testing happen.
Can the SAP Activate methodology be used for small projects?
Yes. The phases scale to the size of the project.
Who manages the plan?
Usually a joint project manager from the business and the implementation partner.
Planning an S/4HANA project?
We’ll walk you through each Activate phase and what it means for your team and timeline.