Extended Maintenance to 2030: A Bridge, Not a Destination
Orpington Technologies | SAP S/4HANA Migration Insights
organizations, is as insurance for a migration program that is already underway and simply needs a realistic runway — not as a three-year pause button.
Used well, this is exactly the kind of tool a migration partner should be building into the plan from day one, rather than treating as a fallback to reach for once a deadline is already missed. Orpington Technologies Inc. builds extended maintenance into its client roadmaps deliberately, as a funded contingency for programs that need slightly more runway — not as the default plan, which is how too many organizations end up using it by accident.
A bridge is only useful if you're using it to cross to somewhere. Organizations that buy extended maintenance without a migration program moving underneath it are just paying rent on the middle of the river.
Extended maintenance at a glance
Question
Answer
Who is eligible
SAP ERP 6.0 customers on EHP 6–8 only
Coverage window
Jan 1, 2028 – Dec 31, 2030
Approximate cost
~2 additional percentage points on existing maintenance fees
What it preserves
New security patches, legal/regulatory updates, standard support
What follows it
Customer-specific maintenance (no new patches or legal updates) unless migrated
Sources & Further Reading
[1]
Rimini Street – “No Extension to SAP ECC 6 and Business Suite 7 Mainstream Maintenance
End Dates,” August 2025
[2]
SAP Licensing Experts – “SAP Extended Maintenance 2027-2030: Real Cost vs Options,”
April 2026
[3]
CIO – “Nearly half of SAP ECC customers may stick with legacy ERP beyond 2027,” June 4,
2025
© Orpington Technologies Inc.
www.orpingtontech.com
Page
3
of
3