Your SAP ECC system will not switch off on 1 January 2028. Nothing dramatic happens at midnight. But the ECC to S/4HANA migration you keep pushing to “next quarter” has a hard edge, and as of 23 October 2026 you are about 434 days away from it.
That is roughly 14 months. Most projects take 12 to 24 months. Do the maths, and you can see why CIOs, finance heads and SAP consultants are asking the same question right now: where do we actually start?
This guide gives you a straight answer. You will see the real support dates, a seven-step roadmap, the challenges that sink projects and the habits that keep them on track. We also cover the skills gap, because tools do not migrate systems. People do.
Quick answer: where SAP ECC support stands today
If you only have a minute, read this.
- Mainstream maintenance for SAP ECC 6.0 (EHP 6 to 8) ends on 31 December 2027.
- Optional extended maintenance runs from 2028 to 2030, at a premium of two percentage points on your maintenance fee.
- A transition option reaches 2033, but only for selected customers who move to SAP’s private cloud route.
- SAP has committed to keep at least one S/4HANA release in maintenance until 2040.
- Every path ends in S/4HANA. The only open question is how much time you buy first.
What changes after 2027? The dates every team should know
SAP confirmed its position years ago. In its official announcement, SAP promised mainstream maintenance for Business Suite 7 until the end of 2027, followed by optional extended maintenance until the end of 2030. You can also read the same timeline on SAP’s own maintenance strategy page.
One detail trips people up. ECC 6.0 with enhancement packages 0 to 5 already lost mainstream maintenance at the end of 2025, according to IBsolution’s 2026 overview. So check your enhancement package before you quote any date in a board meeting.
| Option | Timeline | What you get | The catch |
|---|---|---|---|
| Mainstream maintenance | Until 31 Dec 2027 | Full support, patches and legal updates | Ends for EHP 6 to 8 |
| Extended maintenance | 2028 to 2030 | Patches and legal updates continue | Two extra percentage points; EHP 6 to 8 only |
| Customer-specific maintenance | After 2027 if you skip the extension | Reduced support | Limited scope |
| Transition option | 2031 to 2033 | ECC support inside SAP’s private cloud model | Needs a RISE route and eligibility |
| S/4HANA | Maintained to 2040 | Current innovation and support | You must migrate |
Please read the 2033 line carefully. It is not a free extension. Gambit’s explainer notes that SAP calls it an offering, not an extension of maintenance, and that further details arrive shortly before it goes on sale in 2028. Planning your whole budget around it is a gamble.
How many companies have moved?
Fewer than you might expect. Gartner found that about 39 percent of roughly 35,000 ECC customers had bought or subscribed to S/4HANA licences by the end of 2024, as The Register reported. Meanwhile, DSAG’s 2026 investment report says only 37 percent of ECC users expect to be live on S/4HANA by the end of 2027, according to Arkyn’s summary. About half plan to finish by 2030.
So if you feel behind, you are in large company. However, large company is not the same as safe.
Why ECC to S/4HANA migration can’t wait for 2027
Waiting feels cheap. It is not. Here are four reasons the wait-and-see plan costs more than it saves.
- Time runs out first. A 12 to 24 month project that starts in 2027 finishes in 2028 or 2029. That means you pay for extended maintenance whether you planned to or not.
- Everyone queues at once. Nearly half of existing SAP customers plan to finish by 2030, per the DSAG figures cited by IBsolution. IBsolution also expects the S/4HANA consultant market to tighten from 2027. Good partners and good people will get expensive.
- Extended maintenance is a bridge. You pay more to keep the same system. Meanwhile, the business gets none of the new capabilities.
- Compliance keeps moving. Tax and statutory rules change often, and GST updates in India are a good example. After support ends, your team may face manual workarounds.
None of this means panic. It means choosing your date on purpose, instead of letting the calendar choose it for you.
Brownfield, greenfield or bluefield: pick your route
Before any roadmap, you need to decide how you will move. There are three common routes.
Brownfield (system conversion). You convert your existing ECC system in place. Your history, configuration and custom code come along. It is usually the fastest route, and it disrupts users the least. The risk is obvious: you also carry your old mess into the new system.
Greenfield (new implementation). You build a fresh S/4HANA system and move only the data you need. It gives you a chance to redesign processes and keep the core clean. It also takes the most time and money.
Bluefield (selective data transition). This is the middle path. You keep parts of your configuration, choose which data moves, and redesign where it pays off. It often needs specialist tooling and an experienced partner.
A quick rule of thumb: choose brownfield when your processes work and speed matters. Choose greenfield when your ECC system is heavily customised and the business wants real change. Choose bluefield when you need both.
One more point. RISE with SAP is a commercial and hosting package, not a migration method. You can run any of the three routes above with or without it.
The ECC to S/4HANA migration roadmap: 7 steps
Think of this as the spine of your project. Details change from company to company, but the order rarely does.
Step 1: Build the business case and pick your deadline
Decide which deadline you are really working to: 2027, 2030 or the narrow 2033 option. Then put numbers on it. Include licences, hosting, partner fees, internal effort and the cost of extended maintenance. Get the CFO involved early, because this project touches every budget line.
Step 2: Run the readiness checks
Start with the SAP Readiness Check for S/4HANA. It flags relevant simplification items, add-on issues, custom code impact and data volumes. SAP’s simplification item catalog guide explains how the catalog, the check and the Readiness Check fit together. Run these early. Surprises are cheap on day one and painful in month ten.
Step 3: Clean up before you convert
Retire custom code nobody uses. Archive old data. Fix duplicate customers and vendors. Usage statistics collected over several months show which Z programs your users actually run. In many landscapes, a large share of custom code turns out to be dead weight. Removing it shrinks the project before it starts.
Step 4: Choose your approach and target design
Now pick brownfield, greenfield or bluefield. Also decide what “clean core” means for you. In short, keep the core as standard as possible. Build extensions on SAP BTP or through released interfaces, so future upgrades stay painless.
Step 5: Convert in a sandbox first
For a system conversion, the Software Update Manager (SUM) does the heavy lifting. Its Database Migration Option combines database migration, software update and data conversion into one procedure, as the SAP Learning course on system conversion describes. Always rehearse on a copy of production. Your Basis team will thank you.
Step 6: Test, train and rehearse the cutover
Run integration tests with real business users, not only consultants. Schedule at least two or three mock cutovers, and time each one. Train users on the new Fiori screens before go-live, not after. This step decides whether people trust the new system on Monday morning.
Step 7: Go live and stabilise
Plan a hypercare period with fast answers and daily issue reviews. Track adoption, not just tickets. Then start harvesting the benefits you promised in step one.
Challenges that derail ECC to S/4HANA migration projects
Almost every failed or late project hits the same walls. Knowing them in advance is half the defence.
Custom code that nobody understands
Years of Z programs, user exits and modifications rarely come with documentation. SAP’s custom code migration worklist shows what needs adapting, but your team still has to decide what to fix, rewrite or delete.
Business Partner and master data
In S/4HANA, the Business Partner becomes the central master data object. Customer-vendor integration (CVI) links it to your existing customers and vendors, and it must be in place before conversion, as IBsolution explains. Dirty master data makes this step slow.
The finance conversion
Finance changes the most. Several sub-ledger tables merge into the Universal Journal (ACDOCA), which gives you one line-item source for reporting. That is a big win, but your finance team must understand the new data model and test every close process.
Data volume and quality
Large databases mean longer downtime and higher HANA memory needs. Archive early. Also decide how much history the business really needs in the new system.
Weak business involvement
When IT runs the project alone, testing becomes a checkbox. Users then find the problems after go-live. Name a business owner for each process area from day one.
Skills and change fatigue
Your ECC experts know the old world well. S/4HANA brings new tools, new data models and new user interfaces. Without planned learning, you get slow projects and frustrated teams.
Best practices from projects that finish on time
These habits show up again and again in programmes that land well.
- Start with data, not slides. Run the readiness checks in the first month. Let facts shape the plan.
- Protect the clean core. Every new modification today becomes a migration problem tomorrow.
- Fund the business side. Release key users from daily work so they can design, test and decide.
- Test early and often. Automate regression tests where you can. Repeat them after every change.
- Rehearse cutover like a drill. Time every step, and fix the slow ones.
- Communicate in plain words. Tell users what changes for them, when and why.
- Budget for contingency. Add a buffer for surprises, because there will be some.
- Train before you need it. Teach people while your team builds the system.
- Choose partners on experience, not on slides. Ask for references from companies with a landscape like yours.
The skills gap nobody puts in the project plan
Every migration plan lists licences, hosting and partner fees. Very few list learning. Yet the people who run your ECC system today need new skills tomorrow.
Here is how that looks by role:
- Finance teams need to understand the Universal Journal, new asset accounting and the revised close. Our SAP FICO training covers S/4HANA finance end to end.
- Procurement and inventory teams meet new material document handling and Fiori apps. See the SAP MM course.
- Sales teams work with changed order-to-cash processes. The SAP SD course is the place to start.
- Developers must move from classic ABAP to modern models. Start with our SAP ABAP training, then read RAP vs CAPM vs ABAP to choose your path.
- Basis administrators run SUM, HANA and the cutover. Our SAP Basis training builds those skills.
- Integration teams connect S/4HANA to everything else. The SAP CPI course covers that ground.
Experienced ECC users do not always need a full course. That is why SKILS also lists S/4HANA delta programmes for Finance, Sales, Procurement and Technical teams in its course options. Delta training focuses only on what changed, so people learn faster and return to work sooner.
Running a project at scale? Our corporate SAP training is customised to your landscape, your modules and your go-live calendar. Many companies across Pune’s manufacturing belt, from Chakan to Pimpri-Chinchwad, face this same challenge.
What this means for your career
The migration wave is also a job market. If you want to start a career in SAP, S/4HANA skills are the ones employers are asking for. Read why companies are racing to hire S/4HANA talent, check how long it takes to learn SAP, and see whether SAP certification matters after training. Looking for an SAP training institute in Pune? Start with our full course list and our career page.
A quick checklist to share with your team
Copy this into your next steering meeting.
- We know our ECC enhancement package and our exact support end date.
- We have chosen our target deadline: 2027, 2030 or 2033.
- Someone has run the SAP Readiness Check.
- We have a list of custom code to keep, rewrite or retire.
- Our customer and vendor master data is clean and ready for the Business Partner.
- The finance team has seen the Universal Journal in a sandbox.
- Every process area has a named business owner.
- We have planned at least two mock cutovers.
- Training is in the budget and on the calendar.
- We have asked partners for references, not just proposals.
Frequently asked questions
When does SAP ECC support end?
Mainstream maintenance for SAP ECC 6.0 with EHP 6 to 8 ends on 31 December 2027. Optional extended maintenance then runs until 31 December 2030 for an added two percentage points on your maintenance fee.
Is ECC to S/4HANA migration mandatory?
No law forces you to move, and your system will keep running after 2027. However, without extended maintenance you lose standard support, including patches and legal updates. Over time, that risk grows.
How long does ECC to S/4HANA migration take?
Most projects run 12 to 24 months, depending on size, custom code and the approach you choose. Large, heavily customised landscapes can take longer.
Which approach is best: brownfield or greenfield?
It depends on your goals. Brownfield is faster and keeps history. Greenfield lets you redesign processes. Bluefield sits in between. Your readiness check results should guide the decision.
Which SAP skills are in demand for migration projects?
Finance (FICO), supply chain modules such as MM, SD and PP, ABAP with modern development models, Basis and integration all see demand. Delta knowledge of S/4HANA changes is especially useful for existing ECC consultants.
Final thoughts: start the conversation this week
The ECC to S/4HANA migration deadline is not a surprise. It is a date on the calendar, and every month you wait makes your options narrower and more expensive. Run the readiness check. Pick your path. Fund the learning.
If your team needs S/4HANA skills, or if you want to build a career around this wave, we are happy to help. Contact SKILS to talk about a custom corporate programme, or check the training calendar for upcoming batches.
