Trupeer Blog
요약
SAP S/4HANA migration is the move from SAP ECC (SAP Business Suite 7) to SAP S/4HANA, SAP's current ERP built on the SAP HANA database. Companies migrate in one of three main ways: converting their existing system (brownfield), reimplementing from scratch (greenfield), or a selective mix of the two (bluefield).
For most SAP customers, the question is no longer whether to migrate, but how and when. SAP's support deadlines are approaching, partners are busy, and every month of delay narrows the options. This guide covers the support timeline, the three migration approaches, the phases of a migration, realistic timelines and, most importantly, the people side: the process changes, training and hypercare that decide whether a migration succeeds once the system is live.
Why migrate to S/4HANA now: the ECC support timeline
SAP's maintenance commitments for SAP ERP 6.0 (ECC) and the other Business Suite 7 core applications set the clock:
Date | What happens |
|---|---|
End of 2027 | Mainstream maintenance for SAP ERP 6.0 (enhancement packages 6 to 8) ends |
2028 to end of 2030 | Optional extended maintenance, at a premium of two percentage points on the maintenance basis |
After 2030 | Customer-specific maintenance: the system keeps running, but with reduced coverage |
End of 2030 | SAP ends support for SAP Business Suite 7 on third-party databases and legacy Java; conversion tooling for those systems is only available before then |
Up to end of 2035 | The SAP ERP, private edition, transition option: a paid subscription for large, complex customers who move to SAP ERP, private edition on SAP HANA before the end of 2030 |
The transition option is not a blanket extension. SAP describes it as a time-bound subscription for its largest and most complex customers, with prerequisites including a move to SAP ERP, private edition on SAP HANA by 31 December 2030 and a minimum system size. SAP originally planned it for 2031 to 2033, and in October 2026 updated the end date to 31 December 2035. See SAP's announcement for the full conditions.
For most organisations, then, 2027 and 2030 remain the real planning dates. Beyond the deadlines, S/4HANA also brings a simplified data model, real-time reporting, the SAP Fiori user experience and SAP's newest AI capabilities, which are built for S/4HANA and SAP's cloud ERP rather than ECC.
Greenfield vs brownfield vs bluefield
Greenfield | Brownfield | Bluefield | |
|---|---|---|---|
What it is | New implementation of S/4HANA from scratch | Technical conversion of the existing ECC system | Selective data transition: a new or converted system with chosen data and processes carried over |
Processes | Redesigned, often around SAP standard | Largely kept as they are | Mix: some redesigned, some kept |
Historical data | Usually limited to open items and balances | All history kept | Selected history kept |
Custom code | Mostly retired | Kept and adapted | Selectively kept |
Speed and cost | Usually the longest and costliest | Usually the fastest technical route | In between, depending on scope |
People impact | Highest: new processes and screens for most users | Lower at first, mostly new screens and transactions | Varies by business unit |
Best for | Heavily customised systems, or a chance to redesign how the business works | Systems in good shape where processes still fit | Groups that want to redesign some units or regions but keep others |
Most decisions come down to how much you want to change the way the business works, versus how fast you need to move. Our guide to S/4HANA greenfield vs brownfield covers the training and documentation impact of each approach in detail.
Deployment is a separate choice. RISE with SAP packages S/4HANA as a private cloud subscription, while GROW with SAP offers the public cloud edition for companies that want SAP standard processes and faster adoption.
The phases of an S/4HANA migration
Most S/4HANA programmes follow SAP Activate, SAP's implementation methodology:
Phase | What happens | People and process work |
|---|---|---|
Discover | Business case, approach and scope | Identify which processes and teams will change most |
Prepare | Plan, team, governance and system readiness checks | Document as-is processes; set up change management and a training plan |
Explore | Fit-to-standard workshops and design decisions | Agree to-be processes; record design decisions and process owners |
Realize | Configure, build, migrate data and test | Record to-be processes; build SOPs and role-based training; run user acceptance testing |
Deploy | Final testing, end-user training and cutover | Train every role; run cutover rehearsals; prepare the hypercare model |
Run | Hypercare, then business as usual | Answer questions, fix issues, update documentation and exit hypercare on metrics |
The technical work dominates most project plans. The people and process work in the right-hand column is what decides adoption, and it is the part most often squeezed when timelines slip.
How long does an S/4HANA migration take?
There is no standard length. Duration depends on the approach, the number of systems and countries, data volume and quality, the amount of custom code and how much the business processes change. As a rough guide, a straightforward brownfield conversion is often measured in months, while a multi-country greenfield programme rolled out in waves typically runs for well over a year.
Three things shorten timelines more than anything else: clear scope decisions early, clean master data, and documentation and training produced in parallel with the build rather than squeezed in before go-live. Work backwards from your support deadline, and leave room for testing, training and hypercare.
The people side of S/4HANA migration
S/4HANA changes more than the system underneath. Users notice it in three places:
New screens and ways of working. SAP Fiori apps replace many classic transactions, and users need to learn new navigation even where the process is unchanged.
Process changes. Some S/4HANA changes affect how work is done. For example, Business Partner replaces separate customer and vendor master data, and finance teams work with a single source of truth for financial and management accounting data.
New roles and responsibilities. Greenfield redesigns often move steps between teams or into shared services.
That makes change management, training and hypercare central to the migration, not add-ons:
Change management: identify the impact on each role early and plan communication and support. See RISE with SAP change management.
Role-based training: give each role short, specific guidance for the tasks it will do on day one. Fiori-specific guidance helps here; see SAP Fiori end-user training materials.
Hypercare: plan the support model, ticket triage and exit criteria before go-live. See what hypercare is and how to plan it.
With Trupeer, process owners record the to-be process in the S/4HANA test system, and Trupeer generates role-based SOPs, training videos and process maps from each recording, translated for every country. When configuration changes late in the build, editing the script or re-recording one step updates the training.
This applies to every ECC to S/4HANA migration, whichever approach you choose. Build the S/4HANA training plan by role as soon as the to-be design is stable. S/4HANA user training then starts in the final test cycles, on the configured system rather than a demo. After go-live, short task videos keep S/4HANA user adoption up while people get used to Fiori.
Capture as-is processes before cutover
Whichever approach you choose, document how processes run in ECC today before the old system and the people who know it move on. As-is documentation feeds fit-to-standard workshops, shows which workarounds the new design must cover, and gives testers and trainers a baseline.
Capture the processes that are high-volume, high-risk or dependent on a few experts first, and include the exceptions and workarounds, not just the standard path. Recording experts as they work in ECC is the fastest way to do this: with Trupeer, each recording becomes an as-is SOP and process map. For a step-by-step method, see documenting as-is processes for an S/4HANA transformation.
What Drives the Cost of an S/4HANA Migration?
Costs vary widely, so it helps to know what moves the number. These are the main drivers to estimate early:
Cost driver | Why it matters | How to reduce it |
|---|---|---|
Approach | Greenfield redesign takes more design, build and change effort than a conversion | Choose the approach per business unit, not one size for all |
Custom code | Every custom program must be adapted, replaced or retired | Run a usage analysis and retire what nobody uses |
Data volume and quality | Migration effort grows with data volume and clean-up needs | Archive old data and clean master data before the build |
Number of countries and systems | Each adds localisation, testing and rollout effort | Template once, then roll out in waves |
Integrations | Interfaces to non-SAP systems must be rebuilt and tested | Inventory every interface early |
Testing | Regression and user acceptance testing take more time than most plans allow | Test against real process steps, including exceptions |
Training and change management | Thousands of users need to learn new screens and processes | Generate training from the configured system instead of building it by hand |
Hypercare | Every week of extended hypercare keeps the project team on the payroll | Have documentation ready on day one and exit on metrics |
Common S/4HANA Migration Mistakes
Treating it as a technical upgrade. Even a brownfield conversion changes screens and some processes for users. Plan change management from the start.
Starting too late. Partners and SAP experts are in short supply as 2027 and 2030 approach. Late starts mean fewer choices and higher rates.
Skipping as-is documentation. Without it, design workshops rely on memory, and critical workarounds disappear at cutover.
Leaving data clean-up until the end. Poor master data is one of the most common causes of delays in testing and go-live.
Building training too late. Training produced in the final weeks, from screens that are still changing, arrives rushed and generic.
No plan to exit hypercare. Without agreed exit criteria, hypercare runs on and the project team cannot move to the next wave.
Forgetting the rest of the landscape. CRM, SCM, SRM and systems on third-party databases have their own deadlines and constraints.
S/4HANA migration checklist
Before the programme
Support timeline confirmed for every system in the landscape, including third-party databases
Migration approach and deployment model chosen (greenfield, brownfield or bluefield; RISE or GROW)
As-is processes documented for critical, high-volume and expert-dependent processes
Custom code and data quality assessed
Change management and training approach agreed and funded
During the build
To-be processes agreed and owned
SOPs, process maps and role-based training built from the configured system
User acceptance testing run against real process steps, including exceptions
Super-users named and trained for every site or team
Hypercare model, ticket categories and exit criteria agreed
At go-live and after
Every user trained for the tasks they will do on day one
An S/4HANA go-live support plan agreed, with super users named in every team
Knowledge base live, so users can find answers before raising tickets
Daily hypercare stand-ups, with documentation updated for every repeat question
Hypercare exited on metrics, not a fixed date
Documentation owned and reviewed after each release
Where Trupeer fits in an S/4HANA migration
Trupeer supports the people and process work at three points: before the build, it captures as-is processes from experts working in ECC; during the build, it turns recordings of the to-be process into SOPs, process maps and training for every role and language; and at go-live, it gives users a searchable knowledge base that cuts "how do I" tickets during hypercare. Genpact used Trupeer to train 140,000 employees across 40 countries for its Workday rollout, delivering a 12-month programme in about three, and the same approach applies to SAP. See how Trupeer supports enterprise software rollouts, or compare options in AI tools for SAP S/4HANA transformation.
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
Related reading
Frequently Asked Questions
What is an S/4HANA migration?
An S/4HANA migration is the move from SAP ECC (SAP Business Suite 7) to SAP S/4HANA. It can be done as a brownfield system conversion, a greenfield reimplementation, or a bluefield selective data transition that combines the two.
When does SAP ECC support end?
Mainstream maintenance for SAP ERP 6.0 ends at the end of 2027. Optional extended maintenance runs to the end of 2030 at a premium, after which customer-specific maintenance applies. Large, complex customers that move to SAP ERP, private edition on SAP HANA before the end of 2030 can subscribe to a transition option, which SAP updated in October 2026 to run until the end of 2035.
What is the difference between greenfield and brownfield S/4HANA migration?
Greenfield is a new implementation that redesigns processes and usually brings over only open items and balances. Brownfield converts the existing ECC system, keeping processes, history and custom code. Greenfield changes more for users; brownfield is usually faster.
What is a bluefield S/4HANA migration?
Bluefield, also called selective data transition, combines greenfield and brownfield. Organisations carry over chosen data, processes or business units while redesigning others, which suits groups that want different approaches for different parts of the business.
How long does an S/4HANA migration take?
It depends on the approach, number of systems and countries, data quality, custom code and process change. Simple brownfield conversions are often measured in months, while multi-country greenfield programmes rolled out in waves typically take well over a year.
What is SAP Activate?
SAP Activate is SAP's implementation methodology for S/4HANA. It runs through six phases: Discover, Prepare, Explore, Realize, Deploy and Run.
What is the difference between RISE with SAP and GROW with SAP?
RISE with SAP packages S/4HANA as a private cloud subscription for companies that need flexibility to keep and extend their processes. GROW with SAP offers the public cloud edition, built around SAP standard processes, for companies that want faster adoption.
How do you prepare users for S/4HANA?
Identify how each role's work will change, document the to-be processes, and give every role short, specific training for the tasks it will do on day one. Make answers easy to find in a knowledge base and plan a hypercare model with clear exit criteria.

