BDC and Datasphere: What Changes, What Stays

When SAP folded Datasphere into Business Data Cloud, the first question from customers with a running Datasphere tenant was always the same: what happens to what we built? The short answer is reassuring. The more useful part of the answer is what you should stop building.

TL;DR: Your Datasphere investment carries over: spaces, models, flows and skills stay, and SAP Analytics Cloud and SAP BW become components of the same platform. What changes is packaging (one BDC contract in capacity units), SAP-managed data products that replace hand-built replication for standard SAP data, SAP Databricks for machine learning inside SAP governance, and master data governance moving into BDC. Stop building flows for data SAP already ships, and time the licence conversion with your next renewal.

What stays

Datasphere does not disappear. It continues as the integration and semantic modelling layer inside BDC, as SAP’s introduction to Business Data Cloud lists it among the core components:

• Spaces and models carry over. Semantic models, views and data flows keep working. BDC consumes them rather than replacing them. The SAP Datasphere documentation remains the reference for the modelling layer.
• SAP Analytics Cloud stays as the visualisation and planning layer, now part of the bundle instead of a separate contract.
• SAP BW stays reachable. BW and BW private cloud edition are components of BDC, so existing warehouse models do not have to be rebuilt on day one.
• Skills stay valuable. People who can model in Datasphere are the people who will connect data products to business questions in BDC.

If you invested in Datasphere over the past years, that work was not wasted. This is an evolution of the packaging around a surviving core, not a platform replacement of the kind SAP customers have lived through before (the Sales Cloud V1 to V2 move was a genuine rebuild; this is not).

What changes

Four things are genuinely different.

1. Packaging and licensing. One BDC contract covers Datasphere, SAP Analytics Cloud, SAP BW and SAP Databricks. SAP licenses BDC on a capacity-unit basis; how a standalone Datasphere or SAC contract converts depends on your contract.
2. Data products replace hand-built extraction. A data product is “a refined data set, metadata describing the data set, and an access port or API” (SAP News). Where SAP ships one (the first wave concentrated on S/4HANA, SAP Ariba and SAP SuccessFactors), the replication flow your team built for the same data becomes legacy. SAP maintains the data product through releases; nobody maintains your custom flow but you. For CX data such as Sales Cloud V2, check the catalogue for your release and keep Datasphere replication where no data product exists yet.
3. Machine learning moves inside the fence. Workloads that used to require copying SAP data to a separate ML platform can run in SAP Databricks under the same governance, and BDC Connect shares data products zero-copy with an existing Databricks, Snowflake or other partner platform. Under the Swiss nDSG and the GDPR, “the data never left SAP governance” is a sentence your data protection officer will appreciate.
4. Master data governance moves into BDC. In May 2026 SAP made SAP Master Data Governance and SAP HANA Cloud core components of BDC and completed the acquisition of Reltio, whose multi-domain master data management it is bringing into BDC (SAP News). Customer and product master data quality, long a separate project, is becoming part of the same platform.

What to stop building

Concretely, from today:

• Stop building new replication flows for data SAP ships as a data product. Check the catalogue first and build only for the gaps.
• Stop modelling generic entities from scratch. Customer, sales order and invoice arrive semantically modelled where a data product exists. Your modelling effort belongs in the last mile: your industry logic, your KPIs, your extension fields.
• Stop copying SAP data out for machine learning when SAP Databricks or a zero-copy share can do the job inside the governance boundary.
• Stop treating S/4HANA and CX analytics as separate projects. On the integrated stack, one foundation serves both. Splitting them recreates the disagreeing-numbers problem BDC exists to end. The Sales Cloud V2 and BDC integration patterns show how the CRM side joins in.

A short migration checklist

Step	What to check	Output
1. Inventory	Spaces, models, replication flows, BW queries in use	List of assets with owner and usage
2. Catalogue match	Which flows duplicate an SAP data product for your release	Flows to retire, flows to keep
3. Contract	Renewal dates of Datasphere and SAC, actual consumption	Conversion timing and sizing basis
4. BW path	Which BW models stay, which move to data products	Staged plan instead of a big-bang migration
5. Master data	Ownership of customer and product attributes	Named owner per domain
6. First use case	One question management already asks	Scope for the first BDC release

The renewal conversation

Time the move commercially. If your Datasphere or SAC contract renews in the next twelve months, negotiate the BDC conversion at renewal. Bring your consumption history: capacity sizing favours customers who know their actual usage over those who accept a default size.

Keep the scope modest. The right first step after conversion is not a platform migration project. It is one domain, the data products that serve it, and one analytics view that answers a question your management already asks. Master data ownership comes first; why CRM data depends on the data foundation sets out the order. The platform work follows demand, not the other way round.

If you want a second pair of eyes on the inventory, talk to us. Spadoom delivers the ERP core and the CX stack with one team, which is why we look at both sides of the data model at once.

FAQ

Does SAP Datasphere go away with Business Data Cloud?

No. Datasphere continues as the integration and modelling component inside BDC; spaces, models and data flows carry over. What changes is the packaging: new capabilities, data products and licensing now arrive under the BDC umbrella.

Do existing Datasphere licences convert to BDC?

SAP licenses BDC on a capacity-unit basis, and conversion from standalone Datasphere or SAP Analytics Cloud contracts depends on your contract. The practical advice is to time the conversion with your next renewal, bring your real consumption figures and negotiate the bundle rather than the components.

Should I still start a new Datasphere project in 2026?

Start it as a BDC project. The work is largely the same (spaces, models, flows), but contract and architecture should assume BDC packaging, data products wherever SAP ships them, and hand-built replication only where no data product exists yet.

What happens to SAP BW in BDC?

SAP BW, including BW private cloud edition, is one of the BDC components. Existing BW models can keep running while new analytics are built on data products and Datasphere, so the move can be staged instead of a single migration project.