Migration and modernization at scale

SAP BW migration: the warehouse goes, your data stays

By Xavier Franco, CEO de Elternativa · Grupo Zemsania
· 6 min read

Written with the help of AI and reviewed by Xavier Franco

An old wooden barn half dismantled, with the heap of golden grain left intact under the open sky.
In this article

We talk a lot about SAP ECC and 2027, and rightly so. But in many companies there is another system on the same clock that gets less attention: SAP BW, the data warehouse that feeds the finance, sales and management reports. When ECC moves, BW moves with it. And the decision behind it is more strategic than it looks: where you want your data to live for the next ten years.

What SAP has said

I’ll start with the dates, as SAP published them. In its announcement aligning maintenance with SAP Business Suite and S/4HANA, SAP stated that maintenance of SAP BW 7.5 continues until the end of 2027, with extended maintenance until 2030. And that SAP BW/4HANA is aligned with S/4HANA and will be maintained until at least 2040.

So the path the vendor proposes is clear: move to BW/4HANA or to its cloud offering. It is one option. But, as with ECC, it’s worth comparing it before taking it for granted.

In practice: check which version of BW you have and when your maintenance contract expires. It is the date everything else is measured against.

The warehouse goes, your data stays

Here is the idea that brings the most peace of mind. Migrating BW is not migrating your ERP. ECC or S/4HANA remain the source of the data. What moves is the warehouse: the models, the transformations, the loads and the routines around them.

And the data stays with you. The tables and indicators the business uses today are the reference against which everything new is compared. What changes is where they live and who pays for them.

Three possible destinations

When we plan to take a BW out, there are several paths, and they are not mutually exclusive:

  1. Your data platform. Databricks, Snowflake or Microsoft Fabric, with native SQL and orchestration. SAP data lives alongside the rest of the company’s data and any tool reads it the same way.
  2. SAP Datasphere. If you want to stay in the SAP ecosystem, it is the vendor’s own option.
  3. Custom code for the ABAP routines and the logic that fits no tool.

My preference, when the business doesn’t ask for anything else, is for the data to live where the rest of the company’s data already is. A warehouse isolated from the rest, just for SAP data, made sense twenty years ago. Today, the value is in combining them.

In practice: note which reports today combine BW data with data from outside SAP, and how they do it. If the answer is “with an Excel”, you already have an argument.

What’s inside a BW with some years on it

A BW with a history accumulates everything:

  • process chains that load, every night, data nobody consults any more;
  • duplicate models and cubes, created for a specific report that no longer exists;
  • ABAP routines with business rules only the person who wrote them knows;
  • reports that depend on transformations nobody has documented.

That’s why the first step isn’t choosing a destination. It’s knowing what is used. What feeds nothing isn’t migrated: it’s switched off.

Migrating table by table

Trust in a data warehouse is fragile. If Monday’s sales report shows a different figure, trust in the whole project is lost. That’s why the migration is done like this:

  1. Read-only inventory of models, transformations, loads, routines and schedules: what runs and which table each one feeds.
  2. Classification: what stays, what goes and what is switched off.
  3. Rebuild with orchestrated AI in the chosen destination, validated by your team.
  4. Both chains in parallel, on real data, comparing every target table row by row. Each chain is cut over when it matches, not all at once.

In practice: before approving any BW migration plan, ask how it will be demonstrated that each table holds the same data as today. If there is no concrete answer, there is no plan.

And the reports that read from BW

A BW doesn’t live alone: on top of it there are reports, queries and dashboards that people look at every day. When the warehouse moves, those reports don’t disappear. They start reading from the new destination.

If you already use a modern BI tool, such as Power BI, Tableau or Qlik Sense, it will normally stay the same: only where it reads the data from changes. If your reports live in a tool that also has an end date, such as BusinessObjects, it’s a good moment to plan both migrations together and not do the work twice.

In both cases, the rule is the same as for tables: every new report is compared with today’s, number by number, before the old one is retired. And metrics that today are calculated differently in five reports come to be calculated just once, in the data platform, where any tool reads them the same way.

In practice: pull the list of the ten most-used reports that read from BW. They will be the first to be checked when you migrate.

Separating the two decisions

As with ECC, my advice is to separate two decisions. When and how to convert the ERP is a decision with SAP and its partner. What to do with the warehouse is yours, and you can start it now: taking inventory, switching off what’s surplus and moving a first block to your data platform doesn’t depend on the conversion.

And arriving at the conversion with the warehouse sorted takes pressure off everything else.

Where to start

  1. Confirm your version of BW and the date of your maintenance.
  2. Take inventory of models, loads and routines, with their real usage.
  3. Switch off what feeds nothing.
  4. Choose the destination of each block.
  5. Migrate a first chain with table-by-table comparison and decide the rest on that data.

How we help

In Integration and data platform migration we take out the SAP BW warehouse: models, transformations and loads go to Databricks, Snowflake, Fabric or SAP Datasphere, whichever you choose, and the ABAP routines to custom code. S/4HANA or ECC remain the source of the data. Parity measured table by table, on your real data.

We do it with the Datagentis migration module, which connects read-only, inventories what you have, flags what isn’t used and generates the documentation and the plan before anything is moved.

Frequently asked questions

When does SAP BW maintenance end?

According to SAP, maintenance of SAP BW 7.5 continues until the end of 2027, with extended maintenance until 2030. SAP BW/4HANA will be maintained until at least 2040.

Does migrating SAP BW force you to move to BW/4HANA?

No. It can also go to your data platform (Databricks, Snowflake or Fabric), to SAP Datasphere or to custom code.

Do you have to migrate the ERP as well?

No. ECC or S/4HANA remain the source of the data; what moves out is the warehouse.

How is an SAP BW migration validated?

By running the two load chains in parallel on real data and comparing every target table row by row.

Keep reading