Skip to content

SAP Solution Manager to SAP Cloud ALM: A Practical BASIS Transition Roadmap for 2026–2027

Analytics dashboard concept representing IT operations monitoring

Published: 15 November 2026 | SAP BASIS | SAP Solution Manager | SAP Cloud ALM

If your SAP landscape still depends on SAP Solution Manager, the move to SAP Cloud ALM deserves a place on your BASIS roadmap now—not in the final months before the maintenance milestone. SAP states that mainstream maintenance for SAP Solution Manager ends on 31 December 2027 and recommends completing the transition to SAP Cloud ALM before that date. The right response is not to rush into a tool replacement. It is to understand what your organization uses today, decide what must continue working, and plan the transition capability by capability.

Analytics dashboard concept representing IT operations monitoring
Illustrative IT operations dashboard image. This is not a screenshot of SAP Cloud ALM. Photo by Luke Chesser via Unsplash.

For SAP BASIS administrators, this is a practical infrastructure and operations project. Monitoring, alerting, job oversight, interface visibility, change processes, documentation, user access and support responsibilities all need to be considered. This article explains how to begin in a structured way, using SAP’s published transition guidance and learning resources.

Why SAP Cloud ALM is on the BASIS agenda

SAP describes Cloud ALM as its strategic, next-generation application lifecycle management platform for SAP Business Suite and hybrid landscapes. SAP positions it as a cloud-native service with lower operational maintenance overhead than running a traditional on-premises ALM platform. SAP also says that SAP Focused Run can be added alongside Cloud ALM when customers have extensive on-premises or advanced monitoring requirements.

The important point for a BASIS team is that this is not simply a change of dashboard. An ALM platform supports the way an organization observes, operates and manages its SAP services. A transition therefore affects operational ownership, monitoring coverage, escalation paths, service reporting and day-to-day working procedures.

Official timeline: SAP’s Transition to SAP Cloud ALM guidance.

SAP Solution Manager and SAP Cloud ALM: think in capabilities

A common planning mistake is to assume that every Solution Manager function will be moved by copying a configuration or exporting a database. That is not a safe assumption. The transition needs to be assessed by use case. Some capabilities have an equivalent or recommended approach in Cloud ALM; some require redesign, a selective data transfer, a different operating procedure or a complementary product. The exact answer depends on what your organization has implemented and the current SAP guidance for that scenario.

Area to assessQuestions for the BASIS / operations team
System monitoringWhich ABAP, Java, HANA, operating system and cloud systems are monitored today? What alerts are business-critical?
Integration monitoringWhich interfaces, message flows, queues and middleware paths must remain visible?
Job and automation monitoringWhich background jobs and automation tasks have business deadlines or escalation rules?
Exception monitoringWhich exceptions are tracked centrally, and who owns first response and resolution?
Business process monitoringWhich business KPIs or process steps are monitored, and who validates the thresholds?
Change and documentation processesAre ChaRM, ITSM, documentation, test management or custom workflows in use? What is the approved target approach?
Security and configuration analysisWhich compliance checks, configuration baselines and audit evidence must continue?

Use this as a discovery checklist, not as a claim that every listed capability transfers in the same way. SAP’s official transition material provides scenario-specific recommendations and points customers to the readiness check and transition roadmap.

What should a BASIS administrator do first?

1. Discover the current Solution Manager footprint

Start with facts rather than assumptions. Record the Solution Manager release and relevant support package level, connected managed systems, agents and diagnostics components, monitoring templates, technical users, RFC destinations, certificates, interfaces and integrations. Also identify which teams use the platform and for what purpose.

Do not limit the inventory to infrastructure. Ask application support, security, service desk, development, testing and business process owners which alerts, reports and workflows they rely on. A monitoring scenario that appears unused in a technical inventory may still support an important business escalation.

2. Run SAP Readiness Check for SAP Cloud ALM

SAP specifically recommends using the SAP Readiness Check for SAP Cloud ALM to analyze current Solution Manager usage and provide recommendations for equivalent functionality in Cloud ALM. Treat the output as a starting point for a workshop, not as an automatically approved migration design.

Review the results with the owners of each capability. Confirm which functions are actively used, which are obsolete, which need redesign and which need a separate decision. Record gaps and assumptions explicitly.

3. Classify the landscape and operational requirements

Separate cloud services, S/4HANA systems, older SAP NetWeaver or ECC systems, non-SAP applications, and critical integration paths. Note system count, locations, business criticality, maintenance windows, network restrictions, data residency or regulatory constraints, and support coverage.

This step helps determine whether Cloud ALM alone fits the requirements or whether SAP Focused Run should also be evaluated. SAP’s transition guidance describes Focused Run as an option for extensive on-premises or advanced monitoring needs. Do not choose a product based only on system count; validate the actual monitoring scenarios and product support requirements.

4. Design the target operating model before configuration

For each monitoring or ALM scenario, agree on the target tool, owner, alert severity, notification route, response-time expectation and evidence required for closure. Decide who maintains integrations, technical users, certificates, destinations and onboarding when the landscape changes.

For example, an alert that indicates a failed critical background job should have a clear owner and escalation path. A dashboard without an agreed response process is not an operational control.

5. Build a pilot with representative systems

Select a small but meaningful pilot: perhaps one non-production ABAP system, one HANA database scenario and a representative interface or job-monitoring use case. Validate connectivity, data collection, alert quality, access roles, notification behavior and operational handoffs.

Test both normal and failure conditions. Confirm that expected alerts are generated, that noisy or duplicate alerts are manageable, and that the responsible team can investigate the event with the information available. Document what is not covered before expanding the rollout.

6. Plan selective transition and cutover

Do not assume that historical monitoring data, configuration, ITSM records or custom workflows will all move automatically. SAP’s learning path includes separate topics for selective data transfer and Change Request Management transition, which is a useful reminder that these are distinct workstreams. For each one, verify the supported method, prerequisites and limitations in current SAP documentation.

Keep the old and new operating procedures clear during coexistence. Define which platform is authoritative for each scenario, how long parallel monitoring is needed, how alerts are reconciled and who approves decommissioning. Avoid running two tools indefinitely without clear ownership.

A practical transition plan you can adapt

PhaseDeliverableSuggested owner
DiscoverSolution Manager usage inventory, connected systems and stakeholder listBASIS lead
AssessReadiness Check review, capability mapping and gap registerBASIS + ALM architect
DesignTarget architecture, monitoring ownership, security and access modelArchitecture + security
PilotValidated onboarding, monitoring scenarios, alerts and runbooksOperations team
TransitionScenario-by-scenario rollout, data/workflow transition and cutover recordsProject team + process owners
StabilizeOperational acceptance, KPI review, training and decommissioning decisionService owner

Use dates and durations that match your landscape. A small environment with limited Solution Manager usage will have a different plan from a large hybrid estate with many integrations, custom workflows and audit requirements.

What is changing in operations monitoring?

SAP’s 2026 communications describe continued investment in Cloud ALM, including migration and modernization assistants and a broader role in operational observability. SAP’s learning content describes seven integrated monitoring use cases, including real and synthetic user monitoring, integration and exception monitoring, health and job/automation monitoring, business process monitoring, and configuration and security analysis. It also discusses an AI-oriented direction for detection and guided resolution.

For administrators, the practical takeaway is to build strong operational fundamentals first: reliable system onboarding, meaningful thresholds, clear alert ownership, good runbooks and accurate configuration data. AI-assisted operations are only useful when the underlying monitoring signals and operational processes are trustworthy.

Server infrastructure representing enterprise SAP system operations
Illustrative server infrastructure image. Photo by Taylor Vick via Unsplash.

Common mistakes to avoid

  • Waiting until 2027: discovery, stakeholder alignment and redesign can take longer than the technical onboarding itself.
  • Assuming a one-to-one replacement: map business and technical capabilities individually; validate the target approach with SAP guidance.
  • Ignoring non-BASIS stakeholders: service desk, security, application and business teams may depend on Solution Manager workflows.
  • Moving everything without cleanup: retire unused alerts and stale integrations where approved instead of reproducing unnecessary complexity.
  • Skipping access and security design: review technical users, roles, certificates, connectivity and audit needs before broad onboarding.
  • Decommissioning too early: keep the legacy process available until the replacement is tested, accepted and formally approved.

Useful official learning and planning resources

How this affects your SAP BASIS career

For working BASIS administrators and learners, this transition is a good opportunity to strengthen skills beyond traditional system administration. Modern SAP operations increasingly require landscape discovery, connectivity and certificate management, monitoring design, alert analysis, integration awareness, security coordination and structured change management.

Hands-on practice should include understanding the purpose of Solution Manager and Cloud ALM, mapping a managed system, identifying monitoring requirements, tracing an alert to its technical cause and documenting the operational response. Do not claim production experience from a demo tenant; describe lab exercises accurately and explain what was actually tested.

To strengthen your SAP technical foundation, explore RHSoftTech’s SAP BASIS online training. Administrators working with HANA-based landscapes may also find the SAP HANA Administration training relevant.

Frequently asked questions

When does SAP Solution Manager mainstream maintenance end?

SAP states that mainstream maintenance ends on 31 December 2027. SAP’s transition page recommends completing the move to SAP Cloud ALM before that date. Check the relevant SAP notes and your contract for maintenance options and customer-specific details.

Does every customer need SAP Focused Run as well as SAP Cloud ALM?

No. SAP describes Focused Run as an option for extensive on-premises or advanced monitoring requirements. Evaluate the scenarios and supported products in your own landscape before deciding.

Can all Solution Manager data and workflows be migrated automatically?

Do not assume that. SAP provides separate transition guidance for different capabilities, including selective data transfer and Change Request Management. Verify the supported approach for each workstream.

What is the first step for a BASIS team?

Inventory current Solution Manager usage and run SAP Readiness Check for SAP Cloud ALM. Use the results to create a capability map and involve the teams that own the operational processes.

Is SAP Cloud ALM only for S/4HANA systems?

SAP positions Cloud ALM for SAP Business Suite and hybrid landscapes. Confirm the support and onboarding requirements for each product and system type in your environment using current SAP documentation.

Final thought

The Solution Manager maintenance milestone is a useful deadline, but a successful transition is about more than meeting a date. It is about ensuring that the people responsible for SAP services can still see issues, understand their impact and respond in a controlled way. Start with discovery, use SAP’s readiness guidance, pilot the important scenarios and transition one capability at a time.

Editorial note: This article is an independent educational guide based on publicly available SAP materials. Product capabilities and transition recommendations can evolve; verify current requirements, licensing, supported scenarios and implementation steps with SAP before making project decisions. RHSoftTech is not claiming to be an SAP-authorized migration provider.