SAP BW 7.5 end of maintenance: the two dates, who needs which, and the decision
As of 2026-10-20
SAP BW 7.5 has two dates, not one: mainstream maintenance ends on 31 December 2027, and an optional, paid extended-maintenance phase runs to the end of 2030. Which one binds you depends on your release and your contract, not on the product name. Neither date touches SAP BW/4HANA, which SAP committed to maintain until at least 2040.
Run the SAP BW self-diagnostic — eight questions, your route and your dates
The two dates and where they come from
Both dates come from a single SAP announcement made in April 2020, when SAP aligned the NetWeaver 7.5 and BW 7.5 maintenance strategy with its Business Suite 7 extension. Mainstream maintenance for BW 7.5 runs to the end of 2027. Extended maintenance, offered on the same conditions as Business Suite 7, runs to the end of 2030. In the same announcement SAP aligned BW/4HANA with the S/4HANA maintenance commitment, which means at least 2040.
The practical reading is a staircase. Until 2027 you are in standard maintenance. From 2028 to 2030 you are covered only if you bought into the extended phase. After that, classic BW 7.5 has no announced coverage at all. We record nothing beyond end-2030 because SAP has announced nothing beyond it.
A caution on the dates you will see online. Many pages describe 2030 as a recent extension, a date that "moved" from 2027. The primary sources do not support that: 2027 and 2030 were announced together, as the end of one phase and the end of the next. Anyone who quotes only 2027 is describing the end of mainstream maintenance and calling it the end of BW 7.5.
What extended maintenance means for a BW 7.5 customer
Extended maintenance is optional and carries a price premium over standard maintenance fees. It is a contractual position, not an automatic consequence of reaching 2028. Two customers on the same BW 7.5 release can therefore hold different planning horizons, and a date quoted without the contract in hand is a guess.
SAP's description of the NetWeaver 7.5 extension also attaches a technical condition: operating system and database versions must stay in a combination SAP supports, as listed in its Product Availability Matrix. Over a seven-to-ten-year horizon that can mean platform updates in the middle of the extended period, which is a cost the maintenance premium does not show.
The pricing itself is not public. SAP's announcement states "the same conditions as Business Suite 7" without publishing a figure, and we do not estimate one. The only number that matters is the one in your own maintenance agreement.
Which product the date applies to
BW is a word that covers four different things, and they do not share a horizon. BW 7.x on any database is the classic stack. BW on HANA is the same ABAP application with HANA underneath, so it follows the BW 7.5 dates when it runs on the 7.5 release. BW/4HANA is a separate product with its own code line and a deliberately smaller object model. BW Bridge is a BW runtime hosted inside SAP Datasphere, intended as a landing zone rather than a destination.
The release matters as much as the family. SAP set BW 7.4 and older to end mainstream maintenance on 31 December 2020, with no extended option. A system on an older 7.x release is therefore not covered by the 2027-to-2030 staircase at all. Confirm the exact release from the system itself before you read any date.
SAP puts the classic BW 7.5 installed base at 20,000 to 30,000 customers worldwide (SAP product management, Sapphire 2025). The BW/4HANA installed-base floor is around 2,500 customers. That is a floor from public disclosure, not a census, but it shows how much of the BW estate is still classic.
Which date binds you: a decision by situation
The same announcement lands differently depending on where the customer stands. One line per case:
Classic BW 7.5 on extended maintenance — Binding date: 31 December 2030 · What to do: build the migration plan backwards from it, with a margin for delivery capacity.
Classic BW 7.5 on standard maintenance only — Binding date: 31 December 2027 · What to do: either contract the extension or finish the move before the end of 2027. This is the cohort with the least slack.
BW 7.4 or older — Binding date: already passed (31 December 2020) · What to do: treat the system as unsupported and prioritise accordingly.
BW/4HANA — Binding date: none in this window, SAP states at least 2040 · What to do: no maintenance deadline; the question is value, not compliance.
ECC running alongside BW — Binding date: set by the wider S/4HANA programme · What to do: treat the BW decision as a dependent clause of that programme rather than a project of its own.
What the dates do not say is whether to move to Datasphere and Business Data Cloud. They fix a timetable. They do not change the target, and they do not make the migration cheaper.
The paths available before the date
Four paths cover most real cases, and a good recommendation argues the trade-off rather than defaulting to the one the team already knows.
Lift-and-shift rehosts the existing BW model. It buys time without buying capability: you keep every modelling debt the BW estate has accumulated. BARC's description of SAP's own suggested route (lift, shift, then innovate) notes that the first step to a private cloud edition extends maintenance to 2030, which is useful if the driver is the calendar, but it is a transitional step rather than a destination.
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 a named person's report disappears.
Rebuild redoes the semantic layer in Datasphere. It has the highest cost and the highest ceiling, and is defensible only when the existing model is itself the problem.
Stay and federate leaves BW in place and exposes it through BDC Connect. It suits an estate that works and needs reach, not replacement.
Two tools change the arithmetic. The BW Data Product Generator converts existing BW objects into Business Data Cloud data products, and its conversion warnings flag custom ABAP transformations and complex composite-provider unions for manual remodelling. BW Bridge can hold existing content inside a Datasphere tenant while migration proceeds object by object, but it works best with a sunset date written into the architecture decision, otherwise a bridge becomes permanent.
Working example: three years of runway is not three years of delivery
Take a customer on classic BW 7.5 reading these dates in late 2026. The calendar says 2027 is a little over a year away and 2030 is about four years away. The tempting plan is to buy the extension and migrate in the last two years.
Three things argue against that. First, extended maintenance is a premium paid every year it is used, for a platform that receives no new capability. Second, the people who can deliver a BW conversion are the same limited pool every other BW customer is competing for: SAP's own base figure of 20,000 to 30,000 classic customers all face the same two dates, and delivery capacity is the constraint, not the willingness to move. Third, the object inventory has to exist before any path can be costed. An estimate that names a path but no object inventory is a preference, not an estimate.
The better sequence is inventory first, in the next quarter: classify each object as map, redesign or retire. That output decides whether selective migration, rebuild or federation is realistic, and only then does the contract question (extend or not) become a calculation rather than a reflex.
Mistakes that cost credibility
Quoting a year with no product version beside it. A slide that says 2027 and does not say whether it means BW 7.5 mainstream, BW 7.5 extended or something else will be corrected by the client's basis team, in the room.
Treating 2030 as a fresh extension. It is the end of the phase announced in 2020. Presenting it as news invites the question of where you read it.
Using one urgency pitch for every cohort. A customer already on BW/4HANA has no maintenance deadline in this window, and an urgency pitch aimed at them addresses the wrong problem.
Promising AI readiness from a rehost. A lift-and-shift moves the model, not the grounding: SAP's AI stack reads business entities published as governed data products in Business Data Cloud, not classic BW objects. Whether modernisation helps with AI depends on whether the chosen path actually publishes the relevant objects as data products, and SAP has not published a date linking BW modernisation status to AI feature availability.
How to confirm your own date in a day
Read the product and release from the system, not from a project document. Check your maintenance agreement for whether the extended phase was purchased and for what period. Then reconcile both against SAP's maintenance schedule for that exact version, through the Product Availability Matrix and the relevant SAP Notes.
The strongest form of this exercise is to ask the customer's basis team to pull the maintenance end themselves and hand it to you. It is their data, it can be checked, and it removes the one claim a sceptic could use to discredit the rest of your analysis.
What we cannot assert
We cannot say whether a given customer holds extended maintenance: it is contractual. The price premium is not public, so no figure is given. We could not open SAP's own announcement page directly (access refused) and relied on three independent readings of it that agree. Our platform news item of 21 April 2026 frames 2030 as a change from 2027; the primary sources date both to April 2020, so this page does not repeat that framing. Embedded BW in S/4HANA and exact per-release dates for BW/4HANA are not stated here and belong in SAP's Product Availability Matrix.
Frequently asked
When does SAP BW 7.5 maintenance end?
Mainstream maintenance for SAP BW 7.5 ends on 31 December 2027. Optional extended maintenance, offered at a price premium, runs to 31 December 2030. Whether you are covered after 2027 depends on your maintenance agreement.
Is SAP BW 7.5 supported after 2030?
No support beyond 2030 has been announced. Anything later would be a new SAP decision, so check SAP's maintenance schedule for your release rather than relying on a third-party page.
Does the 2027 or 2030 date apply to SAP BW/4HANA?
No. SAP aligned BW/4HANA with the S/4HANA maintenance commitment and states it will be maintained until at least 2040, through a sequence of releases. Check the end date of your specific BW/4HANA release in the Product Availability Matrix.
Did SAP extend BW 7.5 maintenance from 2027 to 2030?
Not as a later change that we can source. SAP's April 2020 announcement set mainstream maintenance to 2027 and extended maintenance to 2030 together. Pages that describe 2030 as a move from 2027 are blurring the two phases.
What happens to BW 7.4 and older releases?
SAP ended mainstream maintenance for BW 7.4 and older on 31 December 2020, with no extended option. Those systems sit outside the 2027-to-2030 staircase.
How much does BW 7.5 extended maintenance cost?
SAP does not publish it. The announcement says extended maintenance carries a price premium on the same conditions as Business Suite 7, and the figure is set in your own agreement.
Engage the editor
This guide is written by Cédric Mary, SAP AI & Analytics Architect & Team Lead. 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.
What this page is built on
- SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths
- SAP Business Warehouse (BW)
- SAP BW/4HANA
- BW Bridge: The Migration Arbitration
- SAP BW Data Product Generator — The BW Modernization Path
- SAP Community — SAP NetWeaver 7.5 Maintenance Strategy (consulted 20 October 2026)
- IBsolution — Maintenance for SAP BW 7.5 and SAP BW/4HANA is extended, 23 April 2020 (consulted 20 October 2026)
- SAPinsider — SAP Extends Maintenance for SAP NetWeaver 7.5 and SAP BW/4HANA (consulted 20 October 2026)
- BARC — End of maintenance SAP BW, last edited 10 December 2025 (consulted 20 October 2026)
External sources
- SAP — SAP BW/4HANA to extend maintenance in alignment with SAP Business Suite and SAP S/4HANA (23 April 2020)
- SAP Help — SAP BW/4HANA documentation (maintenance and release info)
- SAP Help — BDC Connect for Databricks
- SAP News — BDC and the autonomous enterprise
- The 3,000-Year-Old Argument: What SAP’s Business Data Cloud Actually Changes — SAP Community (Data Professionals Blog posts)
- Blog 2 - Accelerating SAP BW Modernization: Hands on Experiences with the BDC Data Product Generator — SAP Community (Technology Blog Posts by SAP)
Read next
- SAP AI on premise and in private cloud: what reaches your landscape
- SAP BW End of Support — What Is Actually Ending, and the Four Migration Paths
- SAP BW/4HANA
- SAP BW end of life 2027 — what that date is, and what sits beside it
- SAP BW migration cost — what nobody publishes, and what actually moves the number
- SAP Datasphere vs BW4HANA: stay, convert, or move to Datasphere and BDC
Alert me to new SAP BW/4HANA missions
No account needed. We first ask you to confirm by e-mail; nothing is sent without that confirmation, and every alert has a one-click unsubscribe link. Privacy
Related guides
These guides cite this page as a source.
- SAP AI on premise and private cloud: what reaches you
- SAP BW/4HANA migration 2027: what the date actually is
- SAP BW End of Life 2027: Mainstream, Extended to 2030
- SAP BW modernisation assessment: 4 deliverables to demand
- SAP BW migration options: a decision tree for 2026
- SAP BW private cloud edition: dates, prerequisites, limits
Read next
Pages this one leads to, each answering a question in full:
Open missions
125 live roles and contracts in SAP BW right now — see the SAP BW missions · freelance SAP contracts.