By Miguel Pacheco, SAP Principal Engineer at Foulk Consulting
If you’ve managed SAP landscapes over the last two decades, SAP Solution Manager (SolMan) has almost certainly been the operational nervous system of your enterprise. It logged your incidents, orchestrated change requests through ChaRM, housed your business process documentation, and ran your testing cycles.
But the clock is officially ticking. Mainstream maintenance for SolMan 7.2 ends at the close of 2027. While 2027 might feel like a distant milestone on a roadmap, postponing your transition leaves you exposed to ballooning maintenance costs, talent scarcity, and rushed, high-risk operational cutovers.
In my previous post, I broke down the clear operational wins SAP Cloud ALM delivers over SolMan: zero infrastructure footprint, automated updates, faster time-to-value, and a streamlined user experience. But understanding why to migrate is only half the battle. The hardest part for most enterprise IT leads is figuring out how to decommission SolMan smoothly without disrupting day-to-day business operations.
Migration isn’t a single “big bang” switch. It requires a pragmatic, phased roadmap.
Mapping the Functional Shift
Before shutting down servers, you must understand where SolMan’s core capabilities land in the modern SAP ecosystem. SAP Cloud ALM is designed to be lighter and faster, meaning it doesn’t try to replicate every legacy SolMan customization. Instead, it streamlines processes or integrates with best-in-breed partners:
| Legacy SolMan Feature | Modern Destination | Primary Benefit |
| Solution Documentation (SolDoc) | SAP Cloud ALM Process Management | Lightweight, BPMN-compliant modeling with zero transport overhead |
| Change Request Management (ChaRM) | Cloud ALM Change & Deployment Management | Standardized release transport management across hybrid landscapes |
| SolMan Test Suite | Cloud ALM Test Management + Tricentis | Built-in manual testing with seamless automated testing integration |
| Business Process Monitoring (BPMon) | Cloud ALM Business Process Monitoring | Cloud-native telemetry with pre-built KPIs and zero local agents |
| IT Service Management (ITSM) | Third-Party / Enterprise ITSM Solutions via Open APIs | Clean API integrations with enterprise ITSM platforms |
The 4-Phase SolMan Sunset Roadmap
To minimize risk and ensure business continuity, we recommend a phased transition that builds operational confidence before legacy systems are turned off.
1. Phase 1: Readiness Check:
Catalog every SolMan module currently in active use and identify custom ChaRM workflows or legacy test scripts. Decide which functions transition directly to Cloud ALM, which belong in external ITSM platforms, and which legacy artifacts can be retired completely.
2. Phase 2: Project Setup:
Provision your SAP Cloud ALM tenant (included with your SAP Enterprise Support agreement). Establish cloud connectors to your SAP S/4HANA, BTP, and cloud engines, and integrate test automation tooling (such as Tricentis Test Automation for SAP).
3. Phase 3: Project execution:
Migrate capabilities in waves to reduce operational friction:
- Wave 1: Process Documentation & Business Process Monitoring (low-risk, high visibility).
- Wave 2: Test Management & Defect Tracking ahead of your next major upgrade cycle.
- Wave 3: Change & Deployment Management (transitioning off ChaRM once release teams are trained).
4. Phase 4: Decommissioning & Extension:
Define audit and regulatory requirements for legacy ChaRM transport logs and execution history. Archive required data into accessible cloud tables, revoke SolMan write access, power down host servers, and reclaim infrastructure costs.
Expand the usage of Cloud ALM to additional scenarios and systems once the core is stable.
Three Pitfalls to Avoid During Migration
Having guided numerous organizations through SAP ALM shifts, we consistently see three common traps:
- Trying to “Lift and Shift” Custom ChaRM Workflows: SolMan allowed endless ABAP customization, often leading to over-engineered approval gates. Cloud ALM encourages standardized, agile release flows. Take this opportunity to simplify your process rather than forcing legacy complexity into a modern cloud tool.
- Neglecting Historical Audit Data: Compliance teams often freak out when SolMan decommissioning is mentioned. You don’t need to keep SolMan running forever just for audit history; extract change logs and sign-off records into read-only storage early in the project.
- Underestimating Change Management for IT Teams: Your Basis, development, and QA teams have muscle memory built around SolMan’s interface. Training them on Cloud ALM’s task-driven dashboards early prevents friction during cutover waves.
Moving Forward with Foulk Consulting
Decommissioning SolMan doesn’t have to feel like jumping off a cliff. With a clear mapping strategy and a structured, phased rollout, you can transition your application lifecycle management into a faster, cleaner cloud environment long before support timelines force your hand.
At Foulk Consulting, we specialize in helping SAP enterprises navigate ALM transformations, test automation strategies, and platform modernization with minimal risk to the business.
Ready to assess your SolMan footprint and build a tailored Cloud ALM migration roadmap? Contact the Foulk Consulting team today to schedule an ALM discovery session.
