SAP BW NetWeaver beyond 2030: the new SAP BDC modernization option
SAP now lets you run BW 7.5 until the end of 2033 inside SAP Business Data Cloud. Who qualifies, what is included, what is not and how I would plan it.
Table of contents
On 10 September 2026 SAP introduced the SAP Business Data Cloud Modernization Option for SAP BW NetWeaver: a service that lets you keep running a BW 7.5 system from 1 January 2031 to 31 December 2033, as long as that system lives inside SAP Business Data Cloud. If you own a large BW 7.5 landscape and the 2030 deadline keeps you up at night, this changes the conversation. It is not, however, a free or universal extension, so the small print matters.
What SAP actually announced
Until now SAP’s message for BW NetWeaver was simple: lift your BW 7.5 to the private cloud edition within BDC and you get maintenance until the end of 2030 (for BW/4HANA in the same model, SAP talks about 2040). The new option adds one more stretch for BW 7.5:
- It is a new cloud service, which SAP says is available for subscription from September 2026.
- It covers running the system from 1 January 2031 to 31 December 2033.
- The minimum term is 12 months. You cannot buy “just Q1 2031” to finish a cutover.
- There are no system size restrictions for eligibility.
- If you need more detail on applicability and technical prerequisites, check SAP Note 3768400.
Who qualifies (and who does not)
This is the key detail: the option is exclusively for systems running within SAP Business Data Cloud. SAP states it explicitly: it does not apply to on-premise BW or to BW in other SAP-managed private cloud environments.
| Where you are today | Does the option apply? | What I would do |
|---|---|---|
| BW 7.5 on-premise or on your own hyperscaler | No | Decide now whether BDC is the target; without that there is no bridge |
| BW 7.5 in another SAP-managed private cloud | No | Ask SAP what moving it to the BDC private cloud edition involves |
| BW 7.5 private cloud edition within BDC | Yes, if SAP confirms eligibility | Assess whether you really need 2031–2033, and for how many years |
| BW/4HANA | Not for you | Your horizon is different (2040 in private cloud edition, per SAP) |
In plain terms: this is not a lifeline for teams that want to stand still. It is an incentive to move BW into BDC first and modernise from there at a more sensible pace.
What is included and what is not
Included:
- The ABAP stack, with no functional restrictions compared with a standard BW NetWeaver system. Process chains, transformations, BEx queries and custom ABAP keep working as they do today.
- Two specific add-ons: SAP BPC 10.1 and SEM-BCS. If you still consolidate with SEM-BCS or plan with BPC NetWeaver, this matters: they are among the hardest components to replace.
Not included:
- The Java application server. SAP says the Java stack will not be available after 31 December 2030, because the third-party components it depends on will no longer be supported.
That last point is the one that will catch projects off guard. In my experience, Java shows up in a mature BW 7.5 where you least expect it. This is the inventory I would start now:
- BEx Web Applications and BI Java (7.x web templates, portal iViews with reports).
- The Portal as the entry point to reports or planning applications.
- Adobe Document Services for PDF output.
- Information Broadcasting that relies on web templates.
- Any integration that goes through AS Java components.
If anything on that list is in use, its deadline is 2030, not 2033. Treat it as a separate project with its own replacement (SAP Analytics Cloud, Analysis for Office or whatever fits).
My read as a consultant
The upside: for large BW systems with many integrations and SEM-BCS consolidation, three extra years reduce the risk of a rushed migration. A good modernisation is not a lift & shift. It means deciding what gets redesigned in Datasphere, what is exposed as a Data Product and what gets switched off. That takes time.
What would make me cautious:
- It is an additional subscription, with a 12-month minimum. SAP also recommends pairing it with the Max Success Plan. Ask for the full cost before presenting it as the “cheap” option.
- Extra time gets used up on its own. Without a modernisation plan with milestones, 2033 will arrive just like 2030: with the whole BW still in place.
- You have to be in BDC. If you are on-premise today, the first project is still moving the system. The option only makes sense if that move fits your strategy.
This is how I would use it: take the move to BDC as the moment to put BW on a diet (remove unused InfoProviders, archive, cut memory), start publishing data as Data Products and retire flows domain by domain. The 2031–2033 option would be the buffer for the last domains, not the main plan.
Questions I would take to the SAP account team:
- After the 12-month minimum, can it be renewed year by year, or is it a fixed commitment to 2033?
- What happens to BPC 10.1 and SEM-BCS after 2033? Is there a recommended replacement path?
- How do we functionally replace the Java pieces we use today before 2031?
My recommendation
If you run BW 7.5, do not change your plan because of this news; use it to make the plan realistic. Build two inventories now: Java dependencies (hard stop in 2030) and business domains in migration order. With those on the table, ask SAP for a proposal that compares “modernise before 2030” with “move to BDC and use the option until 2031, 2032 or 2033”. The right decision comes out of that comparison, not out of the headline.
