
Meet the Authors
bluetelligence's Metadata API, integrated into WavePath, automates SAP BW migrations to cloud platforms like SAP Datasphere, significantly reducing manual effort and project timelines.
The partnership addresses key migration risks by ensuring accurate metadata extraction and lineage, crucial for seamless transition and avoiding costly post-cutover fixes.
This collaboration highlights the growing trend of multi-vendor solutions in the SAP ecosystem, requiring robust governance for clear accountability across specialized partners.
bluetelligence has entered a strategic partnership with Interdobs and SeaPark Consultancy, placing its Metadata API at the center of WavePath, an AI-powered agent designed to automate migrations from SAP BW to modern cloud platforms, including SAP Datasphere, Snowflake, and Databricks. The arrangement gives bluetelligence a role beyond documentation and cataloging, feeding WavePath the semantic and structural information it needs to reconstruct legacy BW models in a new environment.
How the Metadata API Feeds the WavePath Migration Agent
The Metadata API supplies the semantic and structural information required to execute migrations across complex SAP analytics landscapes. WavePath uses that information to automatically read legacy BW models and regenerate data flows in the target platform, rather than requiring teams to rebuild models by hand. Alexander Dürrstein, CEO of bluetelligence, described the API’s function directly: “Our Metadata API acts as the central nervous system for WavePath. By feeding the AI agent with flawless, automated structural definitions, we enable enterprises to shed technical debt and migrate to modern data platforms faster and safer than ever before.”
bluetelligence states that automating data flow and model generation this way can compress migration timelines from years to months and cut manual effort by as much as 50%. The company also says the approach removes manual copying from the process, preventing transcription errors and producing a more standardized, maintainable architecture on the target side. Organizations using WavePath can choose to remain fully within the SAP Business Data Cloud ecosystem or build hybrid data lakes spanning SAP and non-SAP platforms.
Metadata completeness and lineage accuracy are widely treated as a central risk factor in SAP BW migration projects, since gaps in either often surface only after cutover, when they are far more costly to fix. SAP’s broader push toward the Business Data Cloud reflects an industry-wide move to consolidate analytics and data management under a unified cloud layer, a trend that shapes how migration tooling positions itself relative to SAP’s own roadmap, whether it stays inside that ecosystem or extends into third-party platforms.
bluetelligence’s Position Within a Widening Partner Ecosystem
Founded in 2008 in Wiesbaden, Germany, bluetelligence has built its business around software for documenting, migrating, and cataloging SAP metadata, serving more than 200 customers across Europe. Since 2025, the company has been part of the Theobald Software Group. The WavePath partnership adds a new dimension to that history by pairing bluetelligence’s metadata extraction with two other specialized firms rather than delivering a standalone product.
interdobs, based in Utrecht, Netherlands, and SeaPark Consultancy, based in Dublin, Ireland, round out the arrangement. SeaPark is described as a co-creator of WavePath and a specialist in SAP BW migrations. Ronald Konijnenburg, representing interdobs, framed the combination in terms of what each party contributes: “Migrations traditionally stall during the heavy lifting of recreating data models. WavePath solves this by combining SeaPark’s migration methodologies, our AI-driven agent, and bluetelligence’s stellar extraction capabilities. Together, we turn a daunting architectural hurdle into an automated, predictable journey.”
Cross-vendor partnerships like this are common in the SAP metadata and data catalog space, as firms look to cover more of the migration lifecycle than a single-point solution can address on its own. Supporting multiple non-SAP targets alongside SAP Datasphere also reflects a broader trend among SAP customers toward hybrid data architectures, in which analytics workloads are distributed across more than one cloud platform rather than concentrated in a single vendor’s stack.
What This Means for SAPinsiders
Migration timelines may compress sharply. Teams planning SAP BW modernization should revisit existing project schedules and staffing plans if metadata-driven automation delivers the years-to-months reduction bluetelligence describes. Longer-term roadmaps built around manual remodeling may need reassessment.
Metadata quality becomes a partner selection factor. Organizations evaluating migration vendors should weigh a partner’s metadata extraction and semantic-mapping capabilities alongside target-platform support. A migration agent is only as reliable as the structural information feeding it.
Multi-vendor delivery models require closer governance. As metadata, migration, and AI-agent providers partner across company lines, governance teams should map which firm owns which part of the roadmap and support commitments. Vendor accountability can blur when three companies co-deliver one tool.



