SAP Cloud ALM and the gaps in change management: Status as of 2026

1. Definition: What Cloud ALM is and what it is not

SAP Cloud ALM is the strategic cloud platform for Application Lifecycle Management that SAP has been building incrementally since 2019. It is positioned as the successor to SAP Solution Manager (SolMan 7.2), whose mainstream maintenance ends on December 31, 2027. Customers can book extended maintenance for an additional fee until 2030, after which SolMan will run without SAP support.

Cloud ALM is a multi-tenant SaaS application that SAP operates on its own BTP. Customers activate it as part of their Enterprise Support or cloud subscription. There is no on-premise installation. Patches are rolled out every two weeks, and major features are released quarterly. This cloud-only architecture is the most critical design decision and influences every functional discussion.

1.1 The four core areas

SAP structures Cloud ALM into four official areas, which are visible in the Roadmap Explorer application and have varying levels of maturity.

Implementation: Tools for implementing new SAP solutions. Project Management, Solution Documentation (Soldoc), Process Management, Test Management (via Tricentis integration), Requirements, and Stories. This area is relatively mature.

Operations: System Monitoring, Health Monitoring, Job Monitoring, Configuration and Security Analysis, Real User Monitoring, Synthetic User Monitoring, and Integration Monitoring. Functionally, this area overlaps with SAP Focused Run. SAP positions Cloud ALM for medium and small landscapes, and Focused Run for large enterprises with high data volumes.

Change and Deploy Management: The area intended to replace ChaRM from the classic SolMan. This is where the most significant gaps exist as of spring 2026, which is the main topic of this article. Cloud ALM introduces its own terminology, such as features, releases, and deployment plans, which stem from agile project management rather than the classic ITIL vocabulary.

Business and Data Transformation: The newest area, focusing on business process mining, process intelligence, and data migration. Functions from SAP Signavio and LeanIX are being integrated here. Maturity is still in development.

1.2 What Cloud ALM is not

Three important clarifications that are often misunderstood in practice.

First, Cloud ALM is not SolMan in the cloud. The two platforms have fundamentally different architectures, data models, and functional designs. A 1-to-1 migration is technically impossible. Anyone migrating from ChaRM to Cloud ALM is starting over from a process perspective.

Second, Cloud ALM is not intended for all SAP customers. The official positioning addresses cloud-centric landscapes (RISE with SAP, GROW with SAP, S/4HANA Cloud Public Edition) and hybrid setups with cloud components. For pure on-premise S/4HANA landscapes without BTP components, Cloud ALM is functionally limited.

Third, Cloud ALM is not fit-to-needs, but fit-to-standard. SAP explicitly positions the platform as a standardized solution without customization options. Those who have defined their own workflows, custom CRM fields, or proprietary approval logic in SolMan will not find these capabilities in Cloud ALM.

1.3 Why this article is necessary now

Three parallel developments in 2026 make an honest gap analysis a mandatory topic. First, the 2026 DSAG Investment Report shows that 24 percent of customers are already using the SAP Integrated Toolchain either partially or fully, while 39 percent plan to use it in part. Conversely, 37 percent do not use it and have no plans to do so. Second, SolMan mainstream maintenance ends on December 31, 2027. Customers have less than 20 months for stocktaking, strategic decision-making, and migration implementation. Third, Cloud ALM maturity is growing quarterly, but it is not yet complete. Several functions from the ChaRM toolkit do not yet exist in Cloud ALM or are only available in a simplified form.

2. Market status: How far Cloud ALM has really come in 2026

2.1 DSAG Investment Report 2026

The 2026 DSAG Investment Report, published on February 26, 2026, is the most important independent data source. 24 percent of customers are already using the SAP Integrated Toolchain either partially or fully. 39 percent plan to use it at least in part. 37 percent have no usage and no concrete plan to date.

DSAG comments that the comparatively low willingness to invest in the public cloud shows that, from the customer's perspective, functional depth, integration capability, and reliable framework conditions remain decisive. Many companies have highly customized landscapes in which standardized Cloud ALM tools can only be used to a limited extent.

2.2 ERP landscape as context

56 percent S/4HANA On-Premise, 54 percent SAP ECC or Business Suite, 17 percent S/4HANA Private Cloud, 5 percent S/4HANA Public Cloud. The dominance of on-premise is the most important market reality. For these landscapes, Cloud ALM is not the natural ALM path.

2.3 Maturity assessment by area

Implementation: Mature. Operations: Conditionally mature. Change and Deploy Management: Gaps present. Business and Data Transformation: Under development. Anyone choosing Cloud ALM today is buying a platform with clearly growing maturity, but with 2026-level gaps that must be factored into the migration plan.

2.4 Cloud ALM patch strategy

SAP rolls out Cloud ALM patches approximately every two weeks. Customers cannot control the timing of these updates themselves. Major releases occur quarterly with documented roadmap features. A comprehensive testing strategy is a mandatory task for customers: regression tests, smoke tests after every patch, and a clear escalation process for unexpected changes in behavior.

3. The nine documented gaps in Change Management

Gap 1: Cross System Object Lock (CSOL)

What is missing: In SolMan ChaRM, the Cross System Object Lock (CSOL) prevents the same object from being modified in two parallel transports. As of May 2026, CSOL does not exist in Cloud ALM. Source: blue.works/en/cloud-alm-coffee-party-ix from February 18, 2026: "the Cross System Object Lock (CSOL) checks are still missing".

Practical impact: Conflicts between parallel transports are detected later, often not until the import into the Q-system. Workaround: SAP implemented the Cross-Reference Check function as a partial replacement (Q1 2025). This check detects conflicts during transport release, not when the change is created. A full CSOL equivalent is on the roadmap, but without a firm delivery date.

Gap 2: Custom workflows

What is missing: SolMan ChaRM allows for extensive customization of approval workflows. Cloud ALM is explicitly "fit to standard" and does not offer comparable customization options. Source: realtech.com: "Standardization over maximum flexibility".

Practical impact: Customers with established, complex ChaRM configurations must scale back their workflows to the SAP standard. Complex approval logic (such as branched paths, business escalations, or mandatory regulatory steps) cannot be mapped one-to-one. Workaround: External tools or third-party platforms. SAP explicitly recommends integration with third-party ALM tools for any extension requirements.

Gap 3: Full-featured Service Desk and ITSM

What is missing: SolMan includes a full-featured Service Desk with incident management, problem management, and a knowledge base via its ITSM module. Cloud ALM does not have this module to the same extent. Instead, SAP relies on integration with external ITSM platforms (ServiceNow, Jira Service Management). Source: realtech.com January 2025: "No full-featured Service Desk".

Workaround: Using ServiceNow or Jira Service Management as the Service Desk, with Cloud ALM acting as the change management layer. This is currently the most common setup for large enterprises in the DACH region.

Gap 4: End-to-end trackability

What is missing: SolMan ChaRM provides full traceability for every change, from initial request through development, testing, and approval to production deployment. While Cloud ALM improves its tracking capabilities quarterly, as of May 2026, the chain remains incomplete in certain scenarios. ASUG analysis, October 2025: "trackability of every change from start to finish are capabilities that Cloud ALM doesn't currently offer a like-for-like replacement".

Workaround: An external compliance logging platform (Splunk, ELK, Microsoft Sentinel) that aggregates all Cloud ALM events along with additional sources (Git, Jenkins, ServiceNow, BTP Audit Log).

Gap 5: Extensibility and Extensions

What is missing: SolMan allows for custom implementations via BAdIs, custom function modules, custom reports, and custom CRM fields. Cloud ALM does not offer a comparable extension layer. Customers can adjust configurations, but they cannot inject their own code into the platform.

Gap 6: Pure on-premise scenarios

What is missing: Cloud ALM is cloud-only. For customers with strict on-premise requirements, Cloud ALM cannot be used in the traditional sense. realtech.com, January 2026: "Many businesses assume that SAP Cloud ALM is the default replacement for SolMan, but it lacks key functionalities, especially for on-premise environments".

Gap 7: High data volumes

What is missing: Cloud ALM UIs are primarily designed for small and medium-sized customers. With very high data volumes (many systems, many alerts, many parallel transports), the standard UIs reach performance limits. saptechnicalguru.com 2026: "Data volumes on Cloud ALM are not to be too high, since the UIs are still designed for small and medium customers". Workaround: A two-tool strategy. Use Cloud ALM for standard functions and Focused Run for high-volume monitoring.

Gap 8: Data migration from SolMan

What is missing: There is no fully automated migration of existing data from SolMan to Cloud ALM. SAP offers a selective data transfer for certain data categories (such as document files since Q1 2026), but not for all legacy ChaRM data. Xitera Consulting: "Test data is not automatically transferred from SolMan 7.2." 8 GB storage limit for Soldoc. Workaround: Continue running SolMan in parallel with Cloud ALM as a read-only archive until the retention period has expired.

Gap 9: Conditional and consistency checks

What is missing: SolMan ChaRM offers a wide range of consistency checks (e.g., successfully imported into Q before production approval, all mandatory fields filled before status transition, correct dependencies between transports). Cloud ALM includes some, but not all, of these checks. Workaround: Quality gates via external CI/CD pipelines or third-party platforms with their own consistency check libraries.

GapSeverityWorkaround EffortRoadmap Status1 Cross System Object LockHighMedium (cross-reference check)Roadmap, no delivery date2 Custom WorkflowsHighHigh (third-party)Not strategically planned3 Full-featured Service DeskHighMedium (external ITSM)Not strategically planned4 End-to-End TrackabilityMediumMedium (external logging)Gradual expansion5 ExtensibilityHighHigh (third-party)Not strategically planned6 On-Premise OnlyStructuralStructuralArchitectural decision7 High Data VolumesMediumMedium (Focused Run)Performance optimization ongoing8 Data Migration from SolManMediumHigh (manual transfer)Selective Data Transfer being expanded9 Conditional ChecksMediumMedium (external pipelines)Gradual expansion

4. What Cloud ALM has added in 2025 and 2026

To ensure a balanced view of the gaps: Cloud ALM has delivered substantial new functionality over the last 18 months.

Q1 2025 enhancements: Downgrade Protection (DGP), cross-reference check, intrinsic downgrade check. Q1 2026 enhancements: Block check as part of the deployment app, ATC check at CTS-managed transport release, retrofit for upgrade and conversion in S/4HANA, Soldoc document migration, dashboard for RISE with SAP methodology executive view, configuration and security analysis compliance status.

Setup prerequisites for ATC check at transport release: SAP_BASIS 7.40 SP20 or higher, ST-PI 740 SP 26, SAP Notes 3421256 and 3425282 implemented. TMS must be configured client-specifically with TMS parameter CTC = 1. These prerequisites must be verified during the assessment.

Customers making a migration decision today should factor in the roadmap trajectory as an assumption, but not as a guarantee. Experience shows that 70 to 80 percent of announced roadmap features are delivered in the promised quarter, with the remainder delayed.

5. Tool landscape: Cloud ALM, ChaRM, and third-party providers compared

5.1 Evaluation table

ToolL1 CSOLL2 WorkflowL3 Service DeskL4 E2EL5 ExtensionL6 On-PremL8 MigrationCloud ALMPartialNoVia integrationGrowingNoCloud-onlySelectiveChaRM (SolMan 7.2)FullFullFullFullFullFullN/ARev-Trac PlatinumFullFullVia ServiceNowFullLimitedFullPossibleActiveControlFullFullVia integrationFullLimitedFullPossibleSmartChangeFullFullVia integrationFullLimitedFullPossibleOrchestration Layer¹FullFullVia integrationFullFullFullPossible

¹ Solutive AG is the initiator of the Change Orchestration Institute. The evaluation in the table is a self-disclosure by the provider and is not part of an editorially independent validation.

5.2 Three market clusters

Cluster A, Cloud-First: Customers who are cloud-centric, have low custom workflow requirements, and can live with a fit-to-standard approach. For them, Cloud ALM is the natural choice. Approximately 24 percent in the DACH market.

Cluster B, Hybrid: Customers with an on-premise S/4HANA focus and BTP extensions. They use Cloud ALM for cloud components, combined with third-party platforms. Largest market segment, estimated at 50 to 56 percent.

Cluster C, Strictly On-Premise: Customers with pure on-premise S/4HANA landscapes, often subject to regulatory constraints. For them, Cloud ALM is not an option. Estimated at 20 percent of the DACH market.

6. Migration strategies for SolMan to Cloud ALM

Strategy 1: Full transition to Cloud ALM

Suitable for Cluster A. Customer migrates completely from SolMan ChaRM to Cloud ALM. Prerequisites: Low share of custom workflows, no strict on-premise requirements, willingness to adapt processes. Total effort: 6 to 12 months.

Strategy 2: Hybrid with bridge tool

Suitable for Cluster B. Cloud ALM for cloud components, third-party platform as a bridge for on-premise. Total effort: 9 to 18 months. Phased plan: Q3 2026 assessment, Q4 2026 vendor selection, Q1 2027 parallel setup, Q2-Q3 2027 cutover.

Strategy 3: Full transition to third-party platform

Suitable for Cluster C. Total effort: 12 to 24 months. Often the only viable option for strict compliance or data sovereignty requirements.

Strategy 4: Extended maintenance until 2030

Bridge strategy for late adopters. SAP surcharge of 25 to 50 percent. A definitive migration decision must be made by 2029 at the latest.

StrategyClusterEffortSuitable for1 Full Cloud ALMMediumCloud-first2 Hybrid with bridge toolBHighHybrid3 Full third-partyCHighStrict on-prem4 Extended maintenance until 2030TransitionLowLate adopters

7. Architectural consequences of the cloud-only model

Cloud ALM is cloud-only; this is the core architectural decision. For DACH customers with strict data sovereignty requirements, this may rule out Cloud ALM. On March 17, 2026, the DSAG took a position on German cloud sovereignty, identifying data sovereignty as a key concern.

The patch cycle reality (every two weeks) requires a continuous testing strategy: smoke tests after every patch, regression tests for critical workflows, and clear escalation processes for behavioral changes.

The end-to-end compliance architecture requires a central compliance logging platform (Splunk, ELK, Microsoft Sentinel) as an aggregator for all Cloud ALM events plus supplementary sources.

SAP operates a customer influence process for Cloud ALM. Customers can submit improvement requests and vote on them, which influences SAP roadmap prioritization. Accessible via the SAP Cloud ALM Improvement Request Portal with an S-user login. However, customer influence cannot persuade SAP to abandon its fit-to-standard philosophy. Structural gaps (Gap 2 custom workflows, Gap 5 extensibility) will not be resolved through customer influence processes.