SAP Migrate Advisory — Consultant Pitch

The Problem

Customers Arrive Unprepared — and Everyone Pays for It

RISE consultants know the pattern:

The customer signs the RISE contract thinking SAP handles "everything cloud."
Three months in, they discover they're Accountable for hundreds of activities they didn't budget for.
The board approved a migration budget — but it didn't include third-party licences, sandbox costs, data archiving, identity federation, print infrastructure, or monitoring rebuilds.
The project timeline slips because nobody mapped the non-SAP dependencies.
The consultant ends up firefighting instead of advising.

What the board doesn't know

SAP's R&R matrix lists ≈1,200 activities. "Customer" is Accountable for hundreds of them. But "Customer" doesn't tell the CFO which budget line, which team, or which deadline. The board approves a number — not a responsibility map.

What This Tool Does

Turns a Signed Contract Into a Complete Migration Plan

The SAP Migrate Advisory Tool takes the customer's input — their landscape, customisations, team, and constraints — and produces:

Output	What it gives the board
Responsibility Map	Every activity the customer is Accountable for, broken down by team, budget, and deadline — not just "Customer"
TCO Optimisation Plan	Cost traps before, during, and after go-live: sandbox costs, archiving, warehouse retention, third-party licences SAP4me doesn't track
4-Path Comparison	Scored comparison of Brownfield, Greenfield, GROW & RISE, and Leavers & Transitioning Out — what each path actually costs and requires
Skills Gap Analysis	Which capabilities the customer's team has vs. what they just became Accountable for — before the project starts
Non-SAP Dependency Map	Third-party integrations, ISV add-ons, middleware, EDI, monitoring, identity — the costs and responsibilities nobody else tracks
Budget Timeline	When budgets need to be ready, per phase — so the board isn't surprised by costs they didn't plan for

The depth depends on what the customer shares

The more complete the input — landscape details, customisations, team capabilities, vendor landscape — the more precise and actionable the output. A 30–60 minute assessment produces a tailored roadmap the board can act on.

Board-Level Value

Early Budget Clarity — Before It's Too Late

≈1,200

Activities in the RISE R&R matrix

169

ECS services across 7 categories

4

Migration paths assessed

Most boards approve a migration budget based on licence fees and infrastructure. They rarely see:

Cost area	Who tracks it	Typical board visibility
SAP licences & infrastructure	SAP4me	Visible
Third-party ISV licences	Nobody	Invisible
Sandbox / non-production carry cost	Partially (SAP contract)	Partial
Data archiving & retention	Nobody	Invisible
Identity federation & SSO rebuild	Customer (often unplanned)	Invisible
Monitoring & ITSM integration	Customer	Partial
Print infrastructure re-routing	Customer (often forgotten)	Invisible
Team skills gap remediation	Customer (not budgeted)	Invisible
Change management & training	Customer (underestimated)	Partial

What changes when the board has the full picture

Before: Board approves a migration budget based on SAP licence + infrastructure costs. Hidden costs surface 3–6 months in. Project slips. Budget overruns. The consultant gets blamed.

After: Board sees every cost category — including the ones nobody tracks — before signing. Budgets are approved per phase. Timelines are realistic. The consultant starts with a prepared customer.

How It Works

30–60 Minutes In, Complete Migration Plan Out

Step	What happens	Output
1. Assessment	Customer answers 80+ questions across 8 sections: landscape, custom code, infrastructure, change readiness, support transition, compliance, risks & dependencies	Structured input with per-question commentary
2. Analysis	Engine maps responses against ≈1,200 R&R activities, 169 ECS services, and the full RACI matrix — filtered by the customer's chosen path	Path-specific responsibility map
3. Output	Executive summary, technical report, TCO optimisation per phase, meeting schedule — all tailored to the customer's actual landscape and organisation	PDF reports the board can act on

Questionnaire Coverage

Customer & System Overview — organisation, industry, migration scope, system groups
SAP Landscape (per system group) — product, version, database, OS, modules, instances, users
Custom Code & Interfaces — Z-programs, enhancements, interface technologies, data volume, archiving, NSE
Infrastructure (per system group) — virtualisation, network, identity/SSO, print, monitoring, backup, DR, non-SAP apps, security stack
Change Management & Readiness — executive sponsorship, team maturity, user readiness, training, communication
Support Process Transition — current support model, Basis/ABAP/functional team sizes, incident management (ServiceNow, SolMan, Jira), SLAs, change management, testing, knowledge base
Compliance & Governance — GDPR, SOX, ISO 27001, NIS2, data residency, audit trails, SoD, encryption, governance model
Risks & Dependencies — hard deadlines, budget status, business continuity, external dependencies, biggest concerns

Every question has a commentary field

Customers can add context, nuance, and follow-up notes to every answer. This is where the richest input comes from — and where the consultant adds the most value.

Clarity on Roles

Who Does What — Spelled Out

One of the weakest points in any RISE engagement: nobody makes it clear who is responsible for what. This tool names the roles explicitly:

Role	What they do	Key point
SAP (ECS)	Infrastructure, HANA, provisioning, NetWeaver, monitoring	SAP4me tracks these. Clear SLAs. What most people think "SAP manages" means.
Customer (You)	Process design, testing, training, data strategy, security, change management, role design, compliance	Accountable for hundreds of activities. Nobody from SAP reminds you.
ICI / Implementation Partner	Migration, custom dev, integration, project management — varies by contract	Not tracked in SAP4me. Gaps appear at handoff points.
Third Party	Add-ons, BTP extensions, middleware, EDI, print, monitoring, IdP, archiving	Not tracked by anyone. SAP4me doesn't cover them. Cloud ALM doesn't cover them. Your contract doesn't include them. Yet their costs can exceed the SAP subscription.

The tool doesn't just say "Customer" — it maps each activity to the specific role and flags where responsibility is unclear or untracked.

Complement, Not Competition

This Tool Works With SAP Cloud ALM — Not Against It

SAP Cloud ALM is the official tool for managing the SAP project plan. This advisory tool handles what Cloud ALM doesn't cover:

What Cloud ALM does	What this tool adds
SAP project plan & milestones	Non-SAP service alignment & dependency mapping
SAP deliverables tracking	Organisational gap analysis (skills, readiness, change maturity)
RISE baseline responsibilities	Custom decision gates & governance overlays
SAP implementation tasks	Third-party licence, integration & cost tracking

Practical outcome

The customer runs Cloud ALM for the SAP project plan. They run this assessment for everything else — the budget lines, team gaps, and hidden costs that determine whether the project succeeds or overruns.

Why RISE Consultants Use This

It Makes Your Customer Better Prepared — Before You Start

Without this tool	With this tool
Customer thinks SAP handles "everything cloud"	Customer knows exactly which ≈1,200 activities they're Accountable for
Board approves licence + infrastructure budget	Board approves a complete budget per phase — including hidden costs
Consultant discovers gaps during implementation	Gaps are identified before the project starts
Third-party costs surface as surprises	Third-party dependencies are mapped and budgeted upfront
"Customer" is a vague label in the R&R matrix	Each activity is mapped to a specific role: SAP (ECS), Customer, ICI, or Third Party
Consultant spends weeks educating the customer	Customer arrives informed — consultant focuses on execution

All Four Paths

Not Just RISE — Four Paths, Each With Full Assessment

Most tools assume every customer is going to RISE. Reality is messier:

Brownfield (System Conversion) — keep your history, convert in place. Lowest risk, highest retention. But: every Z-program and interface must be remediated.
Greenfield (New Implementation) — start clean on S/4HANA. Best for process redesign. But: data migration complexity, reimplementation cost, and parallel running.
Leavers (Moving Away from SAP) — exiting SAP to another platform. Deserves as much support as staying. Dual-migration planning, data extraction, decommissioning.
Transitioning Out (Forced Exit) — when SAP declines contract renewal or the customer chooses not to continue. Urgent timelines, data portability, vendor lock-in concerns.

Each path gets a full assessment with path-specific scoring, responsibility mapping, and budget timeline.

Want to See It in Action?

The teaser page shows what the assessment covers. The full questionnaire takes 30–60 minutes and produces board-ready reports.

Public teaser: sapmigrate.rsol.io
Full assessment: sapmigrate.rsol.io/questionnaire.html (login required)

Built by Scandisuit (CVR 44170175) · Complementary to SAP Cloud ALM · Not affiliated with SAP SE