Guide

SAP BW to Datasphere migration consultant: what a SAP Datasphere migration consultant does

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.

A SAP BW to Datasphere migration consultant assesses a BW estate, recommends which of four paths fits, and delivers the move object by object while reporting keeps running. A SAP Datasphere migration consultant who has not run a BW estate down is a different person. Demand is large and permanent-led: on 5 October 2026 the Analytics Legends live contract corpus held 262 postings naming SAP BW together with Datasphere or Business Data Cloud, 250 of them permanent and 8 freelance, with 4 on contract.

What the role does, in the order the work happens

Assessment comes first and decides everything after it: an inventory of what exists, what is used and what has a named owner. The Analytics Legends concept card on BW Bridge treats an estate of more than 1,000 queries and 100 InfoProviders as the large case and fewer than 50 objects as small, and says a small estate is usually faster and cheaper to migrate directly. That is an editorial rule of thumb, not an SAP threshold.

Path choice follows, then the build: moving or regenerating objects, rebuilding the semantic layer, redoing access rules and reconciling every migrated report against its legacy twin. The longest job is the least technical: getting owners to agree that a report can be retired.

The four paths and the arguments for each

The BW end-of-support card sets out four paths. Lift-and-shift preserves the existing model and rehosts it; it buys time without buying capability, and the modelling debt travels with it, so it should be presented as a transitional step. Selective migration moves what earns its keep and retires the rest; it is usually the honest answer and the one that needs the most political cover, because retire means somebody's report disappears. Rebuild uses the migration to redo the semantic layer in Datasphere; it has the highest cost and ceiling and is defensible only when the existing model is itself the problem. Stay and federate keeps BW in place and exposes it through BDC Connect, which suits a working estate whose real need is reach rather than replacement.

BW Bridge and the Data Product Generator: what each delivers

BW Bridge runs BW/4HANA-style objects inside the Datasphere tenant: advanced DataStore Objects, CompositeProviders, transformations and process chains, but not InfoCubes and not BEx queries, so classic InfoCubes must first become advanced DataStore Objects. It lets existing investment co-exist with Datasphere while new modelling is done natively. It also costs twice during the bridge period, because it consumes Datasphere capacity on top of the embedded BW/4 footprint. The card's advice is to write a sunset date into the architecture decision record, which is the difference between a bridge and a permanent fixture.

The BW Data Product Generator, for BW 7.5 and BW/4HANA, reads advanced DataStore Objects and CompositeProviders and generates Business Data Cloud data products from them, with BW remaining the system of record during coexistence. It moves data and structure. It does not convert BEx queries to SAC stories, translate transformation logic or wire data access controls on the consuming side. The semantic layer in Datasphere comes from a separate path, the BW/4HANA model transfer. A consultant who conflates the two promises a finished semantic model where the tool delivers provisioned data.

Dates, and why a candidate must verify them

The dates people quote are often wrong for the customer in front of them. SAP's maintenance announcement of 23 April 2020, as recorded on our concept card, gives 31 December 2027 as the end of mainstream maintenance for SAP BW 7.5, including BW 7.5 on SAP HANA, with optional paid extended maintenance to 2030, and at least 2040 for BW/4HANA, aligned with S/4HANA. Whether a given customer is affected depends on the release it runs and on its contract. The same card adds an AI reason to move: Joule's grounding layers read governed Business Data Cloud data products, so an un-federated BW estate is invisible to Joule agents.

Decision table: what to check before hiring one

Assessment — Ask for: an inventory they produced, with usage evidence and owners · Weak answer: a count of objects with no usage data.

Path choice — Ask for: a case where they recommended against their preferred path · Weak answer: every estate gets the same path.

BW Bridge — Ask for: the objects moved, the capacity cost and the sunset date written down · Weak answer: bridge provisioned, no exit plan.

Data Product Generator — Ask for: which InfoProviders generated products and what BW still owned afterwards · Weak answer: says the BW system was simply switched off.

Semantic layer — Ask for: a Datasphere model reconciled to a BEx query, with differences explained · Weak answer: only demos or sandbox work.

Retirement — Ask for: reports retired, who agreed, how the objection was handled · Weak answer: retirement left to the client.

Market and rates

Of the 262 postings on 5 October 2026 naming BW with Datasphere or BDC, Germany accounts for 111, India 23, the United States 22 and Poland 12; 151 are senior. Only 7 postings use explicit migration, conversion or modernisation wording, 3 of them freelance, so the volume is mostly broader BW-plus-Datasphere roles. Co-skills include Datasphere (215 under its longer SAP name), SAC (194), BW/4HANA (138), BDC (114) and Databricks (62). Source: Analytics Legends live contract corpus, generated 5 October 2026. None of the 262 publishes a day rate.

Published rates are indirect. A French market guide dated 26 March 2026, sampling 420 profiles across 15 missions, gives BW a EUR 570 median and BW/4HANA EUR 660, with the BW/4HANA plus SAC profile at EUR 590 to 770, median 680. Our band model, as at 8 May 2026, gives BW/4HANA migration EUR 850, Datasphere EUR 870 and Business Data Cloud EUR 950 per day at France and senior level. The first set is marketplace medians, which sit below direct-client rates by construction; the second is modelled.

What we cannot assert

No source we hold publishes a day rate specific to BW-to-Datasphere migration. The corpus counts are advertised roles, not total demand, and the DACH weighting reflects both the market and how the corpus is crawled.

Frequently asked

Is a BW migration consultant the same as a Datasphere consultant?

No. A Datasphere consultant models and operates the target. A migration consultant decides what moves, in which order and how, and reconciles the results against the BW system being retired.

Does BW Bridge migrate everything?

No. It runs advanced DataStore Objects, CompositeProviders, transformations and process chains, but not InfoCubes or BEx queries.

Does the Data Product Generator convert my BEx queries?

No. It generates data products from existing InfoProviders. Query logic, transformation logic and data access controls remain design work on the Datasphere and SAC side.

Is BW/4HANA also ending?

Per SAP's maintenance announcement as recorded on our concept card, BW/4HANA maintenance runs to at least 2040. Check your own product version and contract before quoting any date.

What this page is built on

SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths
The BW-to-BDC Migration Wave
BW Bridge: The Migration Arbitration
BW Data Product Generator
Analytics Legends live contract corpus, 5 October 2026
Analytics Legends day-rate corpus (LinkQuest 26 Mar 2026, band model 8 May 2026)