Concept card

SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths

As of 2026-08-02T21:40:00Z

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

What is SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths?

Your end-of-maintenance date depends on product, release and contract — this page invents none. It states what is real: a maintenance horizon plus BDC as the named target, four customer cohorts that do not share a deadline, and four migration paths argued on trade-offs.

Search "SAP BW end of life 2027" and you will find a dozen confident dates. Be careful with all of them, including the one in the query: your end-of-maintenance date depends on which BW product you run, which release, and what your contract says — and the only authoritative answer is SAP's own maintenance schedule for your specific product version. This page will not invent a date for you. It will tell you what is actually happening and what the decision is.

What is actually happening

SAP has set a maintenance horizon on classic BW and on BW/4HANA, and has made Business Data Cloud the target platform for enterprise analytics. That combination — a closing window on the old platform plus a named destination — is what has triggered the largest migration cycle in the SAP analytics ecosystem since the move from BW on any database to BW on HANA.

The scale is why it matters commercially as well as technically: roughly four thousand BW customers in the main European market plus around seventeen thousand ECC customers sit inside the addressable population, and the resulting consulting demand is measured in billions through 2028.

You are in one of four cohorts, and they do not share a deadline

Customers still on classic BW under extended maintenance face the hardest date and have to decide first.

Customers running ECC alongside BW get pulled into the conversation as part of a broader S/4HANA transformation — their BW decision is a dependent clause in a bigger programme, not a standalone project.

Why it matters

This is the migration wave that redraws which firms hold which accounts for the next decade — and the single fastest way to lose the room is to quote a date you did not verify for that customer's exact release.

Key points

🔴 There is no single BW end-of-life date: it depends on the product, the release and the contract. Verify against SAP's maintenance schedule for that customer's version.
What IS true: SAP set a maintenance horizon on classic BW and BW/4HANA, and named Business Data Cloud as the analytics target.
That combination triggered the largest SAP analytics migration cycle since BW-on-any-database moved to BW-on-HANA.
Scale: ~4,000 BW customers in the main European market, with consulting demand measured in billions through 2028.
Four cohorts, four different deadlines: extended-maintenance classic BW, ECC-alongside-BW, already-on-BW/4HANA, and those who left for Snowflake/Databricks.
A generic "BW is ending" pitch addresses the wrong cohort three times out of four.
Path 1 — lift-and-shift: buys time, not capability. Inherits BDC's cost model AND every existing modelling debt. Transitional step, never an end state.
Path 2 — selective migration: usually the honest answer, and the one needing the most political cover, because "retire" means someone's report disappears.
Path 3 — rebuild in Datasphere: highest cost and ceiling; defensible only when the existing model is genuinely the problem.
Path 4 — stay and federate through BDC Connect: legitimate when the BW estate works and the real need is reach, not replacement.

Terms used on this page

Extended maintenance: The paid, time-limited support phase after mainstream maintenance ends. Its expiry is the hard date for the first cohort — and it is product- and contract-specific.
Lift-and-shift: Rehosting the existing BW model on the new platform unchanged. Buys time without buying capability; the modelling debt travels with it.
Selective migration: Moving what earns its keep and retiring the rest. Usually the honest path; the retirement decisions are political, not technical.
BW Data Product Generator: The mechanism that turns existing BW objects into BDC-consumable Data Products, changing the cost arithmetic of the less invasive paths.
BDC Connect: The federation layer that lets a working BW or external estate be reached from BDC without replacing it.
Cohort: The customer's starting position — classic BW, ECC+BW, BW/4HANA, or departed to an open stack. It determines trigger, timeline and risk appetite.
Migration wave: An ecosystem-wide cycle that recurs roughly once a decade and redraws which firms hold which accounts for the following ten years.
Modelling debt: Workarounds and compromises accumulated over a warehouse model's life. It survives a rehost and surfaces as cost on the new platform.

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.