When BW / BW/4HANA still fits vs when to modernize
Navigate one of the most consequential SAP analytics decisions: when your existing BW or BW/4HANA environment remains operationally sound and aligned with business needs, and when modernization pressure becomes the stronger strategic path. This framework helps you evaluate fit, understand your 5 modernization paths, and plan a realistic transition.
The modernization decision spectrum
The choice is not binary. It exists on a spectrum from "stay and optimize" through phased modernization to full transformation. Your position depends on data volumes, business velocity, skill availability, cloud strategy, and semantic complexity.
Key timelines you should know
- BW 7.5 maintenance: Mainstream maintenance ends December 31, 2027; optional extended maintenance runs to December 31, 2030 at a premium. As SAP BW, private cloud edition in SAP Business Data Cloud, BW 7.5 is covered to the end of 2030, with an optional BDC Modernization Option to December 31, 2033. Older BW 7.x releases left mainstream maintenance at the end of 2020.
- BW/4HANA: SAP committed in 2020 to maintain the BW/4HANA line until at least the end of 2040, through a sequence of releases. BW/4HANA 2021 is in mainstream maintenance to the end of 2027; BW/4HANA 2023, the current release, to the end of 2030.
- Data Product Generator: Available since 2025 for BW running as a private cloud edition in SAP Business Data Cloud. It replicates BW InfoProvider data into the Datasphere object store as data products for SAP Datasphere, SAP Analytics Cloud, SAP Databricks, and SAP Snowflake; the Query Template Generator carries BW queries into Datasphere analytic models.
- Strategic window: With BW 7.5 mainstream maintenance ending in little over a year, BW 7.5 estates should have a decided path now. 2030 is the end of extended maintenance on premise; the 2031–2033 option applies only to BW running in Business Data Cloud.
Your 5 modernization paths at a glance
Not all modernization looks the same. SAP provides distinct paths depending on your architecture goals and operational readiness.
Each path explained
Durations on the cards are indicative ranges, not SAP benchmarks.
Stay & Optimize
Clean up the existing BW 7.5 or BW/4HANA system, simplify data models, and improve governance without moving platforms.
When: Data volumes stable, requirements clear, team skilled, on-premise preferred.
Timeline: 12-24 months optimization; BW 7.5 support to the end of 2027, or to the end of 2030 with extended maintenance.
BW/4HANA
Convert BW 7.5 to SAP BW/4HANA (current release: 2023), the HANA-only BW with a simplified modeling stack. It runs on premise or as SAP BW/4HANA, private cloud edition.
When: You want platform modernization with BW semantics preserved; on-premise or controlled cloud acceptable.
Timeline: 18-36 months conversion; the BW/4HANA line is maintained to at least 2040, with release upgrades along the way.
BW private cloud edition (in BDC)
Lift BW 7.5 (as SAP BW, private cloud edition) or BW/4HANA (as SAP BW/4HANA, private cloud edition) as is into SAP's private cloud inside SAP Business Data Cloud, billed in BDC capacity units. Prerequisites: BW 7.5 SPS 24 or higher on SAP HANA, or BW/4HANA 2021 SP4 or 2023 SP0 and higher; BW 7.5 does not have to be converted first.
When: You want SAP-operated BW without changing objects, more time for BW 7.5 (to 2030, optionally 2033), and access to Path 5.
Timeline: An as-is move first; conversion to BW/4HANA, data products, and redesign can follow at your own pace.
Datasphere (Transform)
Cloud-native semantic layer with unified governance. Redesign data model and consumption.
When: You want cloud-first architecture, agile consumption, semantic redesign, or multi-cloud capability.
Timeline: 24-48 months for full transformation; semantic redesign adds complexity.
Data Product Generator (available since 2025)
Creates subscriptions on BW InfoProviders (InfoObjects, DataStore objects, InfoCubes, CompositeProviders, MultiProviders, queries as InfoProviders) that replicate their data, with semantics and associations, into the Datasphere object store, where it is published as custom data products for SAP Datasphere, SAP Analytics Cloud, SAP Databricks, and SAP Snowflake. It does not convert BW models or transformations; the companion Query Template Generator transfers BW queries into Datasphere analytic models. The BW data is replicated once into the object store; the no-duplication benefit applies to the downstream zero-copy sharing, not the initial extract. It requires BW running as a private cloud edition in Business Data Cloud (Path 3); it is not a standalone, Databricks-only bridge.
When: You want to keep BW running while reusing its data in Business Data Cloud: new models in Datasphere, SAC stories, or ML and AI work in SAP Databricks or SAP Snowflake.
Support: BW/4HANA 2023 SP0+, BW/4HANA 2021 SP4+, NetWeaver 7.50 SP24+
Cost benefit: Replaces custom extraction pipelines from BW with SAP-delivered subscriptions that run in BW process chains, and carries semantics and associations with the data; BW staging logic stays in BW.
BW Bridge (within Path 4)
Convert BW staging content (ODP DataSources including SAP extractors, InfoObjects, advanced DataStore objects, transformations, process chains) into SAP Datasphere, SAP BW bridge. Two modes: remote conversion (metadata + data) or shell conversion (metadata only). Custom ABAP must pass the bridge's cloud ABAP restrictions, and there is no OLAP engine, so BW queries do not run there. SAP still supports the bridge in Business Data Cloud but calls SAP BW, private cloud edition (Path 3) the strategic route.
When: Moving to Datasphere while you still need business content and ECC extractors, or when an on-premise BW system is being decommissioned.
Quick fit assessment
Use this assessment to locate yourself on the modernization spectrum. More "Keep" checks suggest optimization is appropriate. More "Move" checks suggest modernization is justified.
| Assessment Area | Still Fits (Keep) | Modernization Justified (Move) |
|---|---|---|
| Data volumes | Stable or predictable growth; infrastructure manageable | Exponential growth; BW becoming bottleneck; cost per query rising |
| Business velocity | Requirements stable; few new data sources | Rapid change; new data sources constantly; ad-hoc analysis frequent |
| Semantic clarity | Metrics defined; governance clear; ownership understood | Multiple metric definitions; fragmentation across teams; unclear ownership |
| Cloud alignment | Cloud adoption not urgent; on-premise acceptable | Cloud-first strategy; modernization critical for alignment |
| Skill availability | BW expertise strong; recruiting not difficult | BW skills scarce; team wants modern stack; retention at risk |
| Support timeline | BW 7.5 is covered to 2030 (extended maintenance at a premium, or private cloud edition in BDC), and to 2033 in BDC with the Modernization Option | BW 7.5 mainstream maintenance ends December 31, 2027 and there is no funded plan for afterwards; BW/4HANA, the BDC private cloud edition, or Datasphere needed |
How to use this assessment
Count your "Keep" and "Move" checks. More "Keep" checks suggest you stay and optimize. More "Move" checks suggest you modernize. But the narrative matters more than the score—a single high-impact factor (like skill scarcity or cloud strategy) can outweigh several low-impact ones.
Common outcome patterns
Stay & Optimize
Your BW environment is serving well. Focus on incremental improvements: cleanup, governance maturity, skill development.
Action: Define a 3-5 year optimization roadmap. Review fit annually as context changes. Add SAC or Datasphere for new consumption needs as they emerge.
Plan Modernization
The case for modernization is strong. Develop a transition strategy now.
Action: Define target platform (BW/4HANA, Datasphere, or hybrid). Map workload waves. Plan 18-36 month coexistence, not instant cutover. Budget for retraining and consulting.
Hybrid Coexistence
You have areas where BW still fits (mature reporting) and areas where modernization is justified (new analytics).
Action: Keep stable BW workloads. Modernize new use cases to Datasphere or cloud. This phased approach reduces risk and lets you learn before committing fully.
Cost and risk profile by path
Path 1: Stay & Optimize
Cost: Low upfront; moderate ongoing (infrastructure, support, staff). Invisible costs accumulate.
Risk: Skills become scarcer over time. Agility decreases. Post-2027 you face harder modernization with more technical debt.
Best for: Stable environments with predictable requirements and strong BW expertise already in place.
Paths 2 & 3: BW/4HANA and private cloud edition
Cost: High upfront for a BW/4HANA conversion (migration, retraining); an as-is lift into the BDC private cloud edition avoids conversion effort. Ongoing: licenses, or BDC capacity units for the private cloud edition. Whether total cost ends up below staying depends on the estate.
Risk: Migration complexity; skills transition; performance regression possible. But the BW/4HANA line is maintained to at least 2040, with release upgrades.
Best for: Organizations keeping BW semantics but wanting in-memory platform, cloud, or extended support horizon.
Path 4: Datasphere
Cost: Highest upfront (redesign, new tools, retraining). Moderate ongoing (cloud infrastructure, platform). Enables agility payoff.
Risk: Semantic redesign complex; change management heavy. Requires governance clarity. Longer timeline.
Best for: Organizations wanting cloud-native, multi-tool, agile analytics with redesigned governance.
Path 5: Data Product Generator
Cost: BW as a private cloud edition in BDC plus object-store capacity, both in BDC capacity units; SAP Databricks is optional. Usually lower than a full redesign, because BW keeps running.
Risk: Newer capability (available since 2025); requires a Business Data Cloud subscription (Databricks consumption is optional, not mandatory). It moves data, not logic: transformations still need redesign if you later retire BW.
Best for: Organizations wanting to keep BW logic in place while reusing BW data across Business Data Cloud.
Migration strategy: big-bang vs phased vs hybrid
Big-Bang Migration
What: Move entire environment at once.
Works when: Small, simple environments; high risk tolerance; clear cutoff date.
Fails when: Large, complex environments; hidden dependencies discovered late; scope underestimated.
Outcome: Fast if successful. Catastrophic if it fails.
Phased Migration
What: Move workloads in waves; run both systems in parallel; retire gradually.
Works when: Large, complex environments; multiple teams; complex dependencies.
Fails when: Takes much longer than planned; cost spirals; coexistence becomes permanent debt.
Outcome: Lower risk. Higher total cost. More manageable.
Hybrid Migration (Recommended)
What: Big-bang for some workloads; phased for others.
Works when: Most real organizations; allows speed where possible, care where needed.
Fails when: Adds complexity; requires clear communication about which path applies where.
Outcome: Realistic balance between speed and risk.
Illustrative example: hybrid approach for a global enterprise
Consider a global manufacturer with 150+ InfoCubes and 300+ active users that splits its estate three ways (an illustration, not a client case):
- Big-bang (6 months): Financial reporting InfoProviders (15 objects, high governance, stable requirements) move to BW/4HANA in one cutover.
- Phased (18 months): Supply chain and manufacturing InfoProviders (80 objects, complex dependencies, frequent model changes) move in four waves: procurement, production, logistics, finished goods. Each wave runs in parallel with BW for several weeks before the old objects are retired.
- Deferred (24+ months): Ad-hoc analytics InfoProviders (55 objects, low usage, unclear owners) stay on BW 7.5 until ownership is clear, or are retired.
The point of the split: governed reporting with stable requirements moves early, complex domains move with parallel runs, and low-value content waits or is retired, instead of one timeline for everything. Budget the coexistence period explicitly; it is the price of lower risk.
Detailed phased migration approach for Datasphere/BDC
If you choose Path 4 (Datasphere transform), phased migration is more complex because you're redesigning semantic models, not just upgrading platforms. The key is establishing parallel semantics—both old (BW) and new (Datasphere) running side-by-side with reconciliation gates.
Phase 1: Discovery & Semantic Redesign (Months 1-4)
- Inventory BW objects: Catalog all InfoObjects, InfoCubes, ADSOs, MultiProviders, and Queries. Map dependencies and identify high-value, high-reuse objects (customers, products, financials).
- Semantic assessment: Do BW models match current business semantics, or have business definitions evolved? Datasphere migration is an opportunity to align models to current business reality.
- Baseline usage: Track dashboard, report, and query execution counts. Identify low-usage objects that can be archived rather than migrated.
- Pilot redesign: Choose one high-value, stable domain (often finance customer data or product hierarchy). Design Datasphere models from scratch, not as BW-for-BW translations. Pilot with 2-3 consuming teams. Iterate until satisfaction.
- Estimate scope: Based on the pilot, extrapolate the full migration effort. Split it into semantic redesign, data transformation, consumption migration, and governance setup, and size each from what the pilot showed.
Phase 2: Build & Validate (Months 5-10)
- Create Datasphere semantics: Build Datasphere models for domains prioritized in Phase 1. Use SAP BW bridge if you must keep extractor-based staging; use the Data Product Generator (with BW as a private cloud edition in BDC) to publish BW data as data products for Datasphere, SAP Databricks, or SAP Snowflake while the redesign proceeds.
- Data reconciliation: Establish data validation between BW and Datasphere. Do revenue numbers match? Are customer counts the same? Agree tolerance bands per measure with the business owners before the first cutover.
- Parallel consumption: Build SAC/BI dashboards on Datasphere models in parallel with existing BW reports. For several weeks, ideally across at least one month-end close, both versions run side by side. Business users validate that Datasphere numbers are trustworthy.
- Consume with data products: If using BDC, publish curated Datasphere content as custom data products in the catalog, with named owners and the data product governance settings added in 2026 (terms and conditions, steward approval, access agreements).
- Governance go-live: Once parallel validation succeeds, flip primary consumption to Datasphere. Retire BW reports for that domain.
Phase 3: Expand & Optimize (Months 11-18)
- Wave-based rollout: Repeat Phase 2 for domains 2-4 in parallel waves. Don't wait for domain 1 to finish before starting domain 2 design.
- Consumption migration: Train analysts on Datasphere/SAC. Retire BW workspaces as consumption migrates. Archive BW queries and reports in a document repository for audit trail.
- Integrate with AI: As Datasphere analytic models stabilize, make them available to just ask in SAP Analytics Cloud and to analytical insights in Joule (powered by just ask; admins index the Datasphere analytic models), so business users can ask questions in natural language on governed semantics.
- Plan zero-copy sharing: If using BDC Connect, set up the connection to Databricks, Snowflake, or Google BigQuery (all generally available; Microsoft Fabric in public preview) and share high-value data products zero-copy for external consumption.
Phase 4: Retire & Optimize (Months 19-24+)
- Retire BW infrastructure: Once all critical domains are migrated and stabilized (18-24 months in this plan), decommission BW systems. Preserve data export for audit compliance.
- Performance tuning: Optimize Datasphere query performance, caching, and aggregation strategies based on 6+ months of usage patterns.
- Expand data products: Systematize data product creation. Establish stewardship model. Plan which SAP-managed data products and intelligent content can replace custom flows, and where master data from SAP Reltio (now generally available in BDC) fits.
- Governance maturity: Establish lineage, data quality metrics, and automated compliance reporting. Make governance self-service via the catalog.
Key success factors for phased migration
- Establish reconciliation gates: Every domain cutover requires validated reconciliation (numbers match within tolerance). Don't cutover until confidence is high.
- Run in parallel across at least one month-end close: Mismatches tend to surface during parallel validation, and time pressure breaks reconciliation rigor.
- Assign clear domain ownership: Each migration wave needs a dedicated owner responsible for validation, training, and retirement of legacy reports.
- Invest in data quality early: Datasphere will inherit BW data quality issues. Fix source system data quality before or during Phase 1, not as an afterthought.
- Communicate progress visibly: A phased program like this runs 18-24 months or longer. Teams lose confidence without visible progress. Track and communicate: % of users migrated, % of reports retired, % of objects redesigned.
- Plan for coexistence cost: Running BW and Datasphere in parallel for 12-18 months adds infrastructure and operations cost. Budget for it explicitly: it is the cost of safety, not waste.
Timeline and support horizon
Your platform choice determines when you must act and how long you have to operate without change.
When each path makes sense
Path 1: Stay & Optimize
When: Data volumes stable, requirements clear, team expertise strong, cloud not urgent, growth predictable.
Decision by: Now for BW 7.5 (mainstream maintenance ends December 31, 2027)
Timeline: 12-24 months optimization; BW 7.5 support to 2030 with extended maintenance or the BDC private cloud edition.
Paths 2 & 3: BW/4HANA and private cloud edition
When: You want to keep BW semantics, either modernized on BW/4HANA (in-memory, simplified objects) or lifted as is into SAP-operated private cloud inside Business Data Cloud.
Decision by: 2026-2027, before BW 7.5 mainstream maintenance ends
Timeline: 18-36 months for a BW/4HANA conversion; a lift into the BDC private cloud edition moves BW as is. The BW/4HANA line runs to at least 2040.
Path 4: Datasphere
When: You need cloud-native, agile, multi-tool ecosystem, semantic redesign, or complete governance overhaul.
Decision by: 2026-2027, before BW 7.5 mainstream maintenance ends
Timeline: 24-48 months transformation; plan for SAP BW bridge if you must keep extractor-based staging.
Path 5: Data Product Generator
When: You want to reuse BW data in Business Data Cloud (Datasphere, SAC, SAP Databricks, SAP Snowflake) without a full migration.
Available: Since 2025, for BW as a private cloud edition in BDC
Supported versions: BW/4HANA 2023 SP0+, BW/4HANA 2021 SP4+, NetWeaver 7.50 SP24+
Key decision criteria summary
Choose Stay & Optimize if:
- Data volumes and requirements are stable or grow predictably
- BW team expertise is strong and you can recruit additional resources
- Governance is clear and enforced
- On-premise infrastructure is acceptable
- You have capacity to optimize until 2030
Choose BW/4HANA if:
- You want to preserve BW semantics and data models
- In-memory performance and a simplified, HANA-only BW stack matter
- You want a product line SAP maintains to at least 2040, with release upgrades
- You are willing to invest in migration and retraining
- On-premise or private cloud acceptable
Choose Datasphere if:
- Cloud-first strategy is non-negotiable
- You need agile, multi-tool consumption patterns
- Semantic redesign is acceptable (even desirable)
- You want unified governance across data, semantics, and consumption
- You can invest 24-48 months in transformation
Choose the Business Data Cloud route (Paths 3 + 5) if:
- You want SAP to operate BW without converting objects first
- BW data should feed Datasphere, SAC, SAP Databricks, or SAP Snowflake as data products
- BW 7.5 needs coverage beyond 2027 while you modernize (to 2030, optionally to 2033)
- A Business Data Cloud subscription in capacity units fits your licensing
- You accept that transformations and queries still need redesign over time
What to evaluate next
Related comparisons and frameworks
From modernization decision to execution
Trust and provenance note
This page is an editorial decision framework, not an SAP product directive. Timelines, support windows, and platform capabilities reflect SAP's published information as of November 2026. Verify product details, support timelines, and feature availability with official SAP documentation and your SAP partner before making commitment decisions.