SAP Cloud ALM vs Solution Manager: A Practical Migration Guide

SAP Application Lifecycle Management is the functional area with perhaps the most confusion in the current S/4HANA migration wave. Customers are operating on Solution Manager 7.2, aware that SAP is repositioning Cloud ALM as the strategic direction, and uncertain about what to migrate when and whether their investments in SolMan tooling carry forward. This post establishes the facts and gives segmented recommendations.

What each product covers

SAP Solution Manager 7.2

Solution Manager is the on-premise ALM suite that has served as the central IT operations and project management platform for SAP customers for over two decades. Its relevant capability areas for migration programmes:

Change Request Management (ChaRM): end-to-end change control workflow, transport management, dual-system landscape orchestration
Test Suite: test case management, manual test execution, integration with HP ALM/Micro Focus (historically), CBTA (Component-Based Test Automation)
ITSM: incident and problem management, service desk integration
System Monitoring and Root Cause Analysis (RCA): technical monitoring, E2E workload analysis, exception management
Focused Build / Focused Insights: agile project management and SAP-specific analytics bolt-ons
Landscape Management (LMDB): authoritative landscape topology database

Solution Manager runs as a dedicated ABAP system, typically sized at 4–8 HANA units depending on monitoring scope, and requires its own ABAP basis maintenance, patching, and transport management.

SAP Cloud ALM

Cloud ALM is a cloud-native SaaS service provisioned from the BTP. It is included at no additional licence cost for customers with an SAP Enterprise Support or SAP Cloud Support contract. Its capability set as of mid-2026:

Implementation and Project Management: requirement management, task management, fit-to-standard analysis, process management (backed by the SAP Signavio-aligned process content)
Change and Deployment Management: transport management for S/4HANA Cloud and hybrid landscapes, change request workflow
Test Management: test case management with integration to test automation frameworks (CBTA, Tricentis, Selenium-based)
Operations: monitoring for S/4HANA Public Cloud, S/4HANA Private Cloud managed systems, and BTP-based applications

Cloud ALM does not replace all Solution Manager capabilities in all deployment scenarios. Technical monitoring for complex on-premise landscapes, ChaRM for highly customised change governance workflows, and root cause analysis with ABAP workload statistics remain areas where Solution Manager 7.2 has deeper functionality.

Feature comparison

Capability	Solution Manager 7.2	Cloud ALM
Change Request Management	Full (ChaRM) — highly configurable	Functional for standard transport workflows; less configurable
Transport Management	Full — STMS orchestration	Supported for S/4HANA 2020+ landscapes
Test Case Management	Full (Test Suite)	Full — SAP recommended going forward
CBTA Automation	Full	Supported (CBTA integration)
System Monitoring	Deep (ABAP workload, E2E traces)	Functional for cloud / hybrid; limited for complex on-prem
Service Desk / ITSM	Full	Limited; integration to external ITSM tools
Process Library	SAP Best Practices content	SAP Signavio-aligned process content
Hosting	On-premise ABAP system	SaaS on BTP (SAP-managed)
Basis maintenance	Customer responsibility	None — SAP-managed
Licence cost	Included in Enterprise Support	Included in Enterprise Support / Cloud Support

The maintenance timeline

SAP has communicated a phased strategy for Solution Manager:

Solution Manager 7.2 has mainstream maintenance through the end of 2027, with extended maintenance available beyond that under SAP’s standard terms. SAP has not announced a removal date for SolMan 7.2 in the way it announced the 2027/2030 ECC maintenance deadline.
SAP’s strategic direction for new functionality is Cloud ALM. Solution Manager 7.2 is receiving maintenance and critical patches, but substantive new feature development is happening in Cloud ALM.
The migration tooling from SolMan to Cloud ALM is available: SAP provides migration guides and tooling for migrating test plans, process documentation, and system monitoring configuration.

The practical implication: if you are starting a new S/4HANA implementation programme today, Cloud ALM is the right ALM platform for the project work. If you are operating an established SolMan environment for production system monitoring and change control, there is no urgency to migrate in 2026 — but planning the migration within a 2–3 year horizon is prudent.

gantt
    title SAP ALM Platform Timeline (indicative)
    dateFormat  YYYY-MM
    axisFormat  %Y

    section Solution Manager 7.2
    Mainstream Maintenance     :active, sm1, 2020-01, 2027-12
    Extended Maintenance       :sm2, 2028-01, 2030-12

    section Cloud ALM
    Active Development         :active, calm1, 2021-01, 2030-12
    Strategic Platform         :active, calm2, 2023-01, 2030-12

    section Migration Window
    SolMan to Cloud ALM        :crit, mig1, 2025-01, 2028-12

Migrating from Solution Manager to Cloud ALM

Migration is not a single event — different SolMan capabilities migrate at different times based on readiness and operational criticality.

Test management

This is typically the first and lowest-risk migration. Cloud ALM test management is mature. The migration path:

Export test plans and test cases from SolMan Test Suite (transaction SOLMAN_TEST_MANAGEMENT).
Use the Cloud ALM migration guide to import test plans. The XML structure differs; expect manual rework for complex hierarchies.
Re-integrate automated test frameworks (CBTA scripts) with Cloud ALM’s test automation integration hub.
Run parallel operations for one test cycle before cutting over.

Change management

This is the highest-risk migration for organisations with complex ChaRM configurations. Before migrating:

Document every current ChaRM workflow customisation (change categories, approval roles, emergency change procedures).
Evaluate which customisations are genuinely needed vs legacy governance overhead.
Map current PFCG-based ChaRM roles to Cloud ALM role concepts.

Cloud ALM change management works well for organisations whose change governance aligns with SAP’s standard transport request workflow. It is less suitable for organisations with heavy custom ChaRM extensions, multi-system orchestration logic, or integration with non-SAP change management tools at the workflow level.

System monitoring

This is the last capability to migrate for most on-premise-heavy customers. Solution Manager’s agent-based monitoring (SAP Host Agent, diagnostics agents) has no direct equivalent in Cloud ALM for all scenarios. Cloud ALM operations currently monitors:

SAP S/4HANA Cloud (multi-tenant)
S/4HANA Private Cloud managed systems
BTP-based services

For complex on-premise landscapes with custom alerts, E2E workload analysis, and SAP-specific ABAP trace integration, Solution Manager monitoring remains the more capable tool in mid-2026. This will change — monitor SAP’s quarterly Cloud ALM release notes for operations capability additions.

Recommendations by customer segment

S/4HANA Public Cloud (multi-tenant) customers: Use Cloud ALM exclusively. It is designed for this deployment model; SolMan is not supported for Public Cloud monitoring.

S/4HANA Private Cloud or Rise customers starting a new implementation: Use Cloud ALM for project management, requirements, test management, and change management. Avoid standing up a new SolMan instance for the project.

Existing ECC customers with mature SolMan 7.2 environments: Keep SolMan for production operations and change control during the migration. Stand up Cloud ALM for the S/4HANA implementation project in parallel. Plan a phased SolMan decommission post-go-live, targeting test and change management first.

Organisations with complex ChaRM integrations or custom SolMan tooling: Do not rush. Map your current capabilities against Cloud ALM’s current feature set, identify the gaps, track Cloud ALM quarterly releases, and plan migration for the capabilities that are ready. Running parallel is operationally manageable if you are clear about which system owns which workflow.

The underlying principle is the same as clean core ABAP: the migration is an opportunity to simplify. If your current Solution Manager governance involves custom workflows built over years, the Cloud ALM migration is the right moment to ask whether each of those customisations is adding value or just complexity.

SAP, S/4HANA, Solution Manager, Cloud ALM, and related marks are trademarks of SAP SE.