When you compare SAP Cloud ALM vs Solution Manager, ChaRM's job moves to two Cloud ALM capabilities: Change Enablement, and Release and Deployment Orchestration. A Cloud ALM Feature takes the place of the ChaRM change document. As of 22 October 2026, SAP Solution Manager 7.2 leaves mainstream maintenance on 31 December 2027. This guide maps ChaRM to Cloud ALM from SAP's own documentation, then shows where ServiceNow change fits for teams that run work across ServiceNow and SAP and need to trace one change across both systems.
- Mainstream maintenance for SolMan 7.2 ends at the end of 2027, per SAP's Solution Manager support page.
- SAP's SolMan-to-Cloud ALM terminology map pairs a ChaRM change with a Cloud ALM Feature.
- Cloud ALM's ready-made ServiceNow link forwards events as incidents, with no documented change-request link.
| Capability | SAP Solution Manager ChaRM | SAP Cloud ALM | SAP source |
|---|---|---|---|
| Change object | Request for change, then change documents (normal, urgent and other types) | Feature, from Not Planned to Deployed | SAP Learning: Feature definition |
| Transport tools | CTS, CTS+ for non-ABAP content, central CTS | CTS, CTMS and ATO. CTS+ is not supported. | Integration of Deployment Tools |
| Approval to production | Approval procedure on the request for change, with the change manager as default approver | Project Admin or Change Manager approves the Feature for production | SolMan approval procedures |
| Retrofit | Retrofit between maintenance and project systems | Retrofit app, with ST-PI 740 SP31 or higher | Performing a Retrofit in Cloud ALM |
| Downgrade protection and cross-reference checks | Part of ChaRM and Quality Gate Management | Import checks against production systems only | Cloud ALM Transport Checks |
| ATC checks | ATC results in transport-related checks | ATC export check on modifiable CTS transports | SolMan 7.2 SPS 9 release notes |
| Cross-system object lock | Locks a changed object centrally in Solution Manager | Planned mid-term (by end of 2025) on SAP's 2024 roadmap; delivery not confirmed | SolMan cross-system object lock |
| Urgent change | Urgent change type | New Feature Type for Fixes, planned mid-term (by end of 2025) on SAP's 2024 roadmap; delivery not confirmed | SAP ALM Summit 2024 roadmap |
| Quality Gate Management | Quality Gate Management scenario | Currently not in scope | SAP's implementation transition page |
| ITSM | SolMan ITSM, with a Service Desk Webservice API | ServiceNow Incident Management integration for events; ITSM scoped out of Cloud ALM | Cloud ALM ticket-system integration |
| Migration of change history | Change documents stay in Solution Manager | ChaRM workflows and change documents are not migrated | SAP's transition planning lesson |
| License | Extended maintenance to 2030 for selected functions | No license; one free tenant per customer number | SAP Cloud ALM support page |
When does SAP Solution Manager maintenance end?
SAP Solution Manager 7.2 leaves mainstream maintenance on 31 December 2027, according to SAP News on 18 June 2026. SAP KB 3585220 recommends starting the move to SAP Cloud ALM now and finishing it before 2028. SAP plans no release after 7.2, which makes the SolMan 2027 date the planning anchor for every ChaRM team.
According to SAP KB 3585220, customers should start the transition and "complete it before 2028." SAP Learning's ALM strategy lesson states that there are no plans for further releases after SAP Solution Manager 7.2. SAP's Solution Manager page recommends that all customers transition to SAP Cloud ALM before the end of 2027. The same June 2026 SAP News article points to SAP Notes 52505 and 3255311 for maintenance options. Because 7.2 is the final release, the SAP Solution Manager end of maintenance date sets the deadline for every SAP Cloud ALM vs SolMan plan.
What does Solution Manager extended maintenance to 2030 cover?
Extended maintenance to the end of 2030 covers selected functionality only. SAP's ALM FAQ lists the covered areas: requirements management, project management, process management, test suite, change control management, IT service management (ITSM) and landscape management.
The FAQ says customers who choose the optional extended maintenance for SAP Business Suite 7 receive SolMan 7.2 extended maintenance at no additional cost. SAP's 2020 Business Suite 7 announcement prices that Business Suite 7 option at a premium of two percentage points on the existing maintenance basis. Some trade press describes SolMan extended maintenance as paid. Both statements hold: the SolMan component adds no charge, and the Business Suite 7 extended maintenance it depends on carries the premium. After 2027, or 2030 with extended maintenance, SolMan 7.2 moves to customer-specific maintenance.
ECC has a separate path. SAP describes its SAP ERP, private edition, transition option as usable from 2031–2033 and not a maintenance prolongation of SAP ERP. An update on 13 October 2026 says subscriptions for the transition option may run until 31 December 2035, with further prerequisites. An SAP spokesperson told The Register in January 2025 that the option does not extend the mainstream maintenance deadlines communicated in 2020.
Is SAP Cloud ALM free?
SAP Cloud ALM is license-free for customers with an eligible support contract. SAP's Cloud ALM page states that there is no license for SAP Cloud ALM and that eligible customers can use one tenant per customer number free of charge. Eligibility covers SAP Cloud Service subscriptions containing Enterprise Support, cloud editions, SAP Enterprise Support, and Product Support for Large Enterprises.
SAP's ALM FAQ adds that RISE with SAP customers can request a Cloud ALM tenant without additional license or subscription fee. SAP does not plan to include Cloud ALM usage rights in SAP Standard Support agreements.
The free tenant has a fair-usage limit. SAP Learning's Cloud ALM course says SAP raised the base and extension memory from 8 GB to 24 GB on 21 January 2026, covering SAP HANA memory and monthly outbound API data transfer. SAP's usage rights page still lists the 8 GB baseline, so both figures appear in SAP material today. The same usage rights page bars Cloud ALM from automating productive business processes. Capacity above the baseline is available through the paid SAP Cloud ALM, tenant extension. SAP has not published its price.
Cloud ALM also reaches older ABAP systems. SAP's Cloud ALM setup course lists SAP S/4HANA on-premise, SAP S/4HANA Cloud Private Edition and ECC systems on SAP NetWeaver AS ABAP 7.40 or higher as CTS-integrated.
What replaces Solution Manager ChaRM in SAP Cloud ALM?
SAP Cloud ALM replaces ChaRM with two capabilities SAP calls Change Enablement and Release and Deployment Orchestration. The central object is the Feature, which SAP Learning defines as the entity for change documentation and deployment orchestration. Features carry the transports, the test status and the approval for production in one record.
SAP's terminology page lists Cloud ALM's change enablement and release and deployment orchestration against Solution Manager's change request management, and adds: "This comparison doesn't indicate feature parity between SAP Solution Manager and SAP Cloud ALM." SAP's transition planning lesson is direct: "There is no one-to-one functional parity." The SAP ChaRM replacement inside Cloud ALM is a set of apps: Features, Transport Checks, Retrofit and Deployment.
How does a Cloud ALM Feature compare with a ChaRM change document?
In ChaRM, a request for change runs through an approval procedure, and the associated change documents are created once it reaches Approved, per SolMan's approval procedures documentation. The change manager is the default approver, the workflow templates are CRM_RFC_APRV and CRM_RFC_APPR, and the change manager role is SAP_CM_SMAN_CHANGE_MANAGER. Change types include normal and urgent changes.
In Cloud ALM, SAP's ChaRM transition lesson maps change document to feature and continuous cycle to deployment plan or system group. In SAP Cloud ALM vs ChaRM terms, the change document becomes a Feature. A Feature moves from Not Planned and In Specification through In Implementation and In Testing to Ready for Production and Deployed, per SAP Learning's deployment lesson.
Which transport tools does SAP Cloud ALM change management use?
SAP Cloud ALM change management runs transports through three deployment tools, listed on SAP's Integration of Deployment Tools page:
- CTS: SAP S/4HANA Cloud Private Edition, SAP S/4HANA, AS ABAP on-premise and Employee Central Payroll.
- CTMS: content supported by SAP Cloud Transport Management service.
- ATO: SAP S/4HANA Cloud and SAP Integrated Business Planning.
The same page shows that only CTS supports releasing transports, Transport of Copies and transport checks from Cloud ALM. CTMS accepts released transports only. SAP's setup course states plainly: "CTS+ is not supported." Teams that run non-ABAP changes through CTS+ in Solution Manager need a separate route for those objects.
Every transport move runs through the configured deployment tool, which reports status back to the Feature. SAP's deployment documentation puts it this way: "SAP Cloud ALM does not communicate directly with your managed systems." Central CTS stays with Solution Manager: SAP's CTS documentation says central CTS cannot be used outside of ChaRM or QGM.
Who approves a change to production in Cloud ALM?
A Project Admin or Change Manager approves a Feature for production, per SAP's go-live lesson. A Feature must reach Ready for Production before any transport goes to a production system, and confirming deployment sets it to Deployed, after which the Feature is locked, per SAP's Deploying Features page.
The Features API lets external tools switch most Feature statuses. SAP excludes one step: "the approval for production should be done in the Features app." The Workflow API lets an external system move a Feature from In Testing to Successfully Tested, and users outside Cloud ALM user management appear as External User in the history.
Does SAP Cloud ALM support retrofit?
Yes. SAP documents a Retrofit app in Cloud ALM for keeping maintenance and project systems in sync. SAP's Performing a Retrofit page lists the prerequisites: ST-PI 740 SP31 or higher, SAP Notes 3639096 and 3688071, the Retrofit Performer role, and the use case task Transports: Retrofit (client-specific). Automatic objects move by Transport of Copies. Manual objects are processed by hand. Since 22 July 2026, the Retrofit app history records the result of Transport of Copies removal.
SAP also publishes KBA 3768016 on retrofit categories and held a technical deep-dive webinar on 24 February 2026 titled "Next-Generation Change Management in Cloud ALM : From Retrofit to Intelligent Deployment Checks." Several ranking pages still describe retrofit as absent from Cloud ALM. In Solution Manager, retrofit synchronizes changes when several releases are processed at the same time.
Which transport checks run before production?
Cloud ALM import checks cover Downgrade Protection and a Cross-Reference Check, per SAP's Transport Checks page. They run against production systems only: "Pre-production and quality assurance systems are currently not supported." Downgrade Protection considers transports released in the last 180 days by default, and the window can be raised in table /SDF/CMO_TR_CONF. The Cross-Reference Check covers ABAP repository, data dictionary, customizing, SAP Notes and BW objects, plus CDS views as of SAP_BASIS 7.52. The export check is the ATC check on modifiable CTS transports.
In Solution Manager, SAP KBA 3015525 describes downgrade protection as a feature integrated in Change Request Management and Quality Gate Management. SolMan 7.2 SPS 9 release notes list DGP, the cross-reference check and ATC results inside the transport-related checks.
What changes when you move from ChaRM to Cloud ALM?
Moving from ChaRM to Cloud ALM changes four things SAP documents: change history stays in Solution Manager, Quality Gate Management is out of scope, CTS+ is unsupported, and transport checks cover production systems only. SAP's 2024 roadmap targeted cross-system object lock and a new feature type for fixes for end of 2025; no SAP page reviewed confirms delivery.
SAP's implementation transition page says the transition of Change Control Management related data from Solution Manager to Cloud ALM "is not planned." The same page recommends closing open change cycles in Solution Manager, then activating Deployment Management in Cloud ALM, and lists Quality Gate Management as currently not in scope. Plan where historical change documents stay readable for audit before 31 December 2027. Echelon's guide to documentation that preserves modification history covers the ServiceNow side of the same requirement.
SAP's 2024 ALM Summit roadmap listed cross-system object lock, retrofit and a New Feature Type for Fixes as planned "mid-term = by end of 2025." Retrofit has shipped. In Solution Manager, cross-system object lock locks an object centrally when it changes in a managed system, and downgrade protection requires it to be active. The default conflict scenario is cross-cycle with change type relation Urgent Only.
Testing moves to Cloud ALM test management. SAP's test automation partner page says you will be able to create automated test cases from SAP Cloud ALM into your Tricentis tenant, using Tricentis Test Automation for SAP integrated with SAP Cloud ALM.
How does the Solution Manager to Cloud ALM migration work?
The Solution Manager to Cloud ALM migration follows a sequence SAP publishes on its Cloud ALM transition page: switch service and operations to Cloud ALM now, adopt Cloud ALM for implementation at your own pace, and add SAP Focused Run for advanced operations use cases. Change control sits in the implementation step, so ChaRM teams set their timing before 2028.
- Run the SAP Readiness Check for SAP Cloud ALM to analyze current Solution Manager usage.
- Move solution documentation with Selective Data Transfer.
- Close open ChaRM change cycles, then activate Deployment Management in Cloud ALM.
Run the ServiceNow side of the cutover with the same discipline. Integration flows that touch SAP need ServiceNow ATF as a gate before every deployment, and upgrade regression suites keep releases moving while both systems change. Treat the first weeks of the new change process as a hypercare period after go-live, with named owners for every failed import or rejected approval.
Where does ServiceNow fit beside SAP Cloud ALM?
ServiceNow fits beside SAP Cloud ALM as the IT service management layer, a role SAP assigns to third-party tools. SAP's transition map lists IT Service Management as not in scope for Cloud ALM, with the note "Can be provided by 3rd-party ITSM." For most teams, SAP Cloud ALM vs ServiceNow is a division of work between two systems.
SAP documented this split in Solution Manager as well. SAP KBA 2556872 covers integrating Solution Manager with external service desk systems such as ServiceNow. SAP KBA 2506154 covers ChaRM integration with external service tools, including the symptom "Request for Change not created in ServiceNow."
Change risk for SAP work in ServiceNow depends on how SAP systems are modeled as configuration items. Echelon's guide to standing up a new ServiceNow instance calls the CMDB the most important thing to get right.
What does the SAP Cloud ALM ServiceNow integration cover?
SAP Cloud ALM provides a ready-to-use integration with ServiceNow Incident Management with a pre-defined API mapping, per SAP's ticket-system integration guide. It runs from Intelligent Event Processing: a Cloud ALM event situation can create a ServiceNow incident. SAP says ticket integrations are always bi-directional, and its ServiceNow example "does not consider the back communication from ServiceNow to SAP Cloud ALM." The customer builds that return path.
The guide does not mention change requests. No SAP page reviewed for this guide describes a native link between a ServiceNow change request and a Cloud ALM Feature. The documented change integration points are the Features API and Workflow API, with production approval held in the Features app. Third-party apps on the ServiceNow Store and SAP Store add change and transport synchronization, and they differ in integration depth.
What does ServiceNow provide for SAP today?
ServiceNow's SAP spokes for Integration Hub cover ERP transactions. The SAP S4 HANA OData spoke, tested with SAP S/4HANA version 2023, groups its actions into categories such as contract, sourcing, purchase order, invoice and supplier management. ServiceNow moved all SAP spokes to the Store on 1 March 2022. The ServiceNow docs reviewed for this guide show no spoke for Solution Manager or Cloud ALM.
Custom ServiceNow-to-SAP change flows also have to survive ServiceNow's twice-yearly releases, because upgrades can break integrations that rely on deprecated APIs or undocumented behavior.
Who should own the change record, the approval and the transport?
Teams running both systems need one owner per object. Each system documents a different part of the same change:
- Govern: the ServiceNow change request applies change approval policies and records the approvals.
- Gate: the Cloud ALM Feature holds transports, test status and the Ready for Production approval.
- Execute: CTS, CTMS or ATO moves the transports and reports status back to the Feature.
- Check: Cloud ALM Transport Checks record downgrade and cross-reference findings before production.
Teams must decide which approval is the control of record: the ServiceNow change approval or the Cloud ALM Ready for Production gate. Auditors will ask, and SAP keeps production approval inside the Features app. Both records need to hold up in an audit, the same requirement Echelon sets out for audit trails on governed ServiceNow automation.
Is SAP removing Basic Auth for ServiceNow integrations in November 2026?
No SAP or ServiceNow source shows Basic Auth ending for ServiceNow change or transport integrations in November 2026. The November 2026 date comes from a ServiceNow note about SAP SuccessFactors, and SAP has since moved the SuccessFactors API Basic Auth deletion date to 12 November 2027 in its SuccessFactors deprecation notice.
ServiceNow's SuccessFactors spoke v3.x.x setup page, updated 12 March 2026, says "SuccessFactors will be deprecating basic authentication by Nov 2026" and points to OAuth SAML in spoke v4.12.0. SAP's notice, revised on 12 June 2026, changed the deletion date from 20 November 2026 to 12 November 2027: "will be deleted on November 12, 2027." Basic Auth will be off by default in 1H 2027 with an opt-in, then fully disabled in 2H 2027. One SuccessFactors item keeps a November 2026 date: Basic Auth for UI login and third-party corporate IdP direct integration, deleted 13 November 2026.
ServiceNow's SAM for SAP connection guide uses a WSDL service named /NOW/SAMP with binding NOW_SAMP and says: "The Basic Auth authentication method is planned for deprecation by SAP." It gives no date and recommends OAuth 2.0. The SAP S4 HANA RFC spoke release notes, from 1.0.0 in February 2021 to 2.7.0 in June 2026, contain no Basic Auth deprecation entry.
How many SAP customers still run ECC?
ECC remains widespread. Gartner projected 17,000 ECC holdouts, nearly half of the ECC customer base, by 2027, according to CIO.com in June 2025. The DSAG Investment Report 2026 puts SAP ECC and the older Business Suite at 54 percent of respondents, down from the 68 percent DSAG reported for 2024.
Frequently asked questions.
Is there ChaRM configuration in Cloud ALM?
SAP maps ChaRM's change document to a Cloud ALM feature and the continuous cycle to a deployment plan or system group, per SAP Learning's ChaRM transition lesson. Cloud ALM teams configure Features, a deployment tool (CTS, CTMS or ATO), Transport Checks and deployment plans or system groups in place of ChaRM change cycles. SAP's terminology map states that the comparison does not indicate feature parity.
Does Solution Manager stop working after 2027?
SAP describes the end of 2027 as the end of mainstream maintenance for Solution Manager 7.2. Selected functions, including change control management and ITSM, can receive extended maintenance until the end of 2030 for customers who choose extended maintenance for SAP Business Suite 7, and SolMan 7.2 then moves to customer-specific maintenance. SAP KB 3585220 still recommends completing the move to SAP Cloud ALM before 2028.
Can ChaRM change history move to SAP Cloud ALM?
SAP states that transferring Change Control Management data from Solution Manager to Cloud ALM is not planned. SAP recommends closing open change cycles in Solution Manager before activating Deployment Management in Cloud ALM. Solution documentation can move with Selective Data Transfer, so plan separately where historical change documents stay available for audit.
Can ServiceNow replace SAP Solution Manager?
ServiceNow can cover the IT service management part, which SAP scopes out of Cloud ALM and assigns to third-party ITSM. SAP Cloud ALM remains SAP's stated path for implementation, change enablement and deployment orchestration. Cloud ALM's ServiceNow ticket integration forwards events as incidents, so the two systems work side by side.
Can SAP Cloud ALM deploy CTS+ transports?
SAP's Cloud ALM documentation states that CTS+ is not supported. Cloud ALM deploys through CTS for ABAP systems, SAP Cloud Transport Management service for supported content and the Adaptation Transport Organizer for SAP S/4HANA Cloud. Solution Manager handles non-ABAP changes through CTS+ in Change Control Management, so those objects need a separate route after the move.
Does Cloud ALM have cross-system object lock or urgent changes?
SAP's 2024 ALM Summit roadmap listed cross-system object lock and a New Feature Type for Fixes as planned mid-term, defined as by end of 2025. No SAP page reviewed for this guide confirms delivery of either. Retrofit, from the same roadmap, has shipped and has its own SAP KBA 3768016. Downgrade Protection and the Cross-Reference Check run against production systems.
What replaces SAP Solution Manager?
SAP names SAP Cloud ALM as the successor, and SAP's Solution Manager page recommends all customers transition to Cloud ALM before the end of 2027. SAP's transition guidance adds SAP Focused Run for advanced operations use cases. IT service management sits outside Cloud ALM's scope and can be provided by a third-party ITSM tool.
Is the November 2026 Basic Auth deadline accurate?
It applies to one SuccessFactors item only. SAP moved the SuccessFactors API Basic Auth deletion to 12 November 2027 and lists 13 November 2026 for Basic Auth for UI login and third-party corporate IdP direct integration. ServiceNow's SuccessFactors spoke documentation still says November 2026. No SAP or ServiceNow source applies the date to change or transport integrations.
Echelon works across ServiceNow and SAP, and its expansion from ServiceNow to SAP keeps output in sub-production behind a developer approval gate. The IT Process Graph maps how a business runs across its systems, such as ServiceNow and SAP S/4HANA, so a planned change could be checked against every step it touches.
To see how Echelon works across your ServiceNow and SAP estate, book a scoping call.
