Concept card

The BW-to-BDC Migration Wave

As of 2026-09-27

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is The BW-to-BDC Migration Wave?

~4,000 BW MEE customers (Analytics Legends estimate, Q1 2026) create a €4-6B addressable consulting market through 2028 — consultants who ship 3-5 BW-to-BDC migrations enter 2029 with decade-long anchor relationships.

How do I migrate SAP BW to SAP Datasphere?

Start with an inventory of what BW actually serves (flows, ADSOs, CompositeProviders, queries and their real usage), then pick a path per domain: BW Bridge to carry existing BW objects into a Datasphere tenant, greenfield remodelling in Datasphere views for what deserves a rebuild, and decommissioning for what nobody uses. Migrate domain by domain, reconnect SAP Analytics Cloud, and write a sunset date for anything running on the bridge.

What it is

The BW-to-BDC Migration Wave is the label analytics consultants use for the industry-wide migration cycle SAP has triggered by setting a maintenance horizon on classic BW and BW/4HANA, and by making Business Data Cloud the target platform for enterprise analytics. It matters because migration waves of this scale happen roughly once a decade in the SAP ecosystem — the last comparable event was the move from BW on any database to BW on HANA — and each wave redraws which consulting firms and independent consultants hold the anchor relationships for the following ten years. Whoever ships the first two or three BDC migrations for a given account tends to keep that account's analytics work indefinitely, because migration programmes create deep tacit knowledge of the customer's data model, governance quirks and political landscape that is expensive for a competitor to replicate.

How it works, mechanically, is that SAP customers fall into a handful of cohorts depending on where they currently sit. Customers still running BW on extended maintenance face a hard deadline and have to decide, customers running ECC alongside BW get pulled into the conversation as part of a broader S/4HANA transformation, customers already on BW/4HANA are weighing whether to move again so soon, and customers who bypassed SAP's warehouse entirely and adopted Snowflake or Databricks are being courted back in through BDC's SAP-native semantic layer. Each cohort has a different trigger, timeline and risk appetite, which is why the consulting engagement looks different depending on which cohort the client sits in.

Why it matters

The €4-6B market splits roughly €2-4B from BW MEE customers alone (average €500k-1M per migration) plus a further slice from the ~25% of ECC-to-S/4 programmes that touch BW migration.
Selective migration via BW Bridge is the pragmatic path for most Tier-1 customers in 2026-2027 — it's the volume play, not greenfield BDC.
This is a once-a-decade wave, not a recurring opportunity — consultants who don't position into it during 2026-2028 miss the anchor-relationship window entirely.

Key points

Total addressable market 2026-2028: €4-6B (BW-to-BDC migrations).
~4,000 BW MEE customers (Analytics Legends estimate, Q1 2026); classic BW 7.5 population 20,000-30,000 worldwide (SAP, Sapphire 2025).
Four migration paths: lift-and-shift · BW Bridge selective · greenfield BDC · hybrid extended.
Five customer cohorts: BW MEE EOL · ECC+BW · BW/4 → BDC · pure-cloud · net-new.
Four engagement phases: Discovery (€50-150k) · Design (€200-400k) · Execute (€500k-2M) · Hypercare (€100-300k retainer).
BW Bridge is transitional, not destination (≤ 24 months cap).
DSAG 2026 ranks BW-to-BDC #1 SAP analytics priority.
Senior consultants who ship 3-5 migrations build decade-long anchor relationships.

Terms used on this page

BW MEE: BW on Major-Enterprise-Edition (extended maintenance). ~4,000 BW MEE customers, inside a classic BW 7.5 population SAP puts at 20,000-30,000 worldwide (D. K., Sapphire 2025); mainstream maintenance ends 2027, paid extension to 2030.
BW Bridge: A BW/4HANA runtime inside the Datasphere tenant in which aDSOs, CompositeProviders and InfoObjects keep running — classic InfoCubes are not supported (companions C030, C187). Transitional, not destination.
Lift-and-shift to BW/4 in BDC: Path 1: minimal disruption, minimal modernisation. Useful as transitional step.
Selective migration via BW Bridge: Path 2: pragmatic Tier-1 default for 2026-2027. Progressive without full re-engineering.
Greenfield BDC: Path 3: redesign analytics from S/4 + non-SAP. Maximum modernisation, longest timeline.
Hybrid extended: Path 4: BW + BDC coexist for years; LoB-by-LoB migration. Reality of most Tier-1 programmes.
Discovery phase: €50-150k bounded engagement to scope the migration path. Goal: enable €500k+ Execute decision.
Reporting-parity testing: Auditor-grade reconciliation that every BW report reproduces in SAC + Datasphere with documented variance.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.