Last week, IT-Conductor hosted a powerful and practical webinar focused on helping SAP customers prepare for the shift from SAP Solution Manager (SolMan) to SAP Cloud ALM. Led by our Co-Founder and CEO, Linh Nguyen, the session was packed with technical insights, roadmap updates, and real-world migration lessons.
If you missed it or want a quick summary here’s what we covered:
SAP Solution Manager has served many customers well in on-premises landscapes, but it’s not built for cloud-first, hybrid environments. With mainstream support ending in 2027 and extended support until 2030, the time to plan your transition is now.
Cloud ALM offers a modern, cloud-native alternative aligned with SAP’s future but it’s not a 1:1 replacement (yet).
Cloud ALM is great for:
Health and business process monitoring
Lightweight project management
Task and test tracking
But limitations remain:
No full ChaRM functionality
No cross-system orchestration or retrofit
Requires manual integration with ITSM tools
Still evolving in areas like extensibility and NetWeaver Java monitoring
Customers with hybrid environments currently leveraging Solman is recommended to continue with Solman and Focus Run (commercial costs involved)
Hybrid and legacy system gaps
Missing advanced ChaRM features
Limited out-of-the-box ITSM integration
No-code extensibility and still evolving roadmap
Siloed visibility across tools
Limited job chain orchestration and deep diagnostics
Lack of customization capabilities
SAP offers 8 GB of monitoring storage per Cloud ALM tenant — free. We shared data from real-world customers:
Small landscapes may take 2+ years to hit the limit
Large, high-traffic environments can exceed it in under 12 months
Unclear how much each incremental 8 GB usage will cost but others have shared a figure of around USD 20,000 annually
To avoid surprises: track usage early and consider hybrid support.
As Cloud ALM evolves, IT-Conductor helps bridge the gap with:
Legacy and hybrid system support
Advanced orchestration and automation, such as system refresh, and Infrastructure as Code automation
Event-driven monitoring and self-healing
Job chain visibility and runtime analytics
Transport automation to complement missing ChaRM features
We walked through what's coming in 2024–2025:
Mass event configuration and AI-assisted alert resolution
Business process KPI customization (ABAP & non-ABAP)
Enhanced change management (retrofit, downgrade protection)
Test case migration APIs
Expanded integration & extensibility options
Set clear ALM goals before you configure tools
Don’t assume Cloud ALM has feature parity with SolMan
Budget for integrations and external tools (e.g., OpenTelemetry, ITSM)
Retain SolMan (read-only) during migration
Start small, validate, and then scale Cloud ALM adoption
Thank you to everyone who attended the live session. If you missed it, don’t worry, the recording and whitepaper are available below