SAP ALM Migration Readiness
How complex is your Solution Manager to Cloud ALM transition, what does it involve, and do you have enough time before 2027? Six to ten questions depending on your footprint, about 4 minutes.
Which version of SAP Solution Manager are you running?
SolMan 7.1 or earlier
SolMan 7.2
Not sure
Which Solution Manager capabilities does your organization actively use?
Change Control (ChaRM)
Focused Build / Focused Insights
IT Service Management
Test Suite
Monitoring (system, integration, or BPMon)
Solution Documentation
Custom Code Management
How much have you customized your change management workflows?
Standard — SAP’s defaults with little or no modification
Moderate — custom statuses, approval steps, or authorization rules
Heavy — custom UI extensions, BW dashboards, Z-reports, or heavily modified workflows
How many SAP systems does your Solution Manager manage?
Small — 1 to 5 systems
Medium — 6 to 15 systems
Large — 16 or more systems
Do you run separate development landscapes for innovation and maintenance?
Yes — dual landscape (separate tracks for new development and corrections)
No — single development landscape
Not sure
Does your Solution Manager connect to any of these tools?
Jira
Azure DevOps
ServiceNow (for change or deployment)
Other third-party ALM, CI/CD, or project management tools
None — Solution Manager operates standalone
How dependent are your day-to-day deployments on your change management process?
Low — we could work around it for weeks if needed
High — deployments would stall within days
Critical — production gates depend on it with no manual bypass
Does your change management process serve as a regulatory or audit control?
No — not applicable
Partially — auditors reference it but it is not a primary control
Yes — SOX, GxP, FDA, or another framework formally depends on it
Do you have requirements to preserve historical change records after migrating?
No — a clean cutover is acceptable
We’d like to retain history but it is not mandated
Yes — regulatory, legal, or contractual requirements mandate it
Are you running an S/4HANA migration in parallel?
Yes — in flight or starting within 12 months
Planned but not yet started
No S/4HANA migration planned
Complexity Profile
This assessment is based on general benchmarks and the profile you described. It is not a substitute for a landscape-specific evaluation.