SAP Migration Assessment and Hyperscaler Cloud

A structured assessment of your SAP landscape, a costed comparison of every path, and an architecture on AWS, Azure or hybrid that we then build and run.

Book A Consultation
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 assess before we architect.

    Landscape, workloads, dependencies and risks on the table before a single instance is sized.

  2. We model the cost honestly.

    The multi-year cost of each path on AWS, Azure and hybrid, with the risks priced in and the stay-put option included.

  3. We design the landing zone.

    Accounts, networks, identity, backup, monitoring and recovery, built once and built properly before SAP arrives.

  4. We keep the hybrid option open.

    Regulated or latency-sensitive workloads stay where they are. Non-production, integration and analytics tiers move first.

  5. We design recovery in, not on.

    Cross-region replication, recovery targets per tier and a failover that is rehearsed. The cloud gives you the parts, not the plan.

  6. We execute with the people who assessed.

    Rehearsed cutover and hypercare by the same Basis and functional consultants. No handover to a team that has never seen your landscape.

What that looks like in practice

The hosted landscape with a contract deadline

A vendor-hosted S/4HANA landscape had a contract ending and no plan. The assessment sized it on AWS from real workload data rather than the old hardware, and the migration rebuilt replication, monitoring and recovery along the way. The new platform started with controls the old one never had.

The non-production tier that moved first

Rather than move everything at once, sandbox and development went to the cloud first. That proved the network, identity, backups and cost model on systems nobody would miss, so production moved on a path that had already been walked.

The recovery that had been assumed

The assessment found a standby database that had never once been failed over to. The design that followed put recovery targets per system into the architecture and failover rehearsals into the calendar, before the migration rather than after the first incident.

Where SAP cloud migrations go wrong

The same four things, in almost every migration we are asked to rescue.

  • Cloud sizing copied from the on-premise hardware.
  • Business cases with a single scenario in them.
  • Recovery assumed to come with the cloud.
  • Migration partners that leave at cutover.

What the assessment covers

From inventory to the architecture we build and the cutover we run.

Assessment

  • Landscape and workload inventory
  • Custom code and interface inventory
  • SAP Readiness Check and simplification items
  • Dependencies and third-party add-ons
  • Risk register

Cost model

  • Stay on ECC
  • Lift and shift to AWS or Azure
  • System conversion to S/4HANA
  • New implementation
  • Hybrid split by tier
  • Multi-year cost with risks priced in

AWS architecture

  • SAP-certified EC2 instances for HANA
  • VPC and Transit Gateway design
  • AWS landing zone
  • AWS Backup and Elastic Disaster Recovery
  • CloudWatch and Systems Manager

Azure architecture

  • M-series virtual machines for SAP
  • Azure NetApp Files for HANA
  • Entra ID integration
  • Azure landing zone
  • Azure Site Recovery

Recovery

  • HANA System Replication across regions
  • Recovery time and recovery point per tier
  • Failover rehearsals
  • Recovery runbooks

Execution

  • Cutover rehearsal and runbook
  • Go and no-go gates
  • Hypercare by the assessing team
  • Handover into ongoing operation

Signs you need us

  • Your hosting contract ends before your plan starts.
  • The cloud quote was sized from the old hardware.
  • Nobody has priced staying where you are.
  • The last migration partner left at cutover.
Talk to a cloud architect

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

Ask the landscape before you move it

The ETZ AI Platform reads your systems, interfaces and custom code and answers what depends on what, with SAP-grade authorisation and an audit trail on every action.

See the ETZ AI Platform Book a consultation
  • 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)