Guide

SAP Datasphere vs BW4HANA: stay, convert, or move to Datasphere and BDC

As of 2026-10-05

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.

The question usually arrives as a deadline, and the deadline belongs to the wrong product. Classic BW 7.5 reaches the end of mainstream maintenance on 31 December 2027, with optional paid extended maintenance to 2030. BW/4HANA is maintained to at least 2040, aligned with S/4HANA (SAP maintenance announcement, 23 April 2020). So the choice between BW/4HANA and Datasphere is a decision about direction and about what you want to consume from Business Data Cloud, not a countdown, unless you are still on 7.5.

Two clocks, and which one applies to you

SAP published two different horizons. BW 7.5, including BW on SAP HANA because it runs on the 7.5 release, has mainstream maintenance until 31 December 2027 and an optional paid extension to 2030. BW/4HANA has no near date: SAP states maintenance to at least 2040, in line with S/4HANA. Source for both: SAP maintenance announcement, 23 April 2020.

The scale explains why the topic is loud. SAP product management put the classic BW 7.5 base at 20,000 to 30,000 customers worldwide (Sapphire 2025, reported by SAPinsider). The Analytics Legends registry holds roughly 2,500 BW/4HANA customers, a floor drawn from public disclosure rather than a count from a register. Read the ratio rather than either number: the modernised cohort is a clear minority.

Your own end date depends on release, product and contract. Check SAP's maintenance schedule for your exact version before using any date, including the ones above.

They are not rivals: three layers

BW/4HANA is a HANA-only data warehouse product, generally available since 2016, with its own code line. It is a successor within the BW lineage, not release 4 of BW. Datasphere is a cloud data warehousing service with a different modelling model. Business Data Cloud is the packaged data-product layer above Datasphere. A customer can run BW/4HANA and Datasphere together, and BW bridge exists to let BW content land inside Datasphere.

The either/or framing misleads: the real question is where new modelling will happen and who consumes the data. What Business Data Cloud adds on top of Datasphere has its own decision-frame page, linked below.

BW bridge and the BW Data Product Generator are different tools

BW bridge runs BW/4HANA-style objects inside a Datasphere tenant: advanced DataStore Objects, CompositeProviders, transformations and process chains. It does not take classic InfoCubes or BEx queries. Its purpose is time: existing objects keep working while new modelling is done natively in Datasphere. The cost side matters. Bridge consumes Datasphere capacity units and carries the embedded BW/4 footprint, so you pay for both during the coexistence period. The practical discipline is to write a sunset date into the architecture decision record at kickoff, because an undated bridge tends to become permanent.

The BW Data Product Generator is an add-on for BW 7.5 and BW/4HANA that reads advanced DataStore Objects and CompositeProviders and generates governed data products published into Business Data Cloud. BW remains the system of record. It moves data and structure. It does not convert BEx queries into Analytics Cloud stories, translate transformation logic or set up data access controls on the consuming side. The semantic layer in Datasphere comes from a separate path, the BW/4HANA model transfer. SAP publishes no productivity multiplier for the Generator, so any speed-up figure in a proposal is the supplier's own estimate.

Skills and the shape of the licence

On skills, the market buys the overlap. In the Analytics Legends live contract corpus of 5 October 2026 (1,595 postings), 566 mention Datasphere and 243 of those also name BW or BW/4HANA; 258 postings mention BW/4HANA and 249 mention Business Data Cloud. Source: public/api/contracts-lean.json. Practically, BW craft carries over: InfoObjects, transformations, DTPs and process chains survive the move to BW/4HANA and are what the bridge and the Generator read. What does not carry over is BEx query logic and anything built on InfoCubes, which must become advanced DataStore Objects first.

On licensing, no price list for these combinations sits in our sources, and we do not estimate one. The shape is what can be stated: Datasphere is consumed in capacity units, BW bridge adds the embedded BW/4 footprint on top, and a BW/4HANA Public Cloud Edition is a managed BW/4HANA instance in SAP's cloud rather than Datasphere.

Decision table

Classic BW 7.5, small estate (fewer than 50 active InfoProviders and fewer than 100 active queries), business willing to freeze reporting during a migration sprint — Route: native Datasphere, no bridge · Clock: 2027 met · Watch: the freeze, typically 6 to 9 months for a small estate.

Classic BW 7.5, large estate (hundreds of InfoProviders, thousands of queries), no tolerance for a reporting freeze, funded multi-year programme — Route: BW bridge with a dated sunset · Clock: 2027 met object by object · Watch: paying twice during the overlap.

Already on BW/4HANA, stable estate, no cloud mandate — Route: stay · Clock: 2040 at least · Watch: the direction of travel towards Business Data Cloud, not a deadline.

BW 7.5 or BW/4HANA where the driver is hosting, not analytics — Route: BW/4HANA Public Cloud Edition · Clock: extends the BW runtime · Watch: no Datasphere semantic layer and no lakehouse integration come with it.

BW logic trusted, Business Data Cloud and Databricks consumers wanted early — Route: Data Product Generator while BW stays the record · Clock: coexistence · Watch: queries and access rules are still redesign work.

BW model itself is the problem (undocumented exits, workarounds nobody trusts) — Route: remodel natively in Datasphere · Clock: outside the BW horizon · Watch: generating products from bad logic only moves the debt.

What we cannot assert

SAP publishes no price for Datasphere capacity combined with BW bridge or BW/4HANA, and none of our sources states the licence terms of a given contract. The sizes of the 'small' and 'large' estate thresholds above are the rule of thumb on our concept card, not an SAP limit. The end date for your own system depends on your release and contract.

Frequently asked

Is BW/4HANA out of support in 2027?

No. The 31 December 2027 date applies to classic BW 7.5 mainstream maintenance, with an optional paid extension to 2030. BW/4HANA is maintained to at least 2040, aligned with S/4HANA (SAP maintenance announcement, 23 April 2020). Check your own contract.

Can I run BW/4HANA and Datasphere together?

Yes. They sit at different layers and BW bridge exists to let BW content run inside a Datasphere tenant. The cost is paying for Datasphere capacity and the embedded BW/4 footprint at the same time, so date the overlap.

Does the Data Product Generator convert my BEx queries?

No. It generates data products from advanced DataStore Objects and CompositeProviders. Query logic, transformation routines and access rules remain design work in Datasphere and Analytics Cloud.

Do I need BW skills to work on Datasphere projects?

In the live corpus of 5 October 2026, 243 of the 566 postings that mention Datasphere also name BW or BW/4HANA, so BW knowledge is asked for in a large share of them, though not in most.

What this page is built on

SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths
BW Bridge: The Migration Arbitration
BW Data Product Generator
SAP BW/4HANA
Analytics Legends live contract corpus, 5 October 2026