SAP transformation · decision support

What does waiting past 2027 cost you? Run your own numbers.

SAP ECC 6.0 leaves mainstream maintenance in December 2027. Every year of deferral carries a maintenance premium, a rising bill for the same remediation, and regression effort spent on custom code you will eventually retire. Enter your estate and cost base below; every assumption is editable and every formula is shown.

December 2027 — ECC 6.0 mainstream maintenance endsSAP-published

End-2030 — optional extended maintenance at an additional ~2% on the maintenance baseSAP-published; edit below if your contract differs

01Your SAP estate

Figures pre-filled here are examples only. Replace them with your own.

Custom objects in your ECC system Example — change to your numbers

objects

Z-programs, enhancements, custom tables, forms and reports.

Custom objects believed unused Assumption — example

Objects with no executions in your usage logs. Retired at negligible cost, so excluded from remediation.

02Your cost base

Annual SAP maintenance and support spend Example — change to your numbers

A$ / year

The maintenance base your SAP support fee is calculated on.

Blended day rate you pay for SAP skills Example — change to your numbers

A$ / day

Your own internal or market rate — internal staff, contractors or partner, blended.

SAP releases or upgrades per year Assumption — example

per year

Regression-test effort per release on custom code Assumption — example

days

03Assumptions (editable)

Years of extended maintenance if you defer

years

0 = act before December 2027. SAP's optional extended maintenance runs to end-2030, so the maximum is 3.

Extended-maintenance premium SAP-published; edit if your contract differs

% of base

Applied to your annual maintenance spend for each year of deferral.

Effort to remediate or rebuild one custom object Assumption — example

days

Average across simple and complex objects, including testing.

Annual SAP-skills cost inflation Assumption — example

% / year

Applied to the remediation cost for each year you defer. Use your own rate-card history.

Under clean core: in-scope objects retired rather than moved to BTP Assumption — example

Objects replaced by standard functionality. The remainder are rebuilt as clean-core extensions on BTP.

Under clean core: reduction in per-release regression effort after moving to BTP Assumption — example

Side-by-side extensions are decoupled from the core release cycle, so each release retests less.

01Exposure if you defer

—

02Remediation cost

—at today's rates—if deferred

03Annual saving from clean core

—

Total cost by scenario

Remediation at deferred rates, plus the extended-maintenance premium and regression testing on custom code incurred while you wait.

Remediation at deferred rates
Extended-maintenance premium
Regression testing during deferral

Total cost by scenario, in Australian dollars
Scenario	Remediation at deferred rates	Extended-maintenance premium	Regression testing during deferral	Total

How this was calculated

Estimates from your inputs, not a quote. Every figure above is computed from the numbers you entered and the assumptions you can edit; nothing is drawn from VRdigital's rates, which we do not publish. Commercials arrive as a written fixed-price proposal with success criteria within five business days of a consult. Check the SAP-published dates and premium against your own maintenance contract.

Next step

Architectural Discovery Consultation

Bring the summary you copied. One senior architect works through your estate and your numbers and tells you plainly whether a clean-core migration is worth doing, and what we would commit to if it is.

Book the consultation See the SAP solutions

Fit confirmed honestly — if the outcome cannot be defined and measured, we say so.
The success criteria we would measure, with the measurement method stated.
The baseline identified, so the result can be verified against it.
A written fixed-price proposal within five business days.