SAP RISE with SAP

The RISE with SAP model may be unsuitable when:

1. An organization requires high control of Basis and infrastructure operations and cannot accept SAP-managed operational constraints (a common concern among platform operations teams).
2. Expectations for a single simplified contractual relationship are that all complexity will be removed; evidence suggests implementations can still involve multiple parties and operational interfaces requiring coordination.
3. Budget sensitivity over a long horizon is critical: organizations that cannot accommodate subscription escalation, tiering effects, or packaging changes may find alternatives with more predictable cost structures preferable.
4. A clear and low-friction exit strategy is required: some community and practitioner commentary indicates contractual and operational exit can be complex once a RISE deployment is operationalized.

• Consolidated commercial construct: a subscription that combines ERP software, infrastructure, and certain platform services under a single contracting model.
• Standardized transformation methodology and toolchain: SAP provides a framework and tooling intended to support migration and process standardization.
• Alignment with SAP product roadmap: SAP directs many innovation efforts (including cloud-focused capabilities) toward subscription and cloud deployment models.

• TrustRadius contains reviews for “SAP S/4HANA Cloud” that sometimes reference RISE with SAP.
  • Example: TrustRadius product review page for SAP S/4HANA Cloud
• Gartner Peer Insights content is often paywalled or requires account access; this report references market research commentary but does not reproduce paywalled peer reviews.
  • Gartner research landing page (analyst research that may require account access)
• G2 search results for “Rise reviews” may surface a different product named “Rise” (a naming collision), reducing confidence that listed G2 entries refer to RISE with SAP.
  • Example of likely-not-SAP listing: G2 product listing for a non-SAP "Rise" product

From TrustRadius and similar reviewer comments:

• Reported simplification of some processes, analytical support, and observed improvements in implementation speed in specific deployments. One reviewer noted an improved user experience and an expectation of lower TCO over a limited horizon.
  • Source: TrustRadius product review
• Some organizations value the consolidated contracting and reduced need to separately contract infrastructure and certain platform elements.
• Some teams find SAP-managed operations helpful when internal Basis/infra resources are limited.

Community discussions and some analyst summaries identify common complaints:

• Support quality and delays: reports of reduced support responsiveness and extended resolution times.
  • Example thread: community discussion (Reddit)
• Loss of control and access constraints for Basis teams: limited tooling access and reduced operational visibility compared with on-prem deployments.
  • Example thread: community discussion (Reddit)
• Pricing surprises and add-ons: reports that custom integrations, storage growth, and non-standard needs can increase costs beyond initial quotes.
  • Example thread: community discussion (Reddit)
• Contract exit complexity: community commentary suggesting that contractual exit can be complex.
  • Example thread: community discussion (Reddit)

Vendor-published case studies and product pages sometimes cite availability and performance metrics (for example, a vendor story referencing a near-100% availability claim). These are vendor-provided examples; procurement teams should obtain:

• Detailed SLA definitions, including what counts as downtime and exclusions for maintenance/upgrades.
• Independent post-implementation metrics if available.
• Baseline comparisons and measurement methodology used for reported outcomes.

Practitioner forums include anecdotes of:

• Post-migration dissatisfaction with support and operational processes.
• Adding application server resources to resolve operational issues, sometimes after negotiations.
• Retaining on-prem components for functionality or integrations that were not supported or preferred under certain RISE configurations.

These community accounts are anecdotal and not independently verified but recur in practitioner discussions.

RISE with SAP is SAP’s commercial and delivery model for migrating existing SAP ERP customers (notably SAP ECC and SAP S/4HANA on-prem) to SAP’s cloud ERP operating model—commonly centered on SAP S/4HANA Cloud (private edition for many large enterprises, and public edition for more standardized needs). The offering packages software, cloud infrastructure/hosting, and transformation services under a consolidated contract and methodology.

Observed buyer interpretations of RISE include:

• A packaging and contracting model for SAP S/4HANA Cloud combined with managed services (often SAP-managed Basis/infra) and bundled tools (process mining/architecture/integration tooling varies by package and time period).
• A governance approach intended to provide a consolidated contractual counterparty that shifts operational responsibility to SAP and partners, with trade-offs in control and flexibility.

Vendor positioning: SAP describes RISE with SAP as a structured transformation program toward its cloud ERP offerings, supported by methodology, tools, and advisory services, emphasizing principles that reduce core customization. SAP marketing pages also cite improvement percentages; those claims should be interpreted as vendor-provided outcomes unless accompanied by a published methodology.

Key official pages include the vendor’s “What is RISE with SAP?” overview and the RISE product page (official vendor documentation and product overview pages).

• Primary target: Existing SAP ERP customers facing modernization pressure (ECC to S/4HANA, on-prem to cloud operating model), typically mid-market through very large enterprises.
• Positioning: A subscription model that bundles ERP, infrastructure, services, and a partner ecosystem with SAP acting as the coordinating party. Early launch coverage characterized this as a subscription service that aggregates product and professional services.
  • Press: early launch coverage appeared in major technology press and industry outlets.