What Is SAP Cloud ALM?
SAP Cloud ALM (Application Lifecycle Management) is SAP's cloud-native platform for managing implementation projects, operations, and continuous improvement of SAP solutions. It replaces the on-premises SAP Solution Manager (SolMan) as the strategic ALM platform for organisations running SAP in the cloud — including RISE with SAP, GROW with SAP, and SAP BTP-based cloud products.
Cloud ALM provides capabilities across four primary domains: implementation management (project management, requirements, testing, and deployment); operations (monitoring, alerting, integration monitoring, and business process monitoring); continuous improvement (quality management and change tracking); and analytics (operational dashboards and performance insights).
Unlike Solution Manager, which was a complex on-premises product requiring significant infrastructure investment to operate, Cloud ALM is a SaaS offering managed entirely by SAP. This significantly reduces the operational burden — but introduces its own commercial complexities.
What's Included vs. What Costs Extra
SAP's marketing position is that Cloud ALM is "included" with SAP cloud subscriptions. This is technically accurate — but the inclusion is not unconditional, and the boundaries of what is included versus what requires additional commercial agreement are worth understanding carefully.
Included in Cloud Subscriptions
- Cloud ALM tenant provisioning for RISE/GROW customers
- Implementation management features (projects, requirements, test management)
- Basic operations monitoring for SAP BTP and SAP S/4HANA Cloud
- Integration monitoring for SAP Integration Suite connections
- Business process monitoring (core scenarios)
- Cloud ALM API access for standard integrations
- Standard support and software updates (managed by SAP)
Not Automatically Included
- Extended monitoring for hybrid or on-premises SAP systems
- Advanced analytics and custom dashboards beyond standard templates
- Third-party system integrations requiring additional BTP capacity
- High-volume data retention beyond standard periods
- Custom extensions built on SAP BTP (consume BTP capacity units)
- Professional services for Cloud ALM implementation and configuration
- Monitoring for non-SAP systems in your landscape
"We have seen RISE customers receive their Cloud ALM tenant with the assumption it covers everything — only to discover that monitoring their legacy on-premises SAP systems requires additional commercial agreements and, in some cases, BTP capacity purchases."
Cloud ALM vs Solution Manager: Capability Comparison
Solution Manager was a comprehensive (if complex) platform that handled a very wide range of ALM scenarios for SAP customers. Cloud ALM is maturing rapidly, but there remain meaningful capability gaps for organisations with complex or heavily customised SAP landscapes. Understanding these gaps is important for assessing the true cost of migration.
Where Cloud ALM Matches or Exceeds Solution Manager
For organisations running SAP S/4HANA Cloud (Public Edition) or RISE with SAP (Private Edition), Cloud ALM provides native, tightly-integrated monitoring and operations that was difficult or impossible to achieve with Solution Manager. The implementation management features — particularly test management and transport tracking for cloud deployments — are generally superior to SolMan equivalents. The operational overhead is dramatically lower: SAP manages Cloud ALM's infrastructure, updates, and availability.
Where Cloud ALM Still Lags
Solution Manager has historically provided very deep monitoring for complex on-premises SAP ABAP systems — including custom ABAP performance analysis, detailed work process monitoring, and highly configurable alerting. Cloud ALM's monitoring for on-premises systems is more limited and requires the SAP Cloud ALM Data Collector to be installed locally, creating an additional integration point to manage. Organisations with heavily customised ECC or on-premises S/4HANA landscapes should conduct a functional gap analysis before assuming Cloud ALM is a complete SolMan replacement.
ITSM Integration
Solution Manager included a built-in ITSM capability (incident management, change management) that some organisations used as their primary ITSM platform. Cloud ALM does not include a native ITSM module — SAP expects ITSM requirements to be handled by third-party tools such as ServiceNow or Jira, with Cloud ALM providing monitoring feeds into those systems. For organisations that relied on SolMan's ITSM, this represents a functional gap that has a real cost implication.
Migration Licensing Implications
The migration from Solution Manager to Cloud ALM has specific licensing considerations that are frequently overlooked in transformation planning.
Solution Manager Maintenance Costs
Solution Manager is licensed as part of SAP NetWeaver and is included in the standard SAP software maintenance fee — so there is no incremental licence cost for Solution Manager itself. However, maintaining Solution Manager on-premises requires infrastructure, BASIS resources, and periodic upgrades. For organisations migrating to RISE, these costs should be explicitly modelled as part of the RISE business case, as they represent genuine savings.
The Transition Period
SAP has not mandated a hard cut-off date for Solution Manager support, though the message is clear that Cloud ALM is the strategic direction. Organisations can run both Solution Manager and Cloud ALM in parallel during a transition period — and many do. The commercial implication is that there is no immediate cost pressure to accelerate Cloud ALM migration, giving organisations time to conduct proper transitions rather than rushed cutovers.
Negotiating the Transition
The Solution Manager to Cloud ALM migration is a valuable negotiating moment in any SAP renewal or RISE discussion. If SAP is pressing for a RISE commitment, the removal of Solution Manager operational costs (infrastructure and BASIS support) is a legitimate offset to include in the RISE business case — and organisations should ensure SAP acknowledges this value when discussing RISE pricing.
Cloud ALM and BTP Consumption
SAP Cloud ALM runs on SAP Business Technology Platform (BTP). While Cloud ALM itself does not directly consume the BTP capacity credits in your organisation's RISE contract for standard functionality, there are scenarios where Cloud ALM usage or extensions do touch BTP capacity.
Custom extensions and integrations built in BTP to enhance Cloud ALM — for example, custom monitoring dashboards, advanced reporting, or integration with non-SAP ITSM tools — will consume BTP capacity units. Organisations building significant Cloud ALM customisations should budget for incremental BTP capacity, or negotiate a higher BTP capacity allowance as part of their RISE contract.
Additionally, the Cloud ALM Data Collector for on-premises systems streams data to SAP's cloud infrastructure — the data volumes involved should be reviewed against any cloud data egress costs in your hosting and cloud contracts.
Negotiating Cloud ALM in Your SAP Contract
Cloud ALM is not a commonly negotiated standalone item — but it should be addressed explicitly in any RISE or SAP cloud subscription negotiation. The following points are worth raising explicitly with SAP during commercial discussions.
Define Scope of Inclusion in Writing
Ensure your contract explicitly defines what Cloud ALM capabilities are included in your subscription — particularly around on-premises system monitoring, number of managed tenants, and data retention periods. SAP's sales teams often speak in general terms about Cloud ALM being "included"; the specific boundaries matter and should be documented.
Negotiate BTP Capacity Headroom
If you anticipate building Cloud ALM extensions or integrations on BTP, negotiate sufficient capacity headroom in your RISE BTP entitlement to accommodate these workloads without triggering overage charges. BTP capacity purchased at contract signature is materially cheaper than overage charges incurred during contract term.
Hybrid Landscape Coverage
If you have on-premises SAP systems that will remain in your landscape during the RISE transition, explicitly negotiate the monitoring scope for those systems in Cloud ALM. SAP should provide clarity on whether the Data Collector is included and supported at no additional charge, and what level of monitoring coverage applies to non-RISE systems.