SAP Migration, Upgrade and Conversion

S/4HANA upgrades, system conversions and SAP cloud migrations, tested by the people who run the processes and supported through the first close.

GlueData
Sanlam
Wastepro
FINN
Southco
OSIsoft
Sports Basement
SALT Analytics
AME Africa
Lock & Stern
ClearOn
WEG
Savantis
Sanquin
Hua Hai Pharma
Rumpke
GlueData
Sanlam
Wastepro
FINN
Southco
OSIsoft
Sports Basement
SALT Analytics
AME Africa
Lock & Stern
ClearOn
WEG
Savantis
Sanquin
Hua Hai Pharma
Rumpke

What we do

  1. We plan the upgrade around month-end.

    Sandbox, QA and production windows agreed with finance, never across a close.

  2. We test with the people who run the processes.

    Payment runs, asset transfers, journal uploads and Fiori tiles, tested by the business in sandbox and QA, with us beside them.

  3. We move the data, and prove it.

    SAP data migration with the Migration Cockpit and LSMW, reconciled to the source before anyone signs off cutover.

  4. We rehearse the cutover.

    Transports, interface restarts and post-copy steps on one checklist, run in rehearsal before the real weekend.

  5. We stay through the first close.

    Hypercare ends when month-end has run on the new release, not when the project plan says so.

  6. We move SAP to the cloud without losing the plot.

    From hosted or on-premise to AWS or Azure. Lift and shift, system conversion or selective transition, chosen for your landscape rather than ours.

What that looks like in practice

The tiles that worked some of the time

During QA testing of an upgrade, a journal-entry tile worked on some attempts and not others. We traced it to a mismatch between the UI library on the front end and the back end. It was patched before go-live, which is the only time that fix is cheap.

The allocation that changed its mind

In the first month on a new release, a cost allocation cycle posted to a different functional area than it had for years. A user exit had been altered by the upgrade. We corrected it, tested it in QA and took it through the change board before the next close.

The hosted system that moved to AWS

An S/4HANA landscape moved from a vendor-hosted cloud to AWS. Replication, recovery documentation and monitoring were rebuilt as part of the move, so the new platform started with the controls the old one never had.

Where SAP upgrades go wrong

The same four things, on almost every upgrade we are called into.

  • Upgrades tested by IT and never by finance.
  • Cutover weekends without a rehearsal.
  • Hypercare that ends on a date, not on a month-end.
  • Custom code and user exits nobody checked against the new release.

Paths and tooling

Every route we take a landscape down, and what we use on the way.

Upgrades

  • S/4HANA release upgrades
  • Feature packs and support packs
  • Fiori front-end upgrades
  • SAP HANA revision updates
  • SAP Readiness Check
  • Simplification item check
  • Custom code check (ATC)

Conversion and migration paths

  • ECC to S/4HANA system conversion
  • New implementation
  • Selective data transition
  • SAP Migration Cockpit and LSMW
  • Business Partner conversion (CVI)
  • New Asset Accounting migration
  • Data cleansing and archiving

Cloud migration

  • Hosted SAP to AWS
  • On-premise to AWS or Azure
  • SAP HANA database migration
  • Cloud Connector and BTP reconnection
  • Interface re-pointing and certificates
  • Replication and recovery rebuilt on the new platform

Testing and cutover

  • Sandbox and QA test cycles
  • Cutover rehearsal and runbook
  • Transport sequencing
  • Interface restart checklist
  • Analytics reload coordination
  • Hypercare through the first close

Signs you need us

  • The upgrade date is set and finance has not seen a sandbox.
  • Nobody has listed the custom code the new release touches.
  • Your hosting contract ends before your migration plan starts.
  • The last upgrade’s issues are still open.
Talk to a migration consultant

You can find us here

We have a strong global presence, marking our commitment to delivering tech excellence in key markets worldwide.

Colorado
14133 Downing Street Brighton,
Colorado 80602
Contact us
Cape Town
Regus Business Center, 1st Floor,
Willowbridge, Cape Town
Contact us
Haarlem
Frame Offices B.V.,
Haarlem, Netherlands
Contact us

Know what the upgrade will break before it does

The ETZ AI Platform reads your custom code, configuration and interfaces and explains what the new release touches, with SAP-grade authorisation and an audit trail on every action.

  • Runs in your own SAP BTP subaccount. SAP data never transits ETZ.
  • Your SAP authorisations decide what it may see and do, not the AI.
  • Every action lands on an append-only audit record.
Available on the SAP Store (opens in a new tab)