SAP ECC mainstream maintenance ends on 31 December 2027. What the deadline means for Australian companies, how the financial year, Payday Super, Peppol and data residency affect your plan, and when you need to start.
Short answer: SAP ECC 6.0 mainstream maintenance ends on 31 December 2027. If your company still runs ECC, you have about 14 months, and a typical S/4HANA migration takes 6 to 18 months. Most Australian companies need to start by the first half of 2027 at the latest.
By SAVIC SAP Practice · Nov 3, 2026 · 8 min read
The SAP ECC dates that matter
The deadline is global, so Australian companies face the same dates as everyone else:
| Date | What happens |
|---|---|
| 31 Dec 2025 | Mainstream maintenance ended for ECC 6.0 enhancement packages 0 to 5. |
| 31 Dec 2027 | Mainstream maintenance ends for ECC 6.0 enhancement packages 6 to 8. |
| 31 Dec 2030 | Optional extended maintenance ends. It costs extra on top of your current maintenance fee. |
| 2031 to 2033 | SAP's announced transition option for customers who move to SAP ERP Private Edition through RISE with SAP. |
Extended maintenance and the transition option buy time. They don't remove the need to move to SAP S/4HANA, and both add cost every year you stay. Check your own contract and enhancement-package level with SAP.
Why the plan looks different in Australia
The deadline is global. These Australian factors change when and how you can migrate.
1. The financial year ends on 30 June
Most Australian companies close their books on 30 June. Few finance teams will accept a go-live in June or July, when they are running end-of-financial-year close, tax reporting and audit preparation. That leaves fewer safe cutover windows before December 2027 than the calendar suggests.
2. The Christmas shutdown is a cutover window
Many Australian manufacturers and distributors slow down or shut over Christmas and January. That period is often the best time for a cutover weekend. The Christmas 2026 window is almost certainly too soon for anyone starting now, which leaves mid-2027 or Christmas 2027. The second is right on the deadline.
3. Payroll rules keep changing
Payday Super has applied since 1 July 2026: employers must pay super with each pay cycle, and it must reach the fund within seven business days (confirm the rules for your company with your payroll or tax adviser). Single Touch Payroll Phase 2 is already in place. If ECC runs your payroll, every new rule is another change to maintain on a system nearing the end of mainstream support. Decide early whether payroll moves to SAP SuccessFactors Employee Central Payroll as part of the migration.
4. Peppol e-invoicing
Australian Government agencies receive invoices through the Peppol network, and PINT A-NZ is the format used. B2B e-invoicing is voluntary, but more customers are asking for it. Building Peppol into S/4HANA, rather than into ECC, means you do the work once.
5. Data residency
RISE with SAP and SAP BTP can run in Australian cloud regions. If your board, customers or regulators expect data to stay in Australia, confirm the region early. It affects which hosting and edition options are open to you.
6. SAP skills are in demand
Every SAP customer is working to the same deadline, so experienced S/4HANA consultants get booked out. The later you start, the harder it is to secure a senior team at a sensible rate. Read why talent supply is the real constraint.
Your options
| Option | What it means | Often suits |
|---|---|---|
| Brownfield (system conversion) | Convert your ECC system to S/4HANA, keeping history and configuration. | Stable processes, tight timeline |
| Greenfield (new implementation) | Start again on S/4HANA with standard processes and move only the data you need. | Heavy custom code, processes due for a rethink |
| Selective data transition | Combine both: redesign some areas, carry others across. | Groups with mixed needs across entities |
You also choose a deployment model:
- SAP GROW (S/4HANA Cloud Public Edition): standard processes and a faster go-live. It suits many mid-market manufacturers, distributors and professional-services firms. About SAP GROW.
- RISE with SAP (Cloud ERP Private Edition): more room for your own extensions, and the usual route for brownfield conversions. About RISE with SAP.
Compare the two in detail: RISE vs GROW in 2026.
A realistic timeline from today
- Nov 2026 to Feb 2027: assess. Readiness check, custom-code analysis, choice of option and edition, business case and partner selection.
- Mar 2027 to Sep 2027: build. Design, configuration, data migration rehearsals and testing. Keep it clear of your 30 June close.
- Oct 2027 to Dec 2027: go live. Cutover before the deadline, ideally not in the last fortnight of December.
This works for a focused mid-market scope. Larger groups, or projects with payroll in scope, should start the assessment now and consider extended maintenance as a safety net, not as the plan.
Checklist for Australian ECC customers
- Confirm your ECC enhancement-package level and maintenance contract dates with SAP.
- Mark your blackout periods: end of financial year, peak trading and audit.
- Decide whether payroll (STP Phase 2, Payday Super) moves with the ERP or separately.
- List Peppol and e-invoicing needs from your government and large customers.
- Agree your data residency requirement before choosing hosting.
- Run a custom-code analysis to size the effort. How SAP's custom code tools help.
- Shortlist partners with S/4HANA migration experience. Top SAP partners in Australia.
How SAVIC helps
SAVIC operates in Australia as SAVIC PTY LTD (ABN 97 674 117 410), registered at Mitchell Park, South Australia. Migrations are delivered by SAVIC Technologies' global team of 500+ SAP professionals in India and Singapore. SAVIC Technologies is an SAP Platinum Partner in India and has delivered 125+ S/4HANA Cloud projects worldwide.
We don't yet publish Australian client stories. One example from our global work: Adarsh Developers, an Indian real-estate developer, went live on S/4HANA in 23 days using a pre-configured template, and cut month-end close from 7 days to 2.
ECC to S/4HANA migration →See SAVIC's SAP services in Australia or book an ECC readiness assessment.
Frequently Asked Questions
When does SAP ECC support end in Australia?
The dates are the same worldwide. Mainstream maintenance for SAP ECC 6.0 (enhancement packages 6 to 8) ends on 31 December 2027. Optional extended maintenance is available to 31 December 2030 at an additional fee. Australian companies on older enhancement packages (EHP 0 to 5) are already outside mainstream maintenance.
How long does an ECC to S/4HANA migration take?
A focused mid-market migration typically takes 6 to 12 months; larger programmes with many entities, heavy custom code or payroll in scope take 12 to 18 months or more. Add time to choose a partner and secure budget before the project starts.
When should an Australian company start its ECC migration?
Working back from 31 December 2027, most companies need to start by the first half of 2027 at the latest. Many Australian businesses also avoid cutting over near 30 June because of end-of-financial-year close, which removes a window from the plan.
Can we stay on SAP ECC after 2027?
Yes, for a limited time. You can buy extended maintenance to the end of 2030, or, if you move to SAP ERP Private Edition through RISE with SAP, SAP has announced a transition option that runs from 2031 to 2033. Both cost extra and delay the move rather than replacing it.
Can SAP S/4HANA be hosted in Australia?
Yes. RISE with SAP and SAP Business Technology Platform can run in Australian cloud regions, which helps companies with data residency requirements. Confirm the exact region and hyperscaler in your contract.
Does SAVIC support ECC migrations in Australia?
Yes. SAVIC operates in Australia as SAVIC PTY LTD and delivers ECC to S/4HANA migrations, RISE with SAP and SAP GROW projects with its global team of 500+ SAP professionals. SAVIC Technologies is an SAP Platinum Partner in India and has delivered 125+ S/4HANA Cloud projects worldwide.
