BW Migration Assessment
As of 2026-08-16
BW migration assessment = 5-dimension scoring (criticality, debt, consumers, volume, modernisation benefit) applied to every InfoProvider, DSO, query and process chain. Consumer mapping is the #1 risk: run RSZELTXREF + SAC connection log before wave 1. Output: scored backlog + executive brief with options A/B/C (Bridge / selective modernisation / greenfield) + named data owners per domain. Use BWMT for inventory — no DIY spreadsheet.
What you will learn
- Conduct a full BW migration readiness assessment — inventory InfoProviders, classify by criticality, and output a scored migration backlog
- Apply the 5-dimension scoring model (business criticality, technical debt, consumer count, data volume, modernisation benefit) to rank every BW object
- Produce an executive migration brief (A/B/C options with risk, cost, and timeline) that sponsors can sign off without a technical translator
- Identify the three most common assessment anti-patterns (over-scope, under-governance, missed consumer mapping) and apply mitigations on a live backlog
Module overview
A BW migration assessment is the single highest-leverage artefact on a BW-to-BDC programme. Get it wrong and the next 18 months become a permanent refactor. A senior consultant delivers an assessment in two weeks, not two months — because the discipline is in what you measure, not how long you take.
The five-dimension scoring model. Every BW object (InfoCube, DSO, MultiProvider, CompositeProvider, BEx query, Process Chain) is scored across five dimensions: (1) business criticality — does a board-level KPI depend on this object? (2) technical debt — how many ABAP custom exits, how many layers of transformation, how old is the source extractor? (3) consumer count — how many queries, reports, SAC stories, and external API callers consume this object? (4) data volume — is this 10M rows or 10B? (5) modernisation benefit — does a Datasphere or BDC equivalent exist that removes the technical debt? Score each 1–5. Sum. The top quartile goes in Wave 1. The bottom quartile is a decommission candidate. Everything in between is Wave 2–3 with explicit dependency chains.
Prerequisites
- Intermediate hands-on experience on SAP analytics projects
- Review core concepts first: C036, C034, C035
Outcomes
- Understand the core concepts behind bw migration assessment
- Apply BW in a typical SAP analytics engagement
- Explain the core architecture and decision points for BW Migration Assessment
- Apply a repeatable implementation pattern in a 15-minute lab format
Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.