The Extended Maintenance trap: what SAP Note 3255311 really covers for Solution Manager after 2027

1. What Extended Maintenance means for SAP Solution Manager

Extended Maintenance is the extended support phase offered by SAP after regular mainstream maintenance ends. For SAP Solution Manager 7.2, it is the lifeline many organizations are clinging to: mainstream maintenance ends on December 31, 2027, and extended maintenance promises support until the end of 2030. This very promise creates a dangerous misunderstanding.

Solution Manager 7.2 follows the maintenance model of the SAP Business Suite 7. The extended maintenance for Solution Manager is tied to the extended maintenance of Business Suite 7 and cannot be booked in isolation as a cheap extension. The terms and scope are governed by SAP Note 3255311, which is the definitive source for any planning.

1. The central misconception. Many organizations read the 2030 date as an extra breathing space and postpone their migration decisions accordingly. In reality, extended maintenance is not a frozen state of full operation, but rather reduced maintenance with a limited scope of functions, no further development, and no regulatory updates. Anyone planning with 2030 as a true end date is basing their plans on a false assumption.

2. Why Note 3255311 matters. The note specifies which functions are actually covered by extended maintenance and which parts are discontinued beforehand. Without reading it, any statement about continued operation until 2030 remains unreliable. This article highlights the most important points of the note, but it does not replace the need to review the current version.

2. Why the assumption that everything is fine until 2030 is deceptive

1. Limited scope of functions. Extended maintenance for Solution Manager covers only a portion of its functions: Requirements Management, Project Management, Process Management, Test Suite, Change Control Management, IT Service Management, and Landscape Management. Functions not included in this list are excluded from extended maintenance, even if they are currently in productive use.

2. Some parts end as early as 2027. Even organizations with extended maintenance until 2030 will lose certain components at the end of 2027. Tools closely integrated with Solution Manager, such as the SAP Landscape Manager, have their own, sometimes earlier, end dates. The idea that everything will remain unchanged until 2030 under extended maintenance is factually incorrect.

3. No further development, no regulatory updates. During extended maintenance, only critical bugs are fixed. There are no new features, no S/4HANA-specific enhancements, and no adjustments to new regulatory requirements such as the EU AI Act, NIS2, or DORA. If you rely on Solution Manager for compliance reporting, you will no longer receive updates to the underlying functions.

4. The link to Business Suite 7. Extended maintenance for Solution Manager is tied to the extended maintenance of Business Suite 7. It is therefore not a standalone, low-cost product, but part of a larger, premium-priced maintenance model. The costs must be viewed within the overall context of Business Suite maintenance.

3. What Note 3255311 specifically covers and what it does not

The following summary outlines the reliable key points of the note and the associated SAP documentation. It does not replace the need to check the current version, but it does make the planning basis explicit.

1. Mainstream Maintenance. It runs for Solution Manager 7.2 until December 31, 2027. Until then, full coverage applies, including standard bug fixes.

2. Scope of Extended Maintenance. Coverage is limited exclusively to Requirements Management, Project Management, Process Management, Test Suite, Change Control Management, IT Service Management, and Landscape Management. Anything outside this list is not part of the extended maintenance.

3. Coupling and Costs. Extended Maintenance for Solution Manager is granted to customers who utilize the optional Extended Maintenance for Business Suite 7. It follows the same terms and is therefore part of the premium-priced Business Suite maintenance model, not a separate low-cost plan.

4. Customer-Specific Maintenance after 2030. Beyond 2030, Solution Manager 7.2 will only be available under Customer-Specific Maintenance, with limitations. The terms for this are governed by SAP Notes 52505 and 305372. This is not a strategic operating model, but a strictly limited phase-out period.

5. Perpetual License. Customers with a valid on-premise maintenance contract hold a perpetual license and can technically continue to operate Solution Manager even after the maintenance phases end. However, technically possible does not mean supported: there will be no patches, no security fixes, and no support.

6. No ChaRM Data Migration. Regardless of the chosen maintenance option, SAP does not provide a tool to migrate existing ChaRM data to Cloud ALM. Extended Maintenance only delays this issue; it does not resolve it.

4. Where the Extended Maintenance trap snaps shut

1. The reduction is overlooked. The biggest danger is assuming that Solution Manager will remain usable in its current form until 2030. In reality, the scope is shrinking, new requirements are no longer being addressed, and individual components will reach their end-of-life as early as 2027. Those who plan based on this false assumption will only discover the gaps once they impact operations.

2. Compliance falls out of sync. Regulatory requirements continue to evolve, but Extended Maintenance does not. An audit-relevant process based on a frozen Solution Manager function may fall out of alignment with new obligations from the EU AI Act, NIS2, or DORA. Continuing operations under limited maintenance therefore also poses a regulatory risk.

3. Perpetual operation is a security risk. Simply letting Solution Manager run after the end of maintenance is tempting but risky. Without security fixes, the attack surface grows, and the lack of patches directly conflicts with the compliance requirements of NIS2 and DORA. What looks like cost-saving creates a growing, difficult-to-calculate risk.

4. Time is bought, but not used. Extended Maintenance buys time but does not eliminate any tasks. Those who do not actively use the gained time for inventory assessment and migration will face the same problem in 2029 or 2030, only with less room to maneuver and under higher pressure. Time pressure in ALM projects is expensive because it leads to shortened testing and lower process quality.

5. Cost accounting is deceptive. Because Extended Maintenance is tied to Business Suite 7, it is not a low-cost special rate. The surcharge continues over several years while the functional value declines. In terms of total cost of ownership, starting a migration early can be more cost-effective than continuing long-term operations under reduced maintenance.

5. A decision-making framework for the transition period

Extended Maintenance is not a mistake in itself; it is a legitimate tool for the transition period. The key is to treat it as what it is: a temporary bridge, not a permanent state.

1. Assess actual functional requirements. Compare which of the Solution Manager functions currently in production actually fall under Extended Maintenance. Functions outside the covered list require a successor well before 2030.

2. Track early end dates separately. Components with their own end dates, such as Landscape Management, should be assigned their own milestones, independent of the 2030 horizon.

3. Calculate costs in full. Compare the surcharge for Business Suite 7 Extended Maintenance over the planned duration against the costs of an early migration start. A longer bridge is not automatically the cheaper one.

4. Set a binding migration date. Only book Extended Maintenance with a fixed migration target. A realistic framework involves making the strategic decision by 2027 at the latest and having the successor in production well before 2030.

5. Rule out perpetual continued operation. Do not consider continued operation without support after 2030 as an option, as the security and compliance risks are unacceptable in regulated landscapes.

6. Tool Landscape

The following table classifies the options for the period after 2027. It shows that Extended Maintenance is a bridge with a reduced scope and not an equivalent continuation of full operations.

¹ Solutive AG is the initiator of the Change Orchestration Institute. The assessment in the table is a self-disclosure by the provider and is not part of an editorially independent validation. The Orchestration Layer is a migration target for change and transport governance, not a maintenance model for the Solution Manager itself.

The table highlights the core message: Only migrating to a future-proof platform—whether Cloud ALM, a third-party solution, or an orchestration layer—solves the problem permanently. All maintenance options merely postpone it, with declining functional value and increasing risk over time.

7. Operational consequences for SAP organizations

Note 3255311 outlines specific steps to take.

The first consequence concerns expectations. Extended Maintenance is not an extension of full operations until 2030, but rather a reduced maintenance service with a limited scope. Clarifying this internally prevents poor planning based on the 2030 date.

The second consequence concerns early end dates. Components such as Landscape Management will end as early as 2027 in some cases and require a separate plan that does not get lost in the 2030 horizon.

The third consequence concerns costs. Because Extended Maintenance is tied to Business Suite 7, its surcharge over the planned term must be included in the total cost analysis, and an early migration start should be evaluated as a serious alternative.

The fourth consequence concerns commitment. Extended Maintenance only provides value when paired with a firm migration goal. Without this goal, the bridge becomes a delay that pushes the problem into the future under even greater pressure.