SAP Cloud ALM (Cloud Application Lifecycle Management, or CALM) is SAP’s cloud-native ALM platform, provided at no extra cost to customers with SAP Enterprise Support or cloud subscriptions. CALM covers project management, SAP Activate implementation, operations monitoring, and parts of change management. The platform is primarily designed for cloud-first, fit-to-standard S/4HANA implementations. In Q1 2026, SAP delivered several functional enhancements—or announced them on the official roadmap—that are relevant for customers with complex landscapes. Three key points stand out: the Retrofit App, available for CTS-managed dual-track landscapes since December 17, 2025; the ATC export check in transport checks, delivered on June 25, 2025; and the automatic ATC trigger for CTS-managed transport releases, announced for Q1 2026, which includes the ability to block releases if errors occur (Source: blue.works, “What’s New Week 51 2025”; community.sap.com, “Stay Current with SAP Cloud ALM,” April 2026; SAP Help Portal Cloud ALM Documentation). The Q1 2026 release represents the most significant move toward ChaRM-equivalent functionality to date. It closes gaps, though not all of them.
The three Q1 innovations address specific customer scenarios: Retrofit App for dual-track customers. The Retrofit App is relevant for customers running parallel development tracks: a maintenance track for hotfixes and adjustments that must go into production immediately, and an evolution track for projects moving through QAS to PRD. The Retrofit App automates the transfer of changes between these tracks, reducing the manual effort required for back-porting. Customers without a dual-track operation do not benefit from this feature. ATC integration for code quality checks. The ATC export check and the announced automatic ATC trigger are relevant for customers performing ABAP development who use ATC as a quality assurance tool. These functions are not relevant for pure customizing changes or cloud customers without ABAP development. CTS-managed transport scenarios. Both functions require CTS-managed transports. Customers using gCTS (Git-based Change and Transport System) or other transport mechanisms must verify applicability separately.
In detail: Retrofit App. The app supports the transfer of ABAP changes from the evolution track to the maintenance track (and vice versa), taking transport dependencies into account. It reduces the manual effort for back-ports and the associated sources of error. It has been available since December 17, 2025, for CTS-managed dual-track setups. Important limitation: The app does not support all object types equally. Manual verification is still required for complex customizing objects with mutual dependencies. ATC export check. Checks for ATC findings before exporting a transport (the step out of DEV). Available since June 25, 2025. Configurable: which ATC check variant is used and which types of findings block the export. Automatic ATC trigger during transport release. Announced for Q1 2026. Automatically triggers an ATC check when a transport is released from the development system, with the option to block the release if critical ATC findings are detected. This is the functionality familiar to ChaRM customers: a quality gate in the transport workflow. The current functional status: SAP Cloud ALM has moved toward ChaRM equivalence, but has not yet fully achieved it.
Despite the Q1 enhancements, functional gaps remain: Single-landscape CSOL is still missing. The Cross-System Object Lock function in Cloud ALM addresses multi-landscape scenarios, not single-landscape setups. For customers currently using ChaRM with single-landscape CSOL (protection against simultaneous editing of the same object in parallel lines within the same landscape), there is still no equivalent in Cloud ALM. The Q1 2026 updates do not change this. Release cycles and import windows. The definition of release windows, freeze periods, and automated import cycles following the ChaRM model is not natively available in Cloud ALM. Customers must organize this process outside of Cloud ALM or supplement it with third-party tools. End-to-end transport orchestration. Cloud ALM offers transport monitoring, but not full automated transport orchestration with sequence validation, dependency analysis, and automatic import cycles. Non-CTS scenarios. Most new features are designed for CTS-managed transports. A functional gap remains for gCTS, SAP BTP deployments, and non-ABAP changes.
Update your functional inventory. Anyone who created their functional inventory for the Cloud ALM decision before Q1 2026 should update it now. The Retrofit app and the ATC trigger are new features, but the single-landscape CSOL gap remains open. Don't delay the decision any further. SolMan mainstream maintenance ends on December 31, 2027. A migration project takes 9 to 18 months. Those who continue to delay the decision will be migrating under time pressure. The Q1 2026 update is no reason for further delay; it simply adds to the basis for your decision. Hybrid option for single-landscape customers. Customers with a single landscape and CSOL requirements can use Cloud ALM for monitoring and ITSM, while covering transport orchestration via an SAP-native third-party provider (Rev-Trac, ActiveControl, or Solutive ESM Suite). This is a hybrid architecture with a higher degree of complexity, but it provides full functional coverage.
The SAP Cloud ALM Q1 2026 release brings the Retrofit app and ATC integration. The single-landscape CSOL gap remains open. For ChaRM customers, Q1 2026 changes the basis for the decision, but not the core message: update your functional inventory and do not delay the decision any further.