SAP BW End of Life 2027: Your migration path to Microsoft Fabric

Unlike the traditional 'lift-and-shift' approach, it is not possible to simply transfer data models, transformations, and ABAP-based logic to Microsoft Fabric. Instead, the analysis and evaluation of existing data structures, processes, and business logic is required to rebuild them for a modern data architecture.

Before migration: Rethinking the architecture

It can be helpful to fundamentally question the existing data architecture and rethink it as part of the migration process, before analysing the technical solution. A Data Strategy Assessment from Cosmo Consult can provide a potential starting point for this process. This ensures that the analysis does not rely exclusively on the structures of the existing SAP BW solution, but instead begins by examining the overarching data strategy, as well as the specific business and technical data requirements.

Based on this, it is possible to evaluate

• which existing components are still needed,
• which logic should be modernised or redeveloped,
• and what a future-proof Microsoft Fabric architecture might look like.

This creates an opportunity to avoid unthinkingly carrying over legacy technical burdens, and to align the target architecture specifically with future requirements instead.

How can I import my SAP data into Microsoft Fabric?

Microsoft Fabric offers modern integration approaches to make SAP data available.

• It uses native SAP connectors and replication scenarios to connect SAP S/4HANA, ECC and other source systems.
• It also offers near real-time data integration via replication or Change Data Capture (CDC), which efficiently makes data changes available in Fabric.
• Existing business logic can be reused via CDS views and other SAP artefacts where this makes business and technical sense.

This enables the retention of some existing logic while simultaneously creating a future-proof architecture.

What is a Lakehouse Architecture Based on the Medallion Principle?

Instead of the traditional BW layers, Fabric typically employs a Lakehouse architecture based on the Medallion principle:

• Bronze: Raw data from SAP and other source systems
• Silver: Cleaned and harmonized data
• Gold: Business models, KPIs, and reporting structures

This ensures transparency, better data quality, and maximum flexibility for analytics and AI applications.

What happens to my ABAP code and the transformations?

A key part of the BW replacement involves redeveloping existing transformations.

Typical technologies in Fabric include:

• SQL and Spark
• Data pipelines
• Notebooks

Existing ABAP logic is analyzed, migrated to modern technologies, and often simplified or optimized at the same time. AI can support this process, but business validation remains essential.

Where will my key metrics be in the future?

Key metrics, hierarchies, and calculations are no longer embedded in the BW system but are instead provided in semantic models.

This enables:

• Consistent KPI definitions
• Greater reusability
• Self-service analytics for business units through direct access to standardized, business-defined models
• Consistent analyses across all reports

How do I ensure governance and compliance in Fabric?

As new possibilities emerge, so do increased demands on governance and security.

Key topics include:

• Internal corporate governance guidelines
• Role and permission models
• Data protection and compliance

These aspects should not be considered as an afterthought but should be an integral part of the target architecture.