As CTO at SUPERP, I’ve been closely following the BW issue for years. Not as an abstract discussion about platforms, but as a concrete problem faced by the clients our people work with every day. WavePath is the answer to a question we’ve seen coming for some time.
2027 isn’t far off. For SAP BW customers, that means the end of support. And for many organizations, that means a decision they should have already made.
But here’s the honest truth: most organizations don’t know what they have. Not exactly. They know there’s a BW landscape. They know it’s big. They know it contains ABAP code that no one dares touch anymore. But almost no one knows exactly how many objects are actually active, which transformations are critical, and which ones haven’t been used in years. That’s the blind spot. And you can’t make a good platform choice based on a blind spot.
The problem isn’t the technology. It’s the analysis.
Every major migration I’ve been through didn’t hit a snag because of the target architecture. It hit a snag during the preparation phase. That moment when you’ve been working on a project for three months and you realize you’ve underestimated the scope four times over. That there are transformations nobody has documented. That the dependencies go five layers deep and nobody knew that.
That’s where the months and the money go. Not in the implementation, but in the analysis.
WavePath tackles that problem in a way that, to be honest, I haven’t seen work this well before.
The BW Model Extractor connects directly to the source system and retrieves the entire landscape: object inventory, usage frequency, data volumes, transformation logic, ABAP complexity scores, dependency chains. Not filtered by assumptions. Not based on interviews with people who hope their part of the system is well-documented. Simply: what is actually in the system. This delivers something organizations have never had in most BW projects: a factual basis for a decision.
What WavePath does next is the interesting part
Once the landscape has been mapped out, WavePath generates a migration roadmap: a migration plan that uses the actual dependency graph of the BW system as its starting point. No generic template. No estimates based on samples. A plan derived from how your system is actually structured.
And then: data model generation in the target environment. Datasphere, Snowflake, Databricks, or Fabric. WavePath builds the models—including logic and dependencies—entirely automatically based on “rules” and “best practices” generated by BW consultants. As a customer, you might want things done differently, right? No problem there either; the models can be customized by local agents using tools like Claude Code and automatically redeployed.
What Ronald Konijnenberg describes in his LinkedIn post is exactly what I see in practice:
“Which transformations will be the most painful?” Listed by object, with justification.
“Deploy wave one to Datasphere.” CSN generated; objects deployed in order of dependency.
That’s not just the promise of a nice demo. It’s the result of the migration expertise built right into the system. WavePath has been trained on real projects, not on documentation.
Honest about what it doesn’t do
The same level-headed approach I take with the Prior Labs story applies here: this isn’t something you can just push a button and be done with.
Complex ABAP and AMDP routines still require human judgment. Always. No matter how sophisticated the model is, an expert is still needed to validate the output, challenge it, and adjust it where the logic deviates from what the system expects.
What WavePath eliminates:
- The analysis.
- The classification.
- The documentation.
- The model generation.
- The sequence of the deployment.
What remains is the work that requires true expertise. And that is exactly what we stand for.
The hard deadline is not 2027
Ronald mentions this in his post, and I fully agree: the hard deadline is not the end date of SAP support. The hard deadline is the point by which your organization must have made its platform choice, mapped out its landscape, planned its implementation phases, and begun execution in order to be ready by 2027.
For large BW environments, that clock has already started ticking.
| Visible deadline | Actual deadline |
| 2027: End of Support for SAP BW | Next: site selection, landscape analysis, golf course planning, and start of construction |
The technology is here. WavePath is here. And Interdobs and SeaPark have the expertise to guide the process.
The question is whether you’re ready for it.
At SUPERP, we have everything you need to answer that question. Interdobs and SynTouch are part of our group:
- Interdobs is handling the technical migration, as the leading SAP and data expert within our group. With 25 years of experience in BW environments, they know better than anyone what’s actually in a landscape and what it takes to migrate it successfully.
- SynTouch, a leading specialist in data management and organizational maturity.
- Together with SeaPark Consultancy, our international BW migration partner, we cover the entire spectrum: from technical assessments to platform selection to implementation. We don’t offer a one-size-fits-all solution, but rather the honest advice your IT landscape deserves.
