👁 SAP "recommends" cloud — here's what that means for you
SAP "recommends" cloud. Understanding your options makes all the difference.
SAP offers two cloud paths — GROW and RISE. Both are well-structured, but the responsibilities differ significantly. One is mostly managed by SAP. The other puts approximately 1,200 service activities on your plate. Understanding which is which helps you plan properly.
SAP "recommends" you move to cloud — a sound direction for most organisations. What's useful to understand upfront: the four paths differ in who runs what, who owns what, and how many of those approximately 1,200 service activities become your responsibility. This tool helps you plan, whichever path you're on.
GROW with SAP
S/4HANA Cloud, Essential Edition
🏢Public cloud, multi-tenant
📋SAP-standard processes only
🔒Quarterly upgrades — mandatory
🚗SAP manages the platform and upgrades
📐Limited customisation (side-by-side extensions)
⚡Faster time-to-value, smaller scope
📦Fewer customer-side RACI responsibilities
Best for: New SAP customers, orgs wanting standard processes
VS
RISE with SAP
S/4HANA Cloud, Enterprise Edition
🏗️Private cloud, single-tenant (your landscape)
🔧Customise processes, code, and integrations
⏱️Upgrade cadence more flexible, but still SAP-driven
🚂You manage processes; SAP maintains infrastructure
📐Full customisation, but full responsibility
📊≈1,200 service activities (RISE), 8 R&R chapters
🔴Most customer-side RACI responsibilities
Best for: Existing SAP customers with complex landscapes
💡 The key distinction that's worth clarifying upfront
GROW: SAP owns the platform, the upgrade cycle, and most operational responsibility. You adapt your processes to SAP's standard. Fewer moving parts, less to manage — but also less control.
RISE: You keep your customisations, your integrations, your landscape design — and you also keep most of the operational responsibility. SAP manages infrastructure, but you're Accountable for process design, testing, training, data strategy, security, interfaces, and change management. That's where the ≈1,200 activities come from.
The documentation covers this, but it's spread across multiple SAP documents and not always easy to map to your specific situation. That's where advisory adds value.
Dimension
GROW
RISE
Key Difference
Tenant model
Multi-tenant (public cloud)
Single-tenant (private cloud)
Data sovereignty & isolation
Process scope
SAP standard only
Custom processes allowed
Custom = more RACI ownership
Upgrade cycle
Quarterly, mandatory
Flexible, but SAP-driven
Both require regression testing
Customer RACI burden
Lower (~150 activities)
Higher (≈1,200 activities)
RISE = 6× more responsibility
Outside-datacentre tasks
Fewer (network, SSO)
Full (network, print, identity, EDI, DR)
Cloud ALM doesn't cover these on either path
Change management
Adapt to SAP standard
Redesign your processes
Org change is often underestimated on both paths
Timeline
6–12 months
6–24 months (path-dependent)
Scope expansion affects both
Who manages the gaps
You (but fewer gaps)
You (many more gaps)
Advisory fills what Cloud ALM leaves out
Every Path Gets Support
Four Paths. One Advisory Team Behind You.
Whether you're moving to GROW, transitioning to RISE, managing a partial exit, or navigating an unexpected contract end — we help you understand your responsibilities, plan your scope, and stay in control. No path is left without guidance.
🔄 Brownfield
🏗️ Greenfield
🚪 Leavers
🔀 Transitioning Out
Keep your ECC history. Convert to S/4HANA.
Brownfield preserves your existing configuration and data — but the conversion itself is more complex than most organisations expect. SAP's roadmap has moved, and the target keeps shifting.
Technical conversion WatchSystem conversion, data migration, and custom code remediation are the core technical work. SAP provides tooling, but the volume of custom code can be a significant effort.
Custom code remediation AvoidEvery Z-program, enhancement, and modification needs assessment. Some are straightforward ATC fixes; others require redesign. Underestimating this is the most common Brownfield mistake.
Shifting roadmap WatchECC maintenance deadlines (2027→2030→?), mandatory S/4HANA Cloud features added over time. Understanding the current target helps you plan effectively rather than chasing a moving goal.
Data migration WatchVolume reduction, archiving, and cleansing before conversion. The cleaner your data going in, the smoother the conversion — and the lower your TCO.
Scope keeps expanding Avoid"While we're at it" scope creep is the Brownfield trap. Every additional customisation or process change adds risk and time. Advisory helps keep the scope bounded.
⏱ 6–18 monthsModerate complexity
Start fresh. New processes. New design.
Greenfield gives you a clean slate — but that freedom is also the risk. The main challenge isn't technical; it's keeping "what should we look like now?" focused and bounded.
Process redesign SaveFit-to-standard workshops, business process redesign, and organisational change management. This is where Greenfield succeeds or fails — not in the technology.
Scope definition AvoidThe hardest part of Greenfield: defining scope tightly. "What should we look like?" can expand indefinitely. Clear decision gates and governance overlays keep the programme on track.
Change management AvoidEntirely new processes mean entirely new training needs. This is the highest change management burden of any path. Plan 20–25% of budget for training and adoption.
Data migration from scratch WatchNo historical carry-forward means deciding what to migrate, what to archive, and what to leave behind. Data selection decisions are irreversible — plan them carefully.
Integration landscape WatchAll integrations must be rebuilt from scratch. Non-SAP services, EDI connections, and middleware all need rearchitecting for the new landscape.
⏱ 18–24 monthsHigh complexity
Moving some workloads off SAP. Staying with others.
The most varied path — running two workstreams while managing the transition thoughtfully. Some workloads convert to S/4HANA; others move to alternative platforms. This is hybrid migration done right.
Parallel workstreams AvoidScope effectively doubles — you're managing both an SAP track and a non-SAP track simultaneously. Coordination between the two is the biggest challenge.
Workload assessment SaveDeciding which workloads stay on SAP and which move off requires objective criteria. Cost, complexity, strategic fit, and dependency mapping all play a role.
Data strategy WatchSplit data between platforms, manage interfaces, and maintain consistency. Data that lives in two places needs two governance models.
Vendor coordination WatchMultiple vendors, multiple contracts, multiple timelines. Advisory helps keep everyone aligned and prevents gaps between workstreams.
Exit planning AvoidContract lock-in, extraction fees, and transition timelines for the departing workloads. Plan exit costs before committing to the split.
⏱ 12–30 monthsComplex
SAP contract ending. Time to plan what's next.
Focused transition — evaluating alternatives, managing the SAP dialogue, and planning migration to a new platform. Having a structured plan before the contract timeline starts makes all the difference.
Alternative evaluation SaveObjective assessment of replacement platforms, timelines, and feasibility. Advisory provides the structure to evaluate options without pressure.
SAP dialogue management WatchManaging the conversation with SAP — contract terms, timelines, and exit provisions. Understanding your position before the conversation starts.
Exit cost planning AvoidLock-in penalties, data extraction fees, transition team costs. These are often not discussed until it's too late. Plan for them upfront.
Migration timeline AvoidMoving to a new platform under contract deadline pressure adds risk. A structured timeline with decision gates reduces that pressure.
Knowledge transfer WatchYears of SAP configuration and business logic need to be documented and transferred. This is often the most underestimated part of transitioning out.
⏱ 6–18 monthsUrgent
💡 Every path has responsibilities to own
GROW: org change management, data migration planning, process adaptation, user training, stakeholder governance. RISE: all of that plus ≈1,200 service activities and outside-datacentre areas. Leavers & Transitioning Out: dual-track coordination plus vendor dialogue. Cloud ALM covers the SAP baseline — advisory helps align what Cloud ALM doesn't cover, across all paths. Take the assessment — we'll tailor it to your situation.
The Numbers
≈1,200 Activities. 169 Cloud Services. One Matrix to Navigate.
Every path — GROW, RISE, Leavers, Transitioning Out — touches parts of this matrix. RISE customers carry the most. Here's the scale of responsibility under RISE, and where advisory planning makes the difference.
🤝 Who Does What? The Roles Explained
The ≈1,200 service activities in the RISE R&R matrix don't just say "Customer" or "Vendor" — they assign specific roles. Here's who those roles actually are:
Role
What They Do
Key Point
SAP (ECS) Enterprise Cloud Services
Infrastructure, HANA database management, system provisioning, NetWeaver operations, server provisioning, movement services, platform monitoring
SAP4me tracks these. They're visible, documented, and have clear SLAs. This is what most people think of when they hear "SAP manages RISE."
Customer (You)
Process design, testing strategy, user training, data strategy, security governance, change management, role design, interface ownership, compliance sign-off
You're Accountable for far more than you might expect. The matrix assigns you A (Accountable) and R (Responsible) on hundreds of activities — and nobody from SAP will remind you.
May assist with migration, custom development, integration, and project management — depending on your contract
Not tracked in SAP4me. Their scope, SLAs, and handoff points are defined by your engagement — and that's where gaps appear.
Third Party Non-SAP vendors, ISV add-ons, BTP extensions
Add-on software licences, BTP extensions, middleware, EDI partners, print services, monitoring tools, identity providers, archive systems
Not tracked by anyone. SAP4me doesn't track these. Cloud ALM doesn't cover them. Your contract doesn't include them. Yet they're often essential to keep the landscape running — and their costs can exceed the SAP subscription itself.
≈1,200
R&R Service ActivitiesEvery task in SAP's official Roles & Responsibilities matrix — from kick-off to go-live to operations. Each has a RACI assignment: SAP (ECS), Customer, ICI, or Third Party. Knowing which are yours helps you plan resources and responsibilities.
8
Responsibility ChaptersService Management, Managed Infrastructure, Database Management (HANA), Core Technical Operations, NetWeaver Operations, Server Provisioning, Cloud Application Services, Movement Services.
169
Enterprise Cloud ServicesFrom system provisioning to regression testing to security monitoring. Each with prep, execution, and planning windows. Some are standard, some are chargeable.
6–24
Month RoadmapBrownfield: 6–18 months. Greenfield: 18–24 months. Leavers: 12–30 months. All share the same ≈1,200 activities — the question is which ones you own.
Timeline Overview
The RISE Roadmap: Prepare → Run
SAP structures every RISE migration across five phases. The activities are the same regardless of path — what changes is duration and which tasks get more weight.
Prepare M+1
Explore M+2–5
Gate ✓
Realize M+6–13
Deploy M+14–18
Run M+19–24
▶Prepare — Governance & DiscoveryMonth 1
Establish governance, kick off discovery, set up change management. This phase sets the direction — governance and scope clarity here make everything downstream smoother.
📋Service Management (Chapter A) — 17 activities▶
Delivery & Operations Kick-OffCR1wSAP baseline
Review Support Manual & Landscape ScopeCR1wSAP baseline
The strategic heart of any migration. Brownfield focuses on technical conversion. Greenfield reimagines processes. Both cover ≈1,200 R&R activities — good planning here pays off throughout.
The longest phase. All ≈1,200 activities converge here. Most "Your gap" tasks cluster in Realize — thorough preparation in earlier phases helps manage this workload.
Network Connectivity (VPN/ExpressRoute)RC3wYour gap
Print Infrastructure MigrationAI2wYour gap
🔄Data Migration & Conversion — Your gap▶
Data Cleansing & Archiving (Pre-migration)AC8wYour gap
Custom Code Retirement Decision (Z-programs)AC4wYour gap
Interface Rebuild (Legacy → Cloud Integration)RC8wYour gap
🧪Testing — All chapters converge▶
Unit Testing per Process AreaRA4wYour gap
Integration TestingRA3wYour gap
User Acceptance Testing (UAT)AI3wYour gap
Regression Testing (ECS Service)CR2wSAP baseline
▶Deploy — Cutover & Go-LiveMonths 14–18
High-pressure cutover. Every interface, user, and custom process must switch — preparation in earlier phases is what makes this go smoothly.
🚀Cutover & Go-Live — Critical path▶
Cutover Rehearsal (Dry Run)RA1wYour gap
Final Data Migration & ReconciliationRA3dYour gap
Go-Live Smoke TestRA1dYour gap
Hypercare Support SetupCR2wSAP baseline
🔒Security & Access (Chapter G) — 19 activities▶
User & Role MigrationAC2wYour gap
SSO & Identity FederationRA2wYour gap
SOD Review (Segregation of Duties)RC1wSAP baseline
▶Run — Stabilize & OptimizeMonths 19–24+
RISE transitions to ongoing operations. You remain Accountable for governance, continuous improvement, and tracking SAP's evolving roadmap.
📊Operations & Continuous Improvement▶
Hypercare Incident ManagementCR4wSAP baseline
Knowledge Transfer to BAU TeamAC4wYour gap
Continuous Improvement ReviewsACOngoingYour gap
SAP Roadmap Shift MonitoringAIOngoingYour gap
Key Considerations
Beyond Cloud ALM: What Still Needs Planning
These considerations apply regardless of path — GROW, RISE, Brownfield, or Transitioning Out. They're well-documented in SAP's materials, but worth highlighting because they tend to require more planning than initially expected.
⚠ Scope & Strategy
🌐 Outside the Data Centre
👥 Organisational Change
📋 Cloud ALM Gaps
Scope Definition — Every Path
Scope creeps differently depending on your migration path. What starts as a defined project can double in complexity if the boundaries aren't clear from the start.
Brownfield WatchSAP's roadmap evolves — ECC maintenance deadlines shift, new mandatory features appear. Your scope needs to track a moving target.
Greenfield Avoid"What should we look like?" can expand scope significantly. Without clear decision gates, the ideal future state keeps expanding.
GROW WatchQuarterly upgrades add items continuously. Each upgrade may trigger scope adjustments that weren't in the original plan.
Leavers & Transitioning Out AvoidScope effectively doubles — you're running parallel tracks (old system maintenance + new system build) until transition is complete.
Outside-the-Datacentre Planning
Cloud ALM covers your SAP landscape. It does not cover the infrastructure and services that surround it — and these are all Customer-Accountable in the R&R matrix.
Network WatchVPN, ExpressRoute, DNS, firewall rules — all must be planned for the new cloud topology. Cloud ALM doesn't address your network architecture.
Identity & Access WatchSAML/OIDC federation, role mapping, SSO integration. These sit between your IdP and SAP — not inside Cloud ALM's scope.
Print WatchOutput management (OMS, ADS) often requires separate infrastructure or migration. Rarely planned early enough.
Monitoring & DR AvoidYour existing monitoring stack (Datadog, Dynatrace, custom) needs reconfiguration for cloud. DR strategy must be rebuilt — SAP's RISE DR is not the same as your DR.
Security AvoidWAF rules, vulnerability scanning, pen testing, compliance controls — all Customer-Accountable, all outside Cloud ALM's scope.
EDI & Integration WatchPartner connections, B2B gateways, middleware — these rarely align automatically across organisational silos.
Organisational Change — Often Underestimated
Training & change management typically accounts for 20–25% of budget. It's the area most organisations under-resource, and the one that most directly affects go-live success.
GROW adoption WatchEveryone adapts to SAP's standard. Training is about learning new processes, not custom ones — but the volume of change can overwhelm users.
RISE Brownfield relearning WatchUsers must relearn familiar processes in a new UI. Productivity dips are real and measurable. Plan for them.
RISE Greenfield new processes AvoidEntirely new processes mean entirely new training needs. This is the highest change management burden of any path.
Change readiness SaveAssessing organisational readiness early helps allocate training budget where it matters. Stakeholder mapping and communication planning pay for themselves.
Cloud ALM — Baseline Plan, Not Custom Plan
SAP Cloud ALM gives you a solid baseline plan. But custom tasks, governance overlays, and decision gates still need to be managed outside Cloud ALM — typically in spreadsheets that can be hard to maintain consistently across the programme.
Custom task injection AvoidCloud ALM doesn't allow adding custom tasks. Your non-SAP service activities, internal milestones, and governance gates need a separate structure to track.
Governance overlays WatchDecision gates, approval workflows, and compliance checkpoints that sit on top of the SAP roadmap. These need their own tracking.
Non-SAP service alignment WatchThe ≈1,200 R&R service activities include Customer-Accountable items that Cloud ALM doesn't manage. Advisory planning maps these gaps and coordinates across organisational silos.
Advisory fills the gap SaveAdvisory planning adds structure around what Cloud ALM leaves out — custom decision gates, non-SAP service coordination, and governance overlays that keep the programme on track.
Total Cost of Ownership
TCO Optimisation: Before, During & After Go-Live
Migration cost is only part of the picture. Most organisations focus on licence fees and infrastructure, but TCO in SAP Cloud includes hidden costs that compound if not addressed at the right stage. Here's where advisory planning helps you optimise — not just migrate.
📋 Before Go-Live
⚡ During Go-Live
📈 After Go-Live
🔍 Often Overlooked
Reduce What You Carry Over
The cheapest line item is one you never migrate. Pre-migration is your best window to eliminate waste.
Licence optimisation SaveAudit for shelfware, unused modules, and over-licensed users before contract negotiations begin. Every unused licence you carry into cloud is permanent cost.
Custom code remediation AvoidRetire or replace custom developments before migration. Dead code carried into cloud increases run cost permanently — and makes every future upgrade harder.
Data volume reduction SaveArchive and purge before migration. Smaller database = smaller infra footprint = lower monthly cost. Data archiving is not one-time — it's ongoing.
Integration audit AvoidIdentify and retire unused interfaces. Every integration you migrate is one you maintain in cloud. Reducing interfaces before migration is pure savings.
Third-party licences WatchSAP4me tracks your SAP products, but third-party add-ons, ISV solutions, and BTP extensions are not. These licences are often renewed on autopilot, may overlap with included cloud capabilities, and can exceed the SAP subscription cost itself if left unchecked.
Contract negotiation WatchUnderstand RISE vs. GROW pricing levers, multi-year discounts, and what's included vs. chargeable extras. Negotiate before you commit.
Minimise the Transition Premium
The cutover period is where unplanned costs appear. Every week of extended transition is a week of dual-run cost and deferred ROI.
Parallel run efficiency AvoidMinimise dual-run costs. Every week of parallel operation is double infra cost plus additional licence overlap. Shorten the parallel run window where possible.
Phased migration SaveAvoid big-bang where possible. Phased rollouts reduce risk premium and allow early cost course-correction.
Testing automation SaveManual testing is the biggest variable cost in cutover. Invest in regression automation early — it pays back in every future upgrade cycle.
Change management WatchReduce the productivity dip. Poor adoption extends the ROI timeline more than any technical issue. Invest in training before go-live, not after.
Sandbox strategy WatchIt may be cheaper to keep a sandbox outside RISE until that's no longer possible. Plan for when external hosting becomes unviable — don't just carry it along at RISE rates.
Keep Optimising — Cloud Costs Don't Stand Still
Cloud TCO shifts continuously. The go-live budget is a starting point, not the final number.
Continuous right-sizing SaveInstance sizes correct at go-live may be oversized after stabilisation. Review quarterly — RISE allows scaling adjustments.
Adoption monitoring WatchLow adoption = wasted licences. Track usage, reassign, or decommission. Every unused seat is money burned.
Process standardisation SaveEvery custom process costs more in cloud. Move toward standard where possible — it reduces upgrade friction and run cost.
Data archiving & warehouse retention WatchNot a one-time activity. Cloud storage costs compound. Data warehouse retention adds knowledge and maintenance cost on top of archiving. But it can also be a regulatory or operational requirement — a project tier keeps the production line clean and stable, while retention policies handle compliance and audit.
Training as recurring cost WatchQuarterly upgrades mean quarterly training needs. Budget for it, or pay in adoption gaps.
FinOps discipline SaveCloud cost governance, alerting on sprawl, and chargeback models keep costs visible and managed. Without it, costs drift upward silently.
Hidden Costs That Compound
These are the costs that don't show up in the SAP quote — and that's exactly why they catch organisations off guard.
Sandbox & test environments AvoidCan run 2–3× production footprint if not governed. It may be cheaper to keep a sandbox outside RISE until that's no longer possible — but the cost of carrying it inside RISE is often underestimated. Right-size, decommission ruthlessly, and plan for when external hosting is no longer viable.
Third-party licences AvoidSAP4me tracks SAP products. It does not track your third-party add-ons, ISV solutions, or BTP extensions. These are renewed on autopilot, may overlap with included cloud capabilities, and can exceed the SAP subscription cost itself.
Integration middleware WatchPI/PO → Integration Suite is a separate cost stream, often budgeted separately and forgotten in TCO. Plan for it explicitly.
Data archiving & warehouse retention WatchOngoing, not one-time. Cloud storage costs compound. Retention adds knowledge and maintenance cost. But it can also be a requirement — project tier keeps the production line clean, retention handles compliance.
Exit costs AvoidFor Leavers and Transitioning Out paths: contract lock-in penalties, data extraction fees, and transition team costs. No one budgets for leaving until they have to.
Shadow IT discovery AvoidNon-SAP services duplicating cloud capabilities. You may be paying twice without realising. Audit early, consolidate.
💡 TCO is not a one-time calculation
Cloud TCO shifts continuously — licence adjustments, infra right-sizing, adoption changes, and SAP's evolving roadmap all affect cost. Advisory planning helps you identify optimisation opportunities at each stage, not just at contract signing. Take the assessment to see where your biggest TCO levers are.
RACI Breakdown
≈1,200 Activities: Who's Accountable?
Every service activity in the SAP RISE R&R matrix has a RACI assignment. Here's how responsibility splits across 8 chapters — and who actually owns each piece.
R Responsible — does the workA Accountable — owns the outcomeC Consulted — provides inputI Informed — kept in the loop
⚠ The Clarity Gap
The R&R matrix says "Customer" and "Vendor" — but "Vendor" is not one entity. SAP (ECS) handles infrastructure and platform services. ICI partners handle implementation support. Third-party vendors provide add-ons, middleware, and integrations. Nobody tracks the third-party costs or responsibilities — not SAP4me, not Cloud ALM, not your contract. This is where customers get surprised, and where advisory planning makes the difference.
Chapter
Activities
Customer (You)
SAP (ECS)
ICI / Partner
Planning Focus
A — Service Management
17
24% A/R
76% A/R
Varies
Governance overlay needed
B — Managed Infrastructure
70
7% A/R
93% A/R
Minimal
Network & print ownership
C — Database Management (HANA)
149
12% A/R
88% A/R
Minimal
Data strategy ownership
D — Core Technical Operations
475
18% A/R
82% A/R
Significant
Process design, testing, training
E — NetWeaver Operations
106
15% A/R
85% A/R
Varies
Interface & integration decisions
F — Server Provisioning
35
6% A/R
94% A/R
Minimal
Landscape planning
G — Cloud Application Services
19
32% A/R
68% A/R
Varies
Security & role design
H — Movement Services
13
15% A/R
85% A/R
Significant
Migration scope & sequence
Note: "Customer" means you — the organisation on the RISE contract. "SAP (ECS)" is SAP's Enterprise Cloud Services division. "ICI / Partner" varies by your engagement. Third-party vendor responsibilities (add-ons, middleware, EDI, print, monitoring) are not included in this matrix — they're tracked separately, if at all. That gap is one of the main reasons advisory planning exists.
What You Actually Get
So What Does Advisory Planning Change, Concretely?
Fair question. SAP gives you Cloud ALM, SAP4me, and a contract. Here's what still falls through the cracks — and what this tool can do about it, depending on what you share with us.
The Problem This Solves
You sign a RISE or GROW contract. SAP4me shows your SAP deliverables. Cloud ALM tracks your SAP project plan. Your contract lists your responsibilities in general terms. What's missing: which of the ≈1,200 activities are specifically yours, which ones need a third party you haven't contracted yet, which costs are not in your SAP subscription, and whether your organisation has the skills to cover what you just became Accountable for. That gap is where budget overruns, delayed go-lives, and post-migration surprises come from.
You need to know
What SAP gives you
What still falls through the cracks
What this tool does
Which of the ≈1,200 activities am I actually Accountable for?
R&R matrix with generic "Customer" labels
"Customer" doesn't tell you which team, which budget, which deadline
Maps each activity to your path and organisation — the more you tell us about your landscape, the more precise the mapping becomes
What do third-party vendors cost me — and who tracks them?
SAP4me tracks SAP products only
Third-party licences, ISV add-ons, BTP extensions, middleware, EDI — nobody tracks these
Identifies non-SAP dependencies per path and flags where they're untracked — we can highlight what to look for, but you'll need to fill in your specific vendor details
What's not covered by my SAP contract?
RISE covers infrastructure and platform
Network, identity, print, monitoring, DR, security, data archiving, warehouse retention — all Customer-Accountable
Lists every outside-datacentre area with planning steps — cost estimates improve with your actual contract and landscape details
Does my team have the skills for what we just signed up for?
Not assessed
You're Accountable for testing, training, change management, role design — but do you have the people?
Maps skills gaps against your assigned RACI responsibilities — the more honestly you assess your team's capabilities, the more actionable the output
Which path is right for us?
SAP recommends cloud
"Cloud" isn't one thing. GROW, RISE, Leavers, and Transitioning Out have fundamentally different cost profiles and responsibility loads
4-path assessment with scored comparison — the scoring reflects what you tell us about your landscape, customisations, and organisation
How do I avoid the common cost traps?
Not in scope
Sandbox carry-along costs, data archiving requirements, warehouse retention, custom code that won't migrate cleanly
TCO optimisation per phase: before, during, and after go-live — based on known patterns; your actual savings depend on your specific landscape and contract
Bottom Line
SAP's tools tell you what SAP is doing. This tool tells you what you need to do — and what you're missing. It doesn't replace Cloud ALM or SAP4me. It fills in what they don't cover: your non-SAP services, your skills gaps, your hidden costs, and your organisational readiness. The depth of the answer depends on what you share. The more complete your input — your landscape, your customisations, your team capabilities — the more precise and actionable the output. The assessment takes 30–60 minutes. The output is a tailored roadmap you can act on.
Complementary Planning
Cloud ALM Covers the Baseline. What About the Rest?
SAP Cloud ALM manages your SAP project plan. This tool maps everything else — the responsibilities, costs, and gaps that SAP's tools don't cover.
Capability
SAP Cloud ALM
Advisory Planning
Baseline migration plan (SAP scope)
✓
✓
Non-SAP service alignment
✗
✓
Organisational gap analysis
✗
✓
Custom decision gates & governance overlays
✗
✓
Network/identity/print/DR migration planning
✗
✓
Change management & readiness assessment
✗
✓
SAP roadmap shift monitoring
✗
✓
4 path scoring (Brown/Green/Leave/Exit)
✗
✓
Ready to See What You're Actually Responsible For?
Cloud ALM shows you the SAP baseline. SAP4me shows you SAP's deliverables. This assessment shows you everything else — the activities, costs, and gaps that aren't in your contract but are your responsibility. 30–60 minutes for a tailored roadmap you can act on.