If your BW/4HANA roadmap still says “we’re fine until 2040,” you’ve mixed up two different clocks — and only one of them is actually yours to set.
The clock no one reads closely
Every SAP data leader can recite the BW/4HANA support date from memory: 2040. Far fewer can recite the date that actually governs the next planning cycle. SAP BW 7.5, running on NetWeaver, exits mainstream maintenance on 31 December 2027, with only an optional, cost-escalating extension to end-2030 — priced at a premium of two percentage points on top of the existing maintenance base, the same terms SAP applies across Business Suite 7. These are not the same product and not the same decision. BW/4HANA-s 2040 commitment is real, but it applies to a platform SAP has already told you, in writing, is not where it is investing. Confusing the two dates is the single most expensive planning error we see in data-and-analytics roadmaps right now.
Two dates, one trap
SAP’s maintenance schedule creates a structural illusion of safety. BW 7.5 customers see 2027 looming and reasonably plan a technical conversion to BW/4HANA — a like-for-like move that clears the maintenance cliff without forcing any architectural rethink. BW/4HANA customers see 2040 and reasonably conclude they have a decade of runway. Both groups are right about their date and wrong about what it means. SAP’s Statement of Direction (August 2023) named SAP Datasphere as the strategic successor to BW, shifting from open-ended language to a definitive one. Support to 2040 is a runway for decommissioning, not a mandate to keep building. Every dashboard, transformation, and process chain your team adds to BW/4HANA today is technical debt you will eventually re-platform. The only open question is whether you do it on your terms or SAP’s
Why 2027 forces the real decision now
The mainstream-to-extended step in 2027 is where the trap closes. Organisations still on BW 7.5 face a binary choice well before any comfortable 2040 horizon becomes relevant: convert to BW/4HANA as a bridge, or commit to the cloud target directly. Either path takes 12–24 months of discovery, data-model rationalisation, and testing for a mid-sized landscape — which means the board approving the 2026 budget is effectively making the 2027 call now. Waiting for clarity compresses the runway to a single-digit number of months and forecloses the option to design toward the cloud target instead of merely patching the on-premise one. IOTEK’s position: any BW/4HANA conversion undertaken today without a parallel Datasphere target architecture is a wasted cycle, because you will re-architect the same models twice inside five years.
What actually survives the move
This is where most steering committees underscope. SAP’s BW bridge — the on-ramp from classic BW and BW/4HANA into Datasphere — offers two conversion paths, and neither is a lift-and-shift:
| Conversion path | What moves | Best fit |
|---|---|---|
| Remote conversion | Metadata and data, via a link to the live BW system that stays operational during migration | Landscapes needing minimal downtime and continuous validation |
| Shell conversion | Metadata only, into an empty target; data reloads from source afterwards, objects are rebuilt | Landscapes where a clean, redesigned model is the goal |
Object-level conversion is where the real work lives. InfoCubes and PSA tables become DataStore Objects (advanced); MultiProviders become CompositeProviders; classic DSOs follow the same advanced-DSO path. But this is metadata transformation, not data preservation — query logic, navigation attributes, and read/cache-mode settings all have to be re-modelled on the new objects. None of it is copy-paste; it is a redesign exercise wearing a migration-tool costume. Any team pricing this as a technical lift-and-shift is underscoping it by an order of magnitude.
Business Data Cloud moved the finish line
SAP’s February 2025 launch of SAP Business Data Cloud (BDC) reframes the destination again, and CIOs should stop treating standalone Datasphere as the final target. BDC folds Datasphere, SAP Analytics Cloud, and BW modernisation into one managed SaaS layer, with Datasphere serving as the semantic and knowledge-graph foundation beneath BDC’s insight apps and Joule grounding. The commercial signal is unambiguous: as of 1 January 2026, SAP Datasphere and SAP Analytics Cloud were removed from the list of eligible cloud services for new BTPEA, CPEA, GAnd PAYG subscriptions. Existing tenants are preserved — for no technical migration — but the new commercial path runs through BDC. Practically, an organisation scoping a BW exit in 2026 should target BDC-with-Datasphere-underneath, not Datasphere as a standalone endpoint, or it will face a second re-platforming once BDC’s data-product model matures.
The contrarian read
The consensus advice — “you have until 2040, take your time” — is technically accurate and strategically dangerous. Accurate, because SAP will honour the date. Dangerous, because the decision that actually shapes your data architecture for the next decade is being forced by the 2027 cliff on BW 7.5 and by SAP’s own 2023 Statement of Direction naming Datasphere, not BW/4HANA, as the home for new investment. Every quarter spent treating BW/4HANA as a destination rather than a supported waypoint is a quarter not spent on the harder, more valuable work: rationalising InfoProviders, redesigning MultiProvider logic as CompositeProviders, and building the semantic layer that will actually carry Joule and agentic AI forward.
Practitioner takeaway
Treat 2027, not 2040, as your governing deadline. Use the next two budget cycles to run a shell-conversion pilot on one contained BW domain — a single line-of-business cube-and-DSO chain — into the BW bridge, scoped explicitly against a BDC-plus-Datasphere target, not a BW/4HANA landing zone. If your 2026 plan doesn’t already fund that pilot, you are not deferring the decision. SAP’s maintenance calendar is making it for you.
### Sources – SAP Licensing Experts — SAP BW End of Maintenance 2027: Migration Options: https://saplicensingexperts.com/blog/sap-bw-end-of-maintenance-2027-migration-options – ibsolution — Maintenance for SAP BW 7.5 and SAP BW/4HANA is extended: https://www.ibsolution.com/academy/blog_en/maintenance-for-sap-bw-7-5-and-sap-bw4hana-is-extended – SAP Community — SAP BW/4HANA to extend maintenance in alignment with Business Suite / S/4HANA: https://community.sap.com/t5/technology-blog-posts-by-sap/sap-bw-4hana-to-extend-maintenance-in-alignment-with-sap-business-suite-and/ba-p/13457952 – BARC (Larissa Baier) — End of Maintenance for SAP BW: What’s Next?: https://barc.com/end-of-maintenance-sap-bw/ – SAP Learning — Introducing the Migration from SAP BW to SAP Datasphere (SAP BW bridge): https://learning.sap.com/learning-journeys/modernizing-your-data-warehouse-landscape-from-sap-bw-to-sap-datasphere/introducing-the-migration-from-sap-bw-to-sap-datasphere-sap-bw-bridge – SAP Help — SAP Datasphere BW bridge Conversion Guide (Shell): https://help.sap.com/doc/6467461ba122491da38f00c3e432fdf7/cloud/en-US/SAP_Datasphere_BWbridge_Conversion_Guide_Shell_V1_1.pdf – SAPinsider — Transitioning to SAP Datasphere with SAP BW bridge: https://sapinsider.org/expert-insights/transitioning-to-sap-datasphere-with-sap-bw-bridge/ – SAP Community — Announcement: SAP Datasphere and SAP Analytics Cloud Availability via SAP Business Data Cloud (Jan 2026 eligibility change): https://community.sap.com/t5/technology-blog-posts-by-sap/announcement-sap-datasphere-and-sap-analytics-cloud-availability-via-sap/ba-p/14140920 – SAP News Center — SAP and Databricks: A Bold New Era of Data and AI (BDC launch, Feb 2025): https://news.sap.com/2025/02/sap-databricks-open-bold-new-era-data-ai/