STRATEGY · Jan 2026
Trusted by industry leaders
You don't have to rip out SAP BW to get to Fabric. A migration path that respects existing investments, brings new capabilities online incrementally, and keeps the close cycle running.
This is a working note from the practice — written for senior architects, CDOs and the leadership teams that hire them. The full edition will appear here shortly.
Modernizing SAP analytics in the Microsoft Fabric era touches on patterns we encounter regularly across DACH enterprise engagements. Like most architectural questions, the right answer depends on the organization, the workload and the team — but there are recurring decision points worth naming.
Subscribe to the practice updates below to get the full version when it publishes, or get in touch directly if you'd like to discuss how this applies to your specific situation.
SAP BW has been in production at most large DACH enterprises since the early 2000s. The typical installation we audit has 8–15 years of transformation logic embedded in InfoCubes, DSOs and BEx queries. A complete rip-and-replace migration is not just technically complex — it is politically risky, because finance and controlling teams have built their month-end processes around BW output for over a decade. We have seen three attempted "big bang" migrations fail in the last four years. In each case, the project ran 18–24 months over schedule and was ultimately scaled back to a hybrid state anyway.
SAP's own maintenance roadmap for BW/4HANA runs through 2040. Organizations that have already invested in BW/4HANA migration have a stable foundation. The question is not whether to migrate off SAP, but how to layer modern analytics capabilities on top of it without disrupting the close cycle.
As of Q1 2025, the primary patterns for connecting SAP to Microsoft Fabric are: (1) SAP Connector for Azure Data Factory (mature, production-ready, supports BW Open Hub, ODP, and Direct Extractor Connection). (2) Azure Synapse Link for SAP (currently in preview for S/4HANA Cloud; allows near-real-time delta replication without custom extractors). (3) Third-party connectors: Theobald Software's Xtract Universal and SNP Glue are the dominant choices in DACH, both of which support Fabric as a target. (4) SAP BTP Integration Suite for event-based streaming, useful for high-frequency transactional data.
For most clients running ECC or BW/4HANA on-premises, ADF with ODP extractors remains the most reliable path. It handles delta loads, supports change-data-capture semantics, and the connector is maintained by Microsoft. Extraction throughput averages 2–4 GB/hour per parallel stream — sufficient for most overnight load windows.
The pattern we recommend: keep SAP BW as the authoritative system for existing reports through at least one fiscal year after Fabric goes live. Run both systems in parallel on a shared Golden Record layer in OneLake, with reconciliation checks run nightly. This parallel-run phase — typically 6–9 months — catches the 15–20% of transformation edge cases that are never documented anywhere but in the output of the BEx query itself. Once reconciliation variance falls below 0.1% on all key KPIs for three consecutive months, decommissioning BW becomes a low-risk operational decision rather than a leap of faith.
First conversation is always free.