SAP’s February 4, 2020 announcement offered two different clocks, not one blanket extension. The company committed to maintain SAP S/4HANA through the end of 2040. For core SAP Business Suite 7 applications, mainstream maintenance would run through 2027, followed by optional extended maintenance through 2030. [shared-281d9dd8dc44f3857f989a9d185f00c9e4836404f9e8fbdba85c0a75d0915aad]
That distinction changes the bargaining timetable. The extra mainstream period required no contractual change or additional fee, while the optional extension from 2028 carried a premium of two percentage points on the existing maintenance basis—not two percent of the customer’s contract. Customers that continued without choosing the extension would move to customer-specific maintenance, including problem-solving for known issues at unchanged fees. [shared-281d9dd8dc44f3857f989a9d185f00c9e4836404f9e8fbdba85c0a75d0915aad]
More time can reduce the disruption of a rushed migration, but it does not erase the cost of changing systems: conversion work, integration and operational risk still sit with customers. Nor does a long support promise by itself make a rival platform easier to adopt. The announcement’s competitive test is whether customers use the runway to compare viable alternatives and plan a transition—or treat continued support as a reason to defer one. Evidence that migration costs and credible alternatives were immaterial to customers’ choices would weaken that interpretation. [shared-281d9dd8dc44f3857f989a9d185f00c9e4836404f9e8fbdba85c0a75d0915aad]