Back to overview
Skillset

Migrations & Upgrades

Moving landscapes forward without losing a day of reporting — release upgrades, BW/4HANA conversions and the road to S/4HANA, BDC and DataSphere.

BW/4HANA conversionRelease upgradesS/4HANABDCDataSphereCutover planning
BW 3.xclassic · 3.0B–3.5 BI 7.x7.0–7.5 on HANA BW/4HANAconversion · rebuild BDC · DATASPHEREcloud target architecture S/4HANAnew source system every hop executed in production — upgrade, convert, re-platform
One continuous path: every generation of SAP BI, migrated in production.
01

Strategy before tooling

Greenfield, brownfield or shell conversion — the right approach depends on data quality, custom code and the business appetite for change. I assess the landscape first and let the findings pick the strategy, not the other way around.

02

De-risked by design

Parallel runs, automated reconciliation reports and a rehearsed cutover plan: migrations are won in the preparation. Business users should notice the improvement — not the migration.

03

The cloud horizon

The current chapter: aligning the move to S/4HANA as the new source system, the upgrade to SAP Business Data Cloud and the preparation of the DataSphere migration — several tracks, one consistent target architecture.

04

In practice

The most recent — and perhaps most important — chapter: the migration to SAP Business Data Cloud (BDC) at Sandoz, which I am aligning and driving today. Before that: function-identical BW upgrade at Fővárosi Vízművek (3.1 → 7.0); upgrade and extension at Coop Hungary (3.0B → 3.5); complete BW/4HANA rebuild at Palkeet with aDSOs and CompositeProviders; consolidation of divisional warehouses into the Novartis group data warehouse.

Discuss your project All skills