Lesson 2 of 6
Paths: lift, expose, convert, rebuild
10 min
Listen to this lesson
SAP's recommended path for BW customers is lift, shift, innovate: lift BW into SAP BW private cloud edition within Business Data Cloud, shift (expose) BW data as data products, and innovate by moving use cases to SAP-managed data products and SAP Datasphere. Alongside it sit two older options: convert to SAP BW/4HANA, and rebuild in Datasphere. This lesson compares them; most real plans combine them.
Lift: SAP BW private cloud edition
The lift moves the existing BW system into the SAP-operated private cloud edition within BDC. SAP's user-group material for BW NetWeaver customers stresses that no conversion to BW/4HANA is required, and that BW 7.5 in the private cloud edition benefits from maintenance support until the end of 2030; converting to BW/4HANA private cloud edition gives support beyond 2030. SAP's reference architecture lists the prerequisites: BW 7.5 on SAP HANA at SPS 24 or later (upgrade the database to HANA first if needed); BW/4HANA 2021 at SPS 04 or later; BW/4HANA 1.0 or 2.0 must first move to the latest 2023 support package.
Expose: BW data products
The Data Product Generator publishes BW InfoProvider data into the SAP Datasphere object store as BW data products, so SAC, Datasphere models and SAP Databricks can use BW data without waiting for a rebuild (lesson 4). It requires the private cloud edition and supported release levels.
Convert: SAP BW/4HANA
A conversion turns BW 7.5 into BW/4HANA, replacing classic objects (InfoCubes, classic DSOs, MultiProviders) with BW/4HANA objects (advanced DSOs, CompositeProviders). SAP offers in-place, remote and shell conversion approaches with transfer tooling. It is the path for customers who want BW as a long-term platform to 2040, either on premise or in the private cloud edition.
Rebuild: SAP Datasphere
A rebuild redesigns use cases in Datasphere, using SAP-managed data products or replication flows from SAP S/4HANA, transformation flows for logic and analytic models for reporting. SAP's reference architecture names supporting tools such as a BW Migration Assistant for data flows and a Query Template Generator for queries (check their status), and SAP Datasphere, SAP BW bridge offers a BW-style staging layer for teams that need to reuse ABAP logic. A rebuild is the cleanest end state and the largest test effort.
| Aspect | Lift (BW PCE) | Expose (DPG) | Convert (BW/4HANA) | Rebuild (Datasphere) |
|---|---|---|---|---|
| BW after | Same BW, SAP-operated | BW stays; data also as products | BW/4HANA | Retired per use case |
| Support horizon | To end 2030 (BW 7.5) | Follows BW PCE | To end 2040 | Cloud service |
| Logic change | None intended | None in BW | Object conversion | Redesign |
| Main test | Query regression before and after | Data product equals InfoProvider | Object and query regression | New model equals old query |
| Test effort | Medium | Low to medium | High | Highest |
For customers that choose conversion, SAP supports several approaches with transfer tooling: an in-place conversion of the existing system, a remote conversion into a new BW/4HANA system, and a shell conversion that transfers metadata without data so the system can be reloaded. Each changes object types, so each needs object-level checks (did every classic object get a correct counterpart?) as well as query regression. For Contoso, conversion is a fallback: Noor’s inventory suggests that by 2030 most use cases will run in Datasphere and SAC, so paying for a conversion to keep BW until 2040 is not justified unless that changes.
What would you do?
Contoso's BWP is BW 7.5 on SAP HANA at an older support package. Sam (Basis lead) proposes to lift it to BW private cloud edition next quarter. What must happen first?
Cost matters as much as support dates. A lift moves BW operations into a subscription inside Business Data Cloud, consumed through BDC capacity, and ends Contoso’s on-premise hardware and Basis effort for BWP. A conversion adds project cost for the object conversion and its testing. A rebuild adds Datasphere and SAC work but removes BW entirely at the end. Noor compares the paths over five years, including extended maintenance as the do-nothing baseline, test effort per path, and the cost of running BW and Datasphere side by side during coexistence. Commercial terms vary by contract, so the comparison uses quotes, not list prices.
- SAP's path: lift (BW PCE), shift (BW data products), innovate (SAP-managed data products, Datasphere).
- Lift prerequisites include BW 7.5 on SAP HANA at SPS 24 or later; no BW/4HANA conversion is needed for BW 7.5.
- Convert to BW/4HANA if BW is needed beyond 2030; rebuild in Datasphere for a clean end state.
- Every path, including the lift, needs query regression and business sign-off.
Check your understanding · not graded
Lesson check
1. What is the minimum BW 7.5 level SAP's reference architecture lists for lifting to BW private cloud edition?
2. Which path suits a customer that needs BW as a platform until 2040?
3. Why does a lift with no intended logic change still need query regression?
4. Which option offers a BW-style staging layer inside Datasphere for reusing ABAP logic?