Trupeer Blog
Резюмировать
An SAP implementation is the project of deploying SAP software, such as SAP S/4HANA, SAP SuccessFactors or SAP Ariba, to run an organisation's business processes. It covers designing how processes will work in SAP, configuring and building the system, migrating data, testing, training users, going live and supporting the business afterwards.
Implementing Workday instead? See our Workday implementation guide.
SAP implementations have a reputation: big budgets, long timelines and a long list of projects that went wrong. Most of the failures have little to do with the software. They come from unclear scope, weak data, rushed testing and users who were never really prepared. This guide covers the SAP Activate methodology, realistic timelines and cost drivers, why SAP implementations fail and how to avoid it, and the process documentation, testing and adoption work that decides whether the project succeeds.
If you are moving from SAP ECC to S/4HANA, see our SAP S/4HANA migration guide for the support deadlines and greenfield vs brownfield choices.
The SAP Activate methodology: phases and deliverables
SAP Activate is SAP's implementation methodology. It combines SAP Best Practices (preconfigured processes), guided configuration tools and an agile-style delivery approach. It has six phases:

Phase | Goal | Key deliverables |
|---|---|---|
1. Discover | Understand what SAP can do and build the case | Business case, solution scope, trial or demo system |
2. Prepare | Set the project up to succeed | Project plan, team and governance, system landscape, change management and training strategy |
3. Explore | Decide how processes will work in SAP | Fit-to-standard workshops, design decisions, backlog of gaps, data migration approach |
4. Realize | Build and test the solution | Configuration, extensions, integrations, data loads, test cycles, end-user training materials |
5. Deploy | Get ready for go-live and cut over | Final testing, end-user training, cutover rehearsals, go-live decision |
6. Run | Stabilise and improve | Hypercare, handover to support, continuous improvement |
The most important idea in Activate is fit-to-standard: start from SAP's standard processes and change the business process where you can, rather than customising SAP to match how things are done today. Every customisation adds cost now and maintenance effort later.
The same phases apply to an SAP migration, such as a move from ECC to SAP S/4HANA. The difference is that you start from processes already running in SAP, so documenting how they work today matters even more.
Who is on an SAP implementation team?
Role | Responsibility |
|---|---|
Executive sponsor | Owns the business case and makes the hard scope decisions |
Programme or project manager | Runs the plan, budget, risks and governance |
Business process owners | Decide how each process will work and sign off design and testing |
Functional consultants | Configure SAP modules and lead design workshops |
Technical team | Builds extensions, integrations, data migration and the technical landscape |
Data owners | Clean, map and validate master and transactional data |
Change and training lead | Plans communication, training and adoption |
Super-users or key users | Represent their teams, test the system and support colleagues after go-live |
SAP implementation timeline and cost drivers
There is no standard timeline. A single-country implementation of SAP standard processes can go live within months, while a global programme rolled out in waves across many countries typically runs for years. What determines the timeline is mostly the same as what determines the cost:
Driver | Effect on time and cost |
|---|---|
Scope | Each module, process and business unit adds design, build and test effort |
Fit to standard | Every gap that needs customisation adds build, testing and long-term maintenance |
Data | Poor master data and large migrations slow testing and cutover |
Integrations | Interfaces to non-SAP systems are among the riskiest and most time-consuming items |
Countries and languages | Localisation, rollout waves and translated training add effort |
Testing | Underestimated test cycles are one of the most common causes of delay |
People change | Training and change management for thousands of users |
Hypercare | Every extra week keeps the project team engaged after go-live |
Total cost has three parts: software subscriptions or licences, implementation services from partners, and internal costs such as the time business experts spend on the project. Internal costs are the easiest to underestimate, because the people who know the processes best are also needed to run the business.
How Genpact transformed training for 140,000 employees across 40 countries
When Genpact rolled out Workday across HCM, finance and data, Davetta Harper, VP Organizational Change Leader, had to make sure 140,000 employees across 40 countries could learn and adopt the new system. That meant 500+ training collaterals across 20 workstreams, in five languages. Done manually, with 20-page SOPs built screenshot by screenshot and human translation, the project would have taken at least 12 months.
Her team recorded existing process design sessions and SME walkthroughs, uploaded them to Trupeer AI, and got back polished SOPs and demo videos automatically translated into all five languages. Templates kept formatting consistent, and AI avatars held up in every language with minimal edits.
Genpact delivered 500+ training collaterals in three months instead of twelve, 75% faster than the standard timeline, and end users consumed the content without realizing it was AI-generated.
“We needed to train 140,000 people across 40 countries on a completely new system. Trupeer gave us a way to actually get there.”
— Davetta Harper, VP Organizational Change Leader, Genpact
Why SAP implementations fail
Ask on any SAP forum why implementations fail and the same answers come back. Some well-known failures make the point. Hershey's ERP go-live in 1999, which included SAP, disrupted orders ahead of Halloween. Lidl abandoned its SAP project in 2018 after spending a reported €500 million. Revlon disclosed that problems after its 2018 SAP go-live at a North Carolina plant disrupted shipments. Behind these and many quieter failures are the same causes:
Why it fails | What it looks like | How to prevent it |
|---|---|---|
Customising instead of adopting standard | The project tries to rebuild old processes in SAP; costs and timelines grow | Commit to fit-to-standard and require a business case for every gap |
Unclear scope and weak decisions | Design keeps reopening; the backlog never shrinks | An empowered sponsor and process owners who make and hold decisions |
Poor understanding of current processes | Critical workarounds and exceptions are missed and break at go-live | Document as-is processes, including exceptions, before design |
Bad data | Testing stalls; go-live is delayed; reports are wrong | Start data clean-up early and assign data owners |
Rushed testing | Defects surface after go-live, in front of users and customers | Protect test cycles and test real process steps, not just scripts |
Users not ready | Ticket volumes explode; people fall back to spreadsheets | Role-based training on the real system, ready before go-live |
Weak hypercare | The project team leaves before the business is stable | Agreed exit criteria and documentation that answers repeat questions |
Key people pulled away | Business experts can't give the project enough time | Backfill key roles and plan for their time explicitly |
Notice how few of these are about SAP itself. Most are about decisions, data and people, which means most are preventable.
Process documentation and testing
Two activities connect directly to the failures above: documenting processes and testing them properly.
Document processes before and during the build
As-is processes: before design, record how each critical process runs today, including the exceptions and workarounds. They show what the new design must handle.
To-be processes: once SAP is configured, document each process as it will run in SAP, with owners, steps and controls. These become the basis for testing, training and audit.
Design decisions: record why each decision was made, so it doesn't reopen later and support teams understand the system after go-live.
Business process procedures: many projects write each to-be transaction up as a business process procedure (BPP), sometimes called an SAP BPD. This is the SAP documentation end users follow step by step, and it doubles as the source for training and test scripts.
Recording experts doing the work is the fastest way to capture both. With Trupeer, an expert records the process as they work, and Trupeer generates an SOP, a process map and a training video from the recording. For a detailed method, see documenting as-is processes for an SAP transformation.
Test in layers
Test type | What it proves |
|---|---|
Unit testing | Each configuration item and development works on its own |
Integration testing | End-to-end processes work across modules and systems |
Data migration testing | Migrated data is complete, correct and usable |
User acceptance testing (UAT) | Business users can run their real processes, including exceptions |
Regression testing | Changes and fixes haven't broken anything else |
Performance testing | The system handles peak volumes, such as month-end |
Cutover rehearsal | The go-live plan works, step by step, in the time available |
Build UAT scripts from documented to-be processes so testers cover real steps and exceptions. See our UAT documentation checklist for what to capture during testing.
User adoption: training, go-live and hypercare
A technically perfect SAP system still fails if people don't use it properly. Adoption needs four things:
Change impact by role. Know what changes for each role, and tell people early.
Role-based training on the real system. Short, task-based guides and videos for what each person will do on day one, built from the configured system rather than early prototypes.
Super-users in every team. People who know the system well enough to answer colleagues' questions.
A planned hypercare period. A support model, ticket triage and exit criteria agreed before go-live. See what hypercare is and how to plan it.
Training is often the item squeezed when timelines slip, because it can only be finished once the system is stable. Generating it from recordings of the configured system makes it possible to produce role-based training quickly at the end of the build. With Trupeer, each recording becomes a training video and step-by-step guide, translated into the languages each country needs, and updated by editing the script when configuration changes. See how this works for enterprise software rollouts.
Build the SAP training plan in the Prepare phase, alongside the change management strategy. That way SAP implementation training is scheduled from the start rather than squeezed into the last month. For multi-country programmes, plan SAP rollout training per wave, so each country learns its own localised processes.
How to choose an SAP implementation partner
Most organisations implement SAP with a partner. When comparing partners, look for:

Relevant experience: projects in your industry, size and SAP products, with references you can call.
The actual team: the consultants who will work on your project, not just the sales team.
Commitment to fit-to-standard: partners who challenge customisation rather than encourage it.
Data, testing and change capability: not only configuration skills.
Clear commercial model: fixed price, time and materials or a mix, with clear assumptions and change control.
Knowledge transfer: how your team will be able to run and improve the system after the partner leaves.
SAP's own partner finder lists certified partners by product, industry and country.
Where Trupeer Fits in an SAP Implementation
Trupeer supports the documentation and adoption work at three points in the project. In Prepare and Explore, experts record how processes run today, and Trupeer turns each recording into an as-is SOP and process map for fit-to-standard workshops. In Realize, process owners record the configured to-be process, and Trupeer generates SOPs, process maps and role-based training videos, translated for every country. At go-live and in hypercare, users search a knowledge base with Ask AI before raising tickets, and every new fix is recorded once and becomes a guide. Genpact used this approach to train 140,000 employees across 40 countries for its Workday rollout, delivering a 12-month programme in about three.
SAP implementation checklist
Prepare
Business case, scope and success measures agreed
Sponsor, process owners and core team named, with backfill for key people
Partner selected; governance and decision rights set
As-is processes documented for critical and expert-dependent processes
Data clean-up started, with data owners assigned
Explore and realize
Fit-to-standard workshops completed; every gap justified
To-be processes documented and owned
Integrations inventoried and designed
Test cycles planned and protected in the schedule
Role-based training built from the configured system
Deploy and run
UAT signed off against real process steps
Cutover rehearsed at least once
Every user trained; super-users ready in every team
Hypercare model and exit criteria agreed
Documentation owned and kept current after go-live
Related reading
Frequently Asked Questions
What is an SAP implementation?
An SAP implementation is the project of deploying SAP software, such as SAP S/4HANA, SAP SuccessFactors or SAP Ariba, to run an organisation's business processes. It covers process design, configuration, data migration, testing, training, go-live and post-go-live support.
What are the phases of an SAP implementation?
Most SAP implementations follow the six phases of SAP Activate: Discover, Prepare, Explore, Realize, Deploy and Run.
What is the SAP Activate methodology?
SAP Activate is SAP's implementation methodology. It combines SAP Best Practices, guided configuration and an agile-style delivery approach, and is built around fit-to-standard: adopting SAP's standard processes wherever possible instead of customising the system.
How long does an SAP implementation take?
It depends on scope, the number of countries and systems, data quality, integrations and how much processes change. A single-country implementation of standard processes can take months, while global programmes rolled out in waves often take years.
How much does an SAP implementation cost?
Cost depends on scope, customisation, data, integrations, countries, testing and change management. Total cost includes software subscriptions or licences, partner services and internal costs, such as the time business experts spend on the project, which is often underestimated.
Why do SAP implementations fail?
Most fail for reasons other than the software: customising instead of adopting standard processes, unclear scope and decisions, poor understanding of current processes, bad data, rushed testing, users who are not ready, and weak hypercare.
What is fit-to-standard in SAP?
Fit-to-standard is the approach of starting from SAP's standard, preconfigured processes and adapting the business process where possible, rather than customising SAP to match existing ways of working. Workshops in the Explore phase identify where standard fits and which gaps genuinely need a solution.
How do you choose an SAP implementation partner?
Look for relevant industry and product experience with references, meet the actual consultants who will work on your project, and check their commitment to fit-to-standard, their data, testing and change management capability, a clear commercial model and a plan for knowledge transfer.

