Abstract, glowing SAP transformation route rising towards cloud layers

07SAP S/4HANA CLOUD PRIVATE EDITION

RISE with SAP

We build a clear RISE with SAP route that takes your SAP ERP investment to SAP S/4HANA Cloud Private Edition (new name: SAP Cloud ERP Private): clean core, a controlled transition and continuous improvement.

OUTCOMES FIRST

Business outcomes

  1. 01

    A value-driven route

    A modernisation plan that orders the technical backlog by business outcome, risk and priority.

  2. 02

    Clean-core control

    We keep the differentiation you need and reduce the technical debt that makes upgrades harder.

  3. 03

    Continuous transformation

    Measurement, improvement and regular adoption of new SAP capabilities after go-live.

OVERVIEW

Scope and approach

Moving to RISE with SAP changes the hosting model, and with it business processes, custom code, data, integrations and the operating model; these topics are handled together in one roadmap.

We run the transition through the SAP Activate phases: we measure today's process with SAP Signavio, set up the project and production monitoring in SAP Cloud ALM, and close every phase with a quality gate.

The roadmap does not end at go-live: upgrades, new SAP capabilities and process measurement are tied to a regular improvement rhythm.

FOCUS

What do we solve?

  1. An unclear cloud target

    We clarify the current state, target operations and transformation waves in one roadmap.

  2. Custom code dependency

    Usage and business value analysis separates the developments to remove, redesign or keep.

  3. Fragmented responsibility

    We bring business, application, data, integration, infrastructure and security teams together under shared governance.

WHAT WE OFFER

Capabilities and scope

  1. Transformation assessment

    Process, system, data, code, integration and organisational readiness.

  2. SAP S/4HANA Cloud Private Edition

    Designing the target architecture, operating model and transition principles.

  3. Clean core

    Return to standard, extension strategy and custom code governance.

  4. Data modernisation

    Clean-up, archiving, migration, reconciliation and data ownership.

  5. Integration

    Hybrid architecture and a roadmap for moving to Integration Suite.

  6. Value tracking

    Waves, success criteria, an improvement backlog and a management view.

Four services for SAP Signavio and SAP Cloud ALM

In a RISE project we set up measurement and the target process in Signavio, and the project record and production monitoring in Cloud ALM. The same team runs the move to Cloud ALM for organisations that use Solution Manager.

  • Process measurement and modelling with SAP Signavio

    We run the baseline measurement with the discovery edition and the detailed analysis with Process Intelligence, model the target process in BPMN and synchronise it to Cloud ALM.

    • Data extraction and the KVKK pseudonymisation decision
    • Variant, delay and rework analysis
    • Target process through an approval flow
    • Discover
    • Explore
    • Run
  • SAP Cloud ALM project setup

    We open the project with the Activate roadmap for the transition route and set up process scope, the requirement and feature flow, and the test and deployment plan.

    • Tracking Readiness Check findings
    • Quality gate questionnaires
    • Test automation with Tricentis
    • Prepare
    • Explore
    • Realize
  • Moving from Solution Manager to Cloud ALM

    We list the Solution Manager scenarios that are really in use, map their Cloud ALM counterparts and run the move in stages.

    • Readiness Check for SAP Cloud ALM
    • Moving documentation and Test Suite
    • Decisions on ChaRM and IT service management
    • Run
  • Cloud ALM monitoring and AMS

    We set up monitoring use cases and alert rules in the customer's own Cloud ALM tenant; alerts reach the Negzel AMS team and are resolved by SLA priority.

    • Business process, integration and job monitoring
    • Routing to email and ServiceNow
    • Monitoring and alerting 24/7
    • Deploy
    • Run

INSIDE THE CONTRACT

What is inside a RISE with SAP contract?

RISE with SAP is not a product on its own but a subscription offering: ERP software, hosting, technical operation of the infrastructure and a set of cloud services come under one contract. SAP S/4HANA Cloud Private Edition (SAP Cloud ERP Private) sits at the centre. It is single-tenant, so classic ABAP developments and industry-specific processes can be kept.

Package and scope vary by contract. The package renewed in April 2025 lists items such as SAP LeanIX and SAP Signavio capabilities, SAP Build, SAP HANA Cloud, SAP Master Data Governance and SAP Business Network Supplier Portal alongside the ERP; we read what is included from the contract's product list. SAP Cloud ALM is not a separate item; it comes with Enterprise Support, cloud editions. New releases do not arrive on their own in the private edition: the customer can request one upgrade a year and SAP performs the technical upgrade, while planning, preparation and testing stay with the customer or a partner.

For large and complex systems that must stay on ECC beyond 2030, SAP has a separate offering: SAP ERP, private edition, transition option. It is not a maintenance extension but a time-bound subscription for 2031-2033, combining business continuity services such as legal changes, security patches and bug fixes with services for the move to RISE with SAP. The prerequisites are demanding: the system must be moved to SAP ERP, private edition on SAP HANA before 31 December 2030, be at least 2 TB in size and come with the max success plan.

Layers of the contract

Package contents vary by contract; what is included is read from the product list.

  1. 01

    SAP S/4HANA Cloud Private Edition

    • Single-tenant ERP
    • Classic ABAP development possible
    • Customer plans upgrade timing
  2. 02

    Platform, process and network

    • SAP BTP: extension and integration
    • SAP Signavio: process measurement
    • SAP Business Network: trading partners
  3. 03

    Infrastructure

    • An SAP data centre, a hyperscaler or a customer data centre; technical operations with SAP
  • The customer chooses the infrastructure: an SAP data centre, AWS, Microsoft Azure, Google Cloud or IBM Power Virtual Server; Alibaba Cloud in China. Sovereign cloud and customer data centre options exist as well.
  • Brownfield, greenfield and selective transitions all lead to SAP S/4HANA Cloud Private Edition (SAP Cloud ERP Private). The RISE contract does not decide the route; the route is chosen by measuring the current system.

SAP ACTIVATE

A RISE with SAP transition in six phases

SAP Activate is SAP's six-phase implementation framework: Discover, Prepare, Explore, Realize, Deploy and Run. In RISE with SAP the framework is used inside the RISE with SAP Methodology that SAP announced in January 2024, and SAP S/4HANA Cloud Private Edition has a separate roadmap for each transition route: Greenfield (New Implementation), Brownfield (System Conversion) and Selective (Selective Data Transition).

Each phase closes with a quality gate; some work is prepared in the preceding phase, for example cutover is planned in Realize and executed in Deploy. The RISE with SAP Methodology adds clean core checks to these gates: the first gate is completed in Prepare with SAP's onboarding advisor, the project manager submits the later ones from SAP Cloud ALM, and SAP Enterprise Support returns a clean core report. Clean core is tracked in five dimensions: business processes, extensibility, data, integration and operations.

From Discover to Run

  1. Discover

    Scope and transition route decisionNo gate
    In RISE
    SAP Readiness Check shows what in the current ECC will not work in SAP S/4HANA; SAP Signavio Process Insights, discovery edition provides a free, one-time measurement. Setting up the technical prerequisites for both is a standard SAP service in RISE. The Digital Discovery Assessment and RISE Adoption Plan prepared during the sales cycle are handed over to the implementation team at project start.
    Output
    Transition route decision, scope, value roadmap
    Quality gate
    The predefined phases in Cloud ALM start with Prepare; the first quality gate sits at the end of Prepare.
    Tools
    • SAP Readiness Check
    • SAP Signavio
  2. Prepare

    Plan, team, initial environment and the Cloud ALM projectGate 1
    In RISE
    SAP's onboarding advisor explains the RISE with SAP Methodology, the clean core success plan and how systems are provisioned through SAP for Me. The Cloud ALM project opens with the Activate roadmap for the chosen transition route. In a Brownfield move SAP ECS provides an empty target system and a temporary migration server; in Greenfield the systems arrive later in the project.
    Output
    Cloud ALM project opened with its roadmap, roles, timeline, initial system for Fit-to-Standard
    Quality gate
    Quality Gate 1 (Prepare to Explore): completed with the onboarding advisor and submitted from Cloud ALM.
    Tools
    • SAP Cloud ALM
    • SAP for Me
  3. Explore

    Fit-to-Standard and design sign-offGate + clean core
    In RISE
    In Greenfield all selected processes are shown; in Brownfield only new functionality and processes in the compatibility scope. Requirements are recorded in the Requirements app in Cloud ALM; target processes are modelled in SAP Signavio and transferred to Cloud ALM.
    Output
    Delta requirements, product backlog, design documents, implementation plan
    Quality gate
    Explore to Realize: closes once delta requirements, design documents and the implementation plan are signed off; RISE adds a clean core check.
    Tools
    • SAP Cloud ALM
    • SAP Signavio
  4. Realize

    Sprints, testing and cutover planningGate + clean core
    In RISE
    The solution is configured, extended, integrated and tested in two to four week sprints; cutover is planned in this phase. In Brownfield the technical conversion (SUM) happens here; the standard scope includes two dry runs, one for non-production systems and one for production. Overall planning of the conversion stays with the customer.
    Output
    A release that has passed integration testing and mandatory user acceptance testing
    Quality gate
    Realize to Deploy and a clean core check.
    Tools
    • SAP Cloud ALM
  5. Deploy

    Cutover, go-live and hypercareClean core
    In RISE
    The production environment is set up, business readiness is confirmed and cutover is executed, with several cutover simulations where needed. In Brownfield SAP ECS takes over the converted system, checks it and hands it back; the go/no-go decision for production is the customer's. Hypercare belongs to this phase, after which the project closes.
    Output
    Live system, a defined hypercare period, project closure
    Quality gate
    Clean core check.
    Tools
    • SAP Cloud ALM
  6. Run

    Operations, improvement and upgradesClean core
    In RISE
    Technical operations are a standard SAP service; application management sits with a partner under a separate contract. The customer can request one upgrade a year; upgrades are managed in Cloud ALM with the Upgrade roadmap. Staying in mainstream maintenance requires at least one upgrade every seven years.
    Output
    Monitoring, improvement backlog, upgrade plan
    Quality gate
    Clean core check; Run has its own operations standards.
    Tools
    • SAP Cloud ALM
    • SAP Signavio

Who does what in each phase?

SAP's tasks come from the RISE with SAP roles and responsibilities document; the customer and Negzel rows depend on the contract.

PartyDiscoverPrepareExploreRealizeDeployRun
SAP SignavioFree measurement with the discovery editionProcess Manager and Collaboration Hub tenants arriveTarget process modelled in BPMN and synchronised to Cloud ALMProcess changes as a new revision·The live process is measured again
SAP Cloud ALMReadiness Check analysis can be transferredProject opened with the Activate roadmapRequirements, solution processes, gate questionnaireFeatures, transports, tests and defectsDeployment plan and releaseOperations monitoring, Upgrade roadmap
SAP ECSSets up Readiness Check and discovery edition prerequisitesProvisions systems; in Brownfield an empty target system and a migration server·Technical tasks on service request; two dry runsTakes over the converted system, checks it and hands it backInfrastructure and technical operations; the technical side of upgrades
CustomerTransition route and scope decisionIT contact provisions Cloud ALMProcess experts join the workshopsMandatory user acceptance testing; conversion planningGo/no-go decisionOne upgrade request a year
NegzelSignavio measurement and Readiness Check reviewCloud ALM project setupFit-to-Standard workshops, target process modelConfiguration, development, integration, testingCutover management and hypercareAMS and Cloud ALM monitoring; upgrade testing
Quality gateNoneQuality Gate 1Explore to Realize and clean coreRealize to Deploy and clean coreClean coreClean core

Sample timeline: RISE with SAP transition (12 months)

A sample for a midsize, single-country transition; a firm timeline is discussed once the SAP Readiness Check and the custom code inventory are available.

  1. Preparation and assessmentMonths 1-3 · Discover, Prepare: Readiness Check, infrastructure and route decision
  2. Analysis and target designMonths 3-6 · Explore: Fit-to-Standard, delta list, BTP architecture
  3. Realisation and testingMonths 5-10 · Realize: conversion rehearsals, data, integration, acceptance tests
  4. Go-live and hypercareMonths 10-12 · Deploy (including hypercare), then Run: handover to AMS
  1. Gate 1 (end of Prepare) (Month 3)
  2. End of Explore gate (Month 6)
  3. End of Realize gate (Month 10)

Sample timeline; overlapping bars are preparation work for the next phase. Duration depends on scope and the chosen transition route.

PROCESS EVIDENCE

SAP Signavio: measuring today's processes before changing them

SAP Signavio is SAP's family of process modelling and process mining products. SAP announced its plan to acquire Signavio on 27 January 2021, the day it introduced RISE with SAP. Two of its tools can cover the measurement step of a RISE roadmap: Process Insights works from predefined performance indicators, while Process Intelligence reconstructs the actual process flow from event logs. In new sales the two come as one package with one interface, under the name “Process Insights and Intelligence”.

The baseline measurement is free. SAP Signavio Process Insights, discovery edition became generally available on 15 February 2024 and replaced Process Discovery and Pathfinder. Data is extracted from an SAP ERP or S/4HANA system (SAP Notes 2758146 and 2745851) and the analysis is requested from SAP. The result is a starting picture of where delays, rework and manual intervention concentrate, and the transformation waves are sequenced against it.

Since December 2024, target processes modelled in SAP Signavio Process Manager can be synchronised to SAP Cloud ALM through a standard integration, manually or on approval in Process Governance. They arrive in Cloud ALM as draft solution processes, are published for scoping and feed Fit-to-Standard workshops. We do not assume which Signavio items a contract includes; the tooling plan is built from the product list in the RISE contract itself.

From event log to an approved target process

The measured process becomes a model, the model goes through approval, and the approved model moves to Cloud ALM and to the portal employees read.

Source systems

  • SAP S/4HANA
  • SAP ECC
  • Non-SAP systems
  1. MeasureProcess Insights and IntelligenceDelays, rework, manual touches
  2. DesignProcess ManagerTarget process in BPMN
  3. ApproveProcess GovernanceAutomatic sync on approval
  • SAP Cloud ALMDraft solution processInput to Fit-to-Standard
  • PublishProcess Collaboration HubThe portal employees read

After go-live Process Intelligence measures the same process again; a deviating variant starts a new cycle.

Processes that start from a ready-made template

SAP publishes separate templates (value accelerators) for SAP S/4HANA and SAP ECC in Process Intelligence. Where no template exists, we build the event log on our own data model.

  • Value accelerator

    Order to cash

    Case
    Sales order item
    Steps
    Sales, delivery, billing

    Questions we ask in the measurement

    • Which orders wait in credit checks, and for how long?
    • In which sales organisation does the time from delivery to invoice grow?
    • Which customers and products concentrate order changes?

    Tables in the template documentation

    • VBAK
    • VBAP
  • Value accelerator

    Procure to pay

    Case
    Purchase order item
    Steps
    Requisition, contract, order, goods receipt, invoice

    Questions we ask in the measurement

    • In which categories are orders created after the invoice?
    • For which amounts and categories does the approval cycle get longer?
    • Which suppliers send invoices with price or quantity differences?

    Tables in the template documentation

    • EKPO
  • Other SAP templates

    From invoices to maintenance

    • Invoice to Cash
    • Invoice to Pay
    • Make to Stock
    • Operate to Maintain
    • Inspect to Quality
    • Acquire to Onboard
    • SAP EWM
    • SAP TM
    • SAP IBP

    Templates include data pipelines, metrics and dashboards and are optional. Indicators are calculated from the organisation's own event logs.

  • The suite includes Process Manager, Process Intelligence, Process Insights, Journey Modeler, Process Collaboration Hub, Process Governance and Process Transformation Manager.
  • The Cloud ALM integration works only with Signavio subscriptions based on SAP contracts; one Signavio workspace connects to a single Cloud ALM tenant.
  • A process flow synchronised to SAP Cloud ALM cannot be changed there; changes are made in Signavio as a new revision, while requirements and tests stay linked to the process in Cloud ALM.
  • Event logs contain user identities, so with KVKK, Türkiye's data protection law, in mind, the pseudonymisation decision is taken before mining starts.

PROJECT AND OPERATIONS

SAP Cloud ALM: one record from project to operations

SAP Cloud ALM is SAP's cloud-based application lifecycle management tool. It is included in cloud subscriptions that contain Enterprise Support, cloud editions and in SAP Enterprise Support; one tenant per customer number is available at no extra charge. A RISE project opens by selecting the product-specific SAP Activate roadmap, and tasks are derived from that roadmap.

Requirements gathered in Fit-to-Standard workshops are linked to the process; every change travels with its transports as a feature, and tests and defects sit in the same record. Requirements or user stories can be created directly from SAP Readiness Check findings. The RISE with SAP Methodology dashboards show the system's clean core compliance through software stack, extensibility, data and integration indicators.

Processes go from Signavio to Cloud ALM, requirements come back

Design happens in Signavio; requirements, tests and operations are attached to the process in Cloud ALM.

SAP Signavio

  1. MeasureInsights and Intelligence
  2. DesignProcess Manager, BPMN
  3. ApproveProcess Governance

Processsince December 2024

Requirementssince March 2026

SAP Cloud ALM

  1. RequirementsFit-to-Standard output
  2. Features and testsTransports, Tricentis
  3. OperationsMonitoring, alerts, Negzel AMS

After go-live Process Intelligence measures the same process again.

SAP Cloud ALM in a RISE project

From a Readiness Check finding to an alert in production, every step stays linked to the one before.

  1. DiscoverReadiness Check findingsRequirement or user story
  2. PrepareProject and roadmapActivate tasks, gate 1
  3. ExploreSolution processesDraft process from Signavio
  4. ExploreRequirementsFit-to-Standard output
  5. RealizeFeatures and transportsAcross the landscape with CTS
  6. RealizeTests and defectsManual and Tricentis
  7. DeployDeployment plan and releaseFeatures that go together
  8. RunOperations monitoringAlerts, email, ServiceNow

Negzel AMS · SLA priority

The two sides of Cloud ALM: implementation and operations

Implementation keeps the record of the RISE project; operations watches the system after go-live.

Implementation

Cloud ALM for Implementation
Project and tasksProjects and Setup · Tasks
Tasks derive from the product-specific Activate roadmap; they can also be created manually or from requirements.
Processes
Scope of solution processes; draft processes from Signavio are published here.
Fit-to-StandardProcess based scoping
Workshops run on process-based scoping.
Requirements
A need the standard does not cover is recorded, approved and split into user stories and tasks.
Features and deploymentFeatures · Deployment
Changes travel across the landscape with their transports; deployment is scheduled.
ReleaseDeployment Plans
Requirements and features that go to production together are collected in a release.
Tests and defectsTest Plans · Defects
Manual and automated tests; defects raised directly from a failed run.
Readiness Check linkSAP Readiness Check Integration
Requirements or user stories are created from findings.
Clean core dashboardsRISE with SAP Methodology
Software stack, extensibility, data and integration indicators.

Operations

Cloud ALM for Operations
Business process monitoring
Visibility of business processes across a hybrid landscape.
Integration and exceptionsIntegration & Exception Monitoring
Links messages to the flow across systems.
Real user monitoring
Response times of real user requests.
Jobs and automationJob & Automation Monitoring
Health and deviations of background jobs.
Configuration and securityConfiguration & Security Analysis
Technical configuration items in one place.
Health monitoring
One view of system and service health.
Event processingIntelligent Event Processing
Alert, email, ServiceNow ticket or operation flow.

ABAP systems connect through the ST-PI add-on (/SDF/ALM_SETUP); data collection is switched on separately for each monitoring use case. Synthetic user monitoring is not among the use cases supported for the private edition.

  • Cloud ALM does not move transports itself; in the private edition it manages them through CTS. CTS+ is not supported.
  • Tricentis Test Automation for SAP connects to Cloud ALM with a term licence that comes with Enterprise Support, cloud editions.
  • Cloud ALM may only be used for the customer's own ALM processes; we set up monitoring in the customer's own Cloud ALM tenant.

TRANSITION

From SAP Solution Manager to SAP Cloud ALM

Mainstream maintenance for SAP Solution Manager 7.2 ends on 31 December 2027, and SAP recommends completing the move to SAP Cloud ALM before then. Customers with extended maintenance for Business Suite 7 get extended maintenance until the end of 2030, but it covers only seven functions; application operations and business process monitoring are not among them.

For the inventory, SAP Readiness Check for SAP Cloud ALM shows which Solution Manager scenarios are really in use and suggests their Cloud ALM counterparts. We run the move in stages with SAP's “Transition to SAP Cloud ALM” Activate roadmap, without leaving monitoring idle for a single day.

Solution Manager 7.2 and Cloud ALM

TopicTodaySAP Solution Manager 7.2TargetSAP Cloud ALM
MaintenanceMainstream maintenance ends 31.12.2027; with Business Suite 7 extended maintenance, extended maintenance limited to seven functions until the end of 2030The ALM tool SAP recommends moving to
Usage rightsUnder the support contract; after 2027 and 2030 under customer-specific maintenanceIncluded in subscriptions with Enterprise Support, cloud editions and in SAP Enterprise Support; one tenant per customer number
Change managementChange Request Management (ChaRM)Feature, release and deployment orchestration; workflows and change documents are not migrated
Data that moves·Only solution documentation and Test Suite (Selective Data Transfer)
IT service managementOne of the seven functions under extended maintenanceNot among the functions that move to Cloud ALM; needs a separate ITSM decision
MonitoringApplication operations and business process monitoring are not in extended maintenanceBusiness process, integration, job and health monitoring on the operations side
Inventory·SAP Readiness Check for SAP Cloud ALM lists current usage and suggests counterparts
AMS providerSAP's recommendation for AMS providers is SAP Focused Run; it stays in mainstream maintenance after 2027Only for the customer's own ALM processes; monitoring is set up in the customer's tenant

Usage rights depend on the contract type.

The move with Negzel in five steps

  1. 1Inventory

    SAP Readiness Check for SAP Cloud ALM shows which Solution Manager scenarios are really in use and which systems are connected.

  2. 2Mapping

    Each scenario gets its Cloud ALM counterpart; ChaRM moves to features and deployment, IT service management to a separate tool. For complex ChaRM setups SAP's advice to wait for the required functionality is weighed.

  3. 3Setup and connection

    The Cloud ALM tenant, users and roles are set up; ABAP systems connect through ST-PI and data collection is switched on per monitoring use case.

  4. 4Transfer and parallel run

    Solution documentation and Test Suite are transferred; monitoring and project scenarios are handed over in stages.

  5. 5Shutdown

    After validation, Solution Manager scenarios are switched off step by step.

The steps follow SAP's “Transition to SAP Cloud ALM” Activate roadmap.

COMMON QUESTIONS

Frequently asked questions

Is RISE with SAP just a cloud contract?

On the contract side, yes: RISE with SAP brings ERP software, hosting and technical operation of the infrastructure together in one subscription. The contract does not do the move itself, though; taking processes, custom code, data, integrations and the operating model to SAP S/4HANA Cloud Private Edition (SAP Cloud ERP Private) is a separate project.

Does clean core mean removing all custom developments?

No. Differentiation that creates business value moves to a suitable extension layer; unused code and code that repeats the standard are reduced, and the remaining developments are brought under governance.

Where does a RISE roadmap start?

It starts by assessing the inventory of current systems, processes, data, code and integrations together with business goals. Transformation waves based on value and risk are then built.

Who chooses the infrastructure, and what are the options?

The system is set up in the data centre the customer chooses in the contract; whichever it is, technical operations stay with SAP. The options are an SAP data centre, AWS, Microsoft Azure, Google Cloud and IBM Power Virtual Server, with Alibaba Cloud in China. There are also SAP Sovereign Cloud options and a customer data centre option that runs in the customer's own data centre on Dell, HPE or Lenovo infrastructure. We assess the choice with you independently, looking at data residency, existing cloud contracts and regional options.

Can we stay on ECC after 2030?

For ECC on premise there is no extended maintenance after 2030; the system moves to customer-specific maintenance. SAP ERP, private edition, transition option, which SAP offers for large and complex systems, is not a maintenance extension but a time-bound subscription for 2031-2033. Its conditions: the system is moved to SAP ERP, private edition on SAP HANA before 31 December 2030, it is at least 2 TB in size, and it comes with the max success plan; eligible products are listed in SAP Note 3591251. The 2033 date for compatibility packs in SAP Note 2269324 is a separate matter.

Is SAP Cloud ALM included in a RISE with SAP contract?

SAP Cloud ALM is included in cloud subscriptions that contain Enterprise Support, cloud editions and in SAP Enterprise Support; one tenant per customer number is available at no extra charge. The support item in the contract decides the right; we read the contract's product list when planning the tool.

Does the SAP Signavio baseline measurement cost anything?

A one-time data load with SAP Signavio Process Insights, discovery edition is free; setting up the technical prerequisites is a standard SAP service in RISE. The analysis runs in SAP's region in the Netherlands, so with KVKK in mind the data transfer and pseudonymisation decisions are taken before the analysis.

When should we move from Solution Manager to Cloud ALM?

Mainstream maintenance for SAP Solution Manager 7.2 ends on 31 December 2027, and SAP recommends completing the move before then. We recommend running the RISE project in Cloud ALM from the start, so the project, test and change record stays in the same place after go-live.

THE COMPLETE JOURNEY

Other areas of expertise

Quick access

SAP module consulting

We provide consulting across SAP modules, from finance to manufacturing and from integration to data.

Looking for the right consultant?Find an Expert SAP Consultant
Finance8
Human resources3
Logistics11
Manufacturing7
Projects and engineering2
Platform and development4
Integration2
Data and control3