August 20, 2026
What this webinar is about
Mainstream maintenance for SAP BW 7.5 ends at the close of 2027, so an SAP BW to Datasphere move is no longer a question of whether. There are ways to buy time — extended maintenance to 2030, or lifting the system into private cloud — but none of them change what eventually has to happen, and none of them answer the harder question: what are you actually moving?
Most BW landscapes are fifteen years of decisions nobody wrote down. Queries and providers built by people who have since left. Dataflows reconstructed in workshops from memory. No reliable record of what anyone still runs. Scope ends up set by whoever argues hardest, and a steering committee is asked to approve a number nobody can defend.
So we built something. The PlaniFi Migration Accelerator for SAP BW connects to your BW system read-only, takes inventory of what is genuinely there, shows what still gets used and what depends on what — then generates your first SAP Datasphere models from that same metadata. Ingo Hilgefort walks through it end to end.
If you are still weighing the options, our piece on the practical modernization path from SAP BW to SAP Business Data Cloud covers the strategic choices. This session is narrower and more concrete: what is actually in your landscape, and what a generated target looks like.
What you will learn about SAP BW to Datasphere migration
- How one read-only scan produces a complete, correctly typed object inventory — and separates what your team built from what SAP delivered
- Why usage recency changes the scope conversation: queries bucketed by how long since they were last used, with retirement candidates flagged before anyone budgets to rebuild them
- How directional lineage answers “what breaks if we drop this?” in seconds — upstream and downstream, at whatever depth you need
- What generated SAP Datasphere output actually looks like: local tables, dimension and fact views, and analytical models carrying your restricted and calculated key figures across as measures
- Why every generation run reports its assumptions and gaps instead of silently defaulting them
What an SAP BW to Datasphere scan is worth
For a mid-size BW 7.5 landscape — roughly 2,000 objects and 400 queries — here is what removing the manual discovery pass is modelled to be worth:
| 80–140 consultant-days saved | Discovery, lineage and documentation stop being manual passes over the landscape. |
| $100K–$170K avoided project cost | At a $1,200 blended day rate, before any reduction in rebuild scope. |
| 20–40% retired, not rebuilt | Queries with no recent use are identified up front, so they are never carried into the new platform. |
| weeks → hours to a defensible scope | One scan replaces the workshop cycle that scoping normally depends on. |
Modelled estimate for a mid-size BW 7.5 landscape (~2,000 objects / ~400 queries) at a $1,200 blended day rate. Not a measured result — your figures depend on landscape size and complexity.
Who should attend
- SAP BW developers and data modellers
- Enterprise and data architects planning an SAP Datasphere or SAP Business Data Cloud move
- BI and analytics leads who own the BW estate
- IT leaders accountable for the 2027 decision
- Basis and security teams who have to approve anything that touches production
Why attend this SAP BW to Datasphere session
Scoping is the long pole of a BW migration, and it happens before the budget is even approved — usually on the least evidence anyone will have. Forty-five minutes here shows you what it looks like when that scope is set from a scan instead of a workshop, and what a first SAP Datasphere build looks like when it is generated rather than typed. Nothing is installed in BW to do it: no transports, no agents, no add-ons.
Your speaker
Senior Director SAP Business Data Cloud at SimpleFi
Register Now!
August 20th, 2026, 11AM CST
Duration: 45 Min
Register with your business email address to avoid issues when logging into the event platform
Please see which webinars you have missed on our OnDemand Channel