Video Summary:
The video explains how to design a transition plan from SAP Solution Manager to SAP Cloud ALM. It gives a line-by-line functional comparison, highlights where functionality is equivalent, different, missing, or evolving, and identifies tools and processes to plan and execute the move (SAP Readiness Check, Selective Data Transfer, ChaRM white paper, SAP Activate). It calls out special cases (custom code management, ITSM, Focused Build, regulated environments, operations data migration, and ALM tools running on Solution Manager) that need specific planning and points viewers to the Transition Center and roadmap for details.
Key Points:
- There is no one-to-one functional parity: many Solution Manager features exist in Cloud ALM but some are missing or different (e.g., custom code management not yet in Cloud ALM, IT Service Management not provided, data volume management out of scope).
- Start with the SAP Readiness Check to analyze your actual Solution Manager usage and identify what must be migrated, retained, or reimplemented; use Selective Data Transfer (SDT) to move solution documentation where needed.
- Change Control (ChaRM) and operations require careful planning — ChaRM workflows and change documents are not migrated (follow the ChaRM white paper for migration scenarios), and most operations use cases must be re-established in Cloud ALM (no bulk operations data migration).
- Use the SAP Activate methodology and the Cloud ALM roadmap to structure the transition project (you can import Activate into Cloud ALM to manage the transition); also plan for special cases like Focused Build support, regulated environments, sovereign cloud timelines, and relocating ALM tools (SLD, License Admin Workbench, etc.).