Context: What Does RISE with SAP Mean in Practice?
RISE with SAP is positioned as a bundled offering of software, infrastructure, and services designed to accelerate cloud adoption.
In reality, it quickly becomes clear that RISE is less a standalone product and more an operating and commercial model that introduces technical, organizational, and functional change.
The key question is therefore not only how to execute a successful RISE with SAP migration, but more importantly: how will operations evolve afterward?
Cloud Strategy: Moving Beyond Traditional ERP
Many RISE with SAP projects are part of a broader SAP cloud transformation strategy.
Typical target scenarios include:
- Moving away from monolithic ERP systems
- Building modular, integrated services
- Increasing adoption of platforms such as SAP BTP
- Enabling faster adaptation to changing business requirements
At its core, this is about designing an architecture that supports change and accelerates innovation.
Data and AI as the Foundation of Modern Architectures
Alongside the technical transition, data strategy becomes increasingly critical. The combination of ERP, SAP BTP integration, and data platforms enables new capabilities:
- Leveraging data for better decision-making
- Applying AI and automation
- Integrating tools for analytics and process mining
A key principle: the data strategy must align with business strategy, not the other way around.
Organizational and IT Transformation
The introduction of RISE with SAP impacts not only systems but also roles and responsibilities.
Typical developments include:
- Stronger collaboration between business and IT
- Product-oriented teams replacing traditional silos
- Increased ownership within business units
- Greater importance of architecture and integration
New roles often emerge, such as:
- BTP Administrator
- Cloud Service Manager
- IT Architect / Integration Lead
- Compliance and Security Manager
In mid-sized organizations, these responsibilities are often absorbed by existing roles rather than newly created positions.
Understanding the Commercial Model: FUE and Scope
A core component of RISE with SAP is its commercial structure.
Full Usage Equivalents (FUE)
The traditional named user model is replaced by Full Usage Equivalents (FUE).
Key considerations:
- Billing is based on authorizations, not actual usage
- Incorrect role assignments can significantly increase costs
- Different user types are converted into FUE values
Examples:
- 1 Advanced User = 1.0 FUE
- 5 Core Users = 1.0 FUE
- 30 Self-Service Users = 1.0 FUE
This makes a detailed analysis of roles and authorization concepts essential.
As SAP landscapes continue to evolve technologically—driven by innovations such as RISE with SAP, the Business Technology Platform, and AI-based extensions—transparency around license types and usage is often lost. The result: over-licensing, under-licensing, and an increasing risk of falling into the next cost trap. This article explains how to avoid unnecessary expenses and regain control of your SAP licenses.
What Is Included in the RISE with SAP Contract?
RISE is based on a Cloud Service Agreement and bundles multiple components:
- SAP S/4HANA Cloud (public or private edition)
- Infrastructure via SAP or hyperscalers
- Basic operations and technical support
- Optional services such as SAP BTP and additional extensions
A clear understanding of responsibilities is critical, as not all tasks are automatically handled by SAP.
Common Challenges in Real-World Projects
Across projects, several recurring challenges emerge:
- High coordination effort among stakeholders
- Unclear operational responsibilities
- Ticket-based support becoming a bottleneck
- High migration costs without process optimization
- Additional demand for internal expertise
A common misconception is that the “all-in-one” promise eliminates the need to build internal capabilities. In reality, this remains essential.
Success Factors for RISE with SAP Projects
Based on practical SAP migration experience, the following success factors are critical:
Define a clear target architecture
Focus not only on migration but on the future operating model
Review processes before migration
A pure lift-and-shift approach rarely delivers real value
Clearly define responsibilities and decision structures
As SAP services are largely standardized, complementary expertise becomes a key differentiator
Key Takeaways for Organizations
- Focus not only on migration, but on long-term operations
- Carefully review contract scope and responsibilities
- Analyze the FUE model and authorizations early
- Treat SAP cloud transformation as a company-wide initiative
- Actively plan and manage change
Conclusion
RISE with SAP provides a structured pathway to the cloud and enables access to modern technologies and standardized operating models. At the same time, it requires a strong understanding of internal processes, clearly defined responsibilities, and sufficient in-house expertise.
RISE with SAP is not a turnkey solution, but a powerful framework that can deliver real value when implemented correctly.
Support on Your Cloud Journey
Implementing RISE with SAP involves both technical and organizational transformation. Structured preparation and a clearly defined target vision are critical to success.
We support organizations in planning, executing, and operating their SAP landscapes, helping align individual business requirements with the capabilities of RISE with SAP.