SAP BW 7.5 to BW/4HANA Conversion Checklist

0%

0 of 31 items complete

8 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Assessment

Run SAP Readiness Check for SAP BW/4HANA and review the object and add-on findingsCRITICALRead SAP Note 2383530 (Conversion from SAP BW to SAP BW/4HANA), the central note, and its linked notesCRITICALChoose the path: in-place conversion, remote conversion (new BW/4HANA system) or shell conversion (empty shell, then reload)In-place needs BW 7.5 on SAP HANA at a supported SP; check the minimum SP in the conversion guideList installed add-ons and confirm each has a BW/4HANA compatible version or must be removedList source systems and confirm extraction can run via ODP (SAPI, ABAP CDS, SLT, HANA) since classic S-API without ODP is not supportedInventory custom ABAP in transformations, routines and exits and check it for removed objects

2. Prepare in BW 7.5

Install the SAP BW/4HANA Starter Add-on on BW 7.5CRITICALSwitch system mode with transaction RS_B4HANA_CONVERSION_CONTROL: Compatibility mode, then B4H mode, then Ready for Conversion modeRun the Transfer Cockpit (transaction RSB4HCONV) and its pre-checks to list objects that are not BW/4HANA compatibleCRITICALRemove or replace 3.x data flows (update rules, transfer rules, 3.x DataSources)Delete unused InfoProviders, queries and process chains before transferClean up PSA and change log data so transferred volumes are smallerPlan what happens to BEx Web templates and BEx workbooks, which are not part of BW/4HANA

3. Object transfer

Transfer InfoCubes to DataStore objects (advanced)CRITICALTransfer classic DSOs to DataStore objects (advanced) with the matching modelling propertiesReplace MultiProviders and InfoSets with CompositeProvidersReplace InfoPackages with DTPs reading from ODP based DataSourcesAdjust process chains for removed process types and new objectsCheck BEx queries still run against the new providers and re-test variables and exitsConfirm analysis authorizations (RSECADMIN) cover the new InfoProvidersMove transfers through the landscape with transports in the order the Transfer Cockpit generates

4. System conversion

Build the target stack in Maintenance Planner and download the stack fileCRITICALRun SUM with the BW/4HANA stack (in-place) or install the new system (remote, shell)Run a full trial conversion on a copy of production and record runtimesPerform the post-conversion steps from the conversion guide in order

5. Post-conversion

Reconcile key figures in the main reports against BW 7.5 resultsCRITICALRun every process chain once and confirm delta loads continue without gapsCRITICALReconnect consumers: SAP Analytics Cloud, Analysis for Office and other toolsCompare query runtimes with the old system for the top queriesUpdate operations documentation and monitoring for the new objects

Transaction names and supported paths depend on the BW release, SP and Starter Add-on version. Confirm each step against the current SAP BW/4HANA Conversion Guide and SAP Note 2383530 before you start.

Get your readiness check reviewed

Send us the BW/4HANA readiness check result and we will help you rank the findings by conversion effort.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

BW on HANA versus BW/4HANA

BW 7.5 on HANA is classic BW running on a HANA database: it still supports InfoCubes, classic DSOs, MultiProviders, 3.x flows and BEx Web. BW/4HANA is a separate product that drops those objects in favour of DataStore objects (advanced), CompositeProviders, Open ODS views and ODP based extraction, and runs only on HANA. BW 7.5 has mainstream maintenance to the end of 2027 (check the Product Availability Matrix for any extended maintenance offer), which is why many teams plan the conversion now. The alternative some choose is SAP Datasphere, which is not covered here.

How to use it

Start with group 1 and do not install anything until the readiness check results and the path decision are agreed. The Starter Add-on is the core of an in-place conversion: in Compatibility mode classic objects still run; in B4H mode you can only create BW/4HANA compatible objects; Ready for Conversion confirms the system contains only compatible objects so SUM can convert it. Track object classes in the exported Excel sheet with counts, owners and status.

In-place: same system, keeps history, needs BW 7.5 on HANA.
Remote: new BW/4HANA system, transfer and load data.
Shell: new system with objects only, data reloaded from sources.

Worked example

A plant reporting system has 120 InfoCubes, 300 classic DSOs, 40 MultiProviders and 25 3.x flows. Readiness check flags the 3.x flows and two unsupported add-ons. The team retires 60 unused cubes, rebuilds the 3.x flows as transformations on ODP DataSources, installs the Starter Add-on, and transfers object groups by data flow in the Transfer Cockpit. Only after the system reaches Ready for Conversion mode does Basis schedule the SUM run.

Common mistakes

Transferring everything instead of retiring unused objects first, underestimating BEx Web and workbook replacement, forgetting analysis authorizations on new providers, and assuming every source system extractor works via ODP. Skipping a full trial on a production copy hides the real runtime of large ADSO activations.

Frequently Asked Questions

When does SAP BW 7.5 support end?

SAP has announced mainstream maintenance for SAP BW 7.5 until the end of 2027. Whether an extended maintenance option applies to your contract, and until when, is stated in the SAP Product Availability Matrix and SAP's maintenance announcements; confirm it there before you set the project deadline.

What is the SAP BW/4HANA Starter Add-on?

An add-on for BW 7.5 that prepares an in-place conversion. It introduces the system modes Compatibility, B4H and Ready for Conversion, and delivers the Transfer Cockpit that converts classic objects such as InfoCubes and classic DSOs to DataStore objects (advanced).

Which conversion path should we choose?

In-place keeps the system and history and suits a clean BW 7.5 on HANA. Remote suits a move to new hardware or a cleanup. Shell suits systems where reloading data from sources is acceptable. The readiness check and data volumes usually decide.

Is there an SAP conversion guide for BW/4HANA?

Yes, the SAP BW/4HANA Conversion Guide on help.sap.com, together with SAP Note 2383530 as the central conversion note. Use the guide version that matches your target BW/4HANA release.

If your users want to ask plain English questions about BW/4HANA data on your own servers, we can add a private AI layer once the conversion is stable.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all