Services / Cloud Infrastructure / Migrate & Modernise
Cloud Infrastructure · Migrate & Modernise

Move SAP ECC and S/4HANA to the cloud, without stopping the business.

We move SAP ECC, S/4HANA on-premise and older SAP landscapes onto SAP HANA certified infrastructure on AWS, Microsoft Azure or Google Cloud. You leave ageing hardware behind, get a landscape that is ready for S/4HANA, and keep full control of the systems you run.

Talk to a cloud architect →See how it works
2027End of mainstream maintenance for SAP ECC 6.0 EHP 6 to 8
2030Last year of optional extended maintenance for ECC
2040SAP maintenance commitment for SAP S/4HANA
Why it matters

Why move SAP to the cloud now

SAP has set clear dates. Mainstream maintenance for SAP Business Suite 7 core applications, including ECC 6.0 on enhancement packages 6 to 8, ends at the end of 2027, with optional extended maintenance to the end of 2030 at a higher maintenance fee. Older enhancement packages are already outside mainstream maintenance. At the same time, on-premise hardware refreshes, data centre contracts and SAP Process Orchestration timelines are arriving together. Moving the current landscape to the cloud first removes the hardware problem and gives you a cleaner base for the move to S/4HANA.

Hardware and data centre pressure

Replacing ageing SAP servers and storage locks you into another multi-year cycle. Cloud infrastructure lets you size for today and change size later.

A stepping stone to S/4HANA

S/4HANA runs only on SAP HANA. Moving ECC onto HANA certified cloud infrastructure now shortens the later conversion and lets you test it on copies of production.

Integration timelines too

Mainstream maintenance for SAP Process Orchestration 7.5 also ends in 2027. Planning the infrastructure move and the integration move together avoids doing the work twice.

Environments on demand

Sandbox, project and test copies can be built when needed and switched off afterwards, which is hard to do on fixed on-premise hardware.

What we do

What we do

We plan, migrate and stabilise SAP landscapes on the hyperscaler that fits your business.

01

Landscape assessment

We review your SAP systems, versions, databases, interfaces, sizes and add-ons. You get a clear view of what can move as is and what needs to change first.

02

Target architecture

We design the cloud landscape on SAP HANA certified instance types, with high availability, backup, network and security built in. The design follows SAP and hyperscaler reference architectures.

03

Lift and shift

Where the operating system and database stay the same, we move systems with a homogeneous system copy or replication. This is the fastest path with the fewest changes.

04

OS and database migration

We move from AIX, HP-UX, Solaris, Oracle, SQL Server or DB2 to Linux and SAP HANA using SAP tools such as Software Update Manager with Database Migration Option. You land on a platform that is ready for S/4HANA.

05

S/4HANA readiness

We can combine the move with preparation work: custom code checks, data volume reduction and a plan for the later S/4HANA conversion. Some customers convert during the move itself.

06

Cutover and hypercare

We rehearse the cutover on copies, agree a downtime window with the business and support you closely in the weeks after go-live.

How it works

How it works

  1. 1

    Discover and decide

    We collect system data, sizing and interface lists, then agree the target cloud, region and migration path. You get a migration plan with risks and options.

    2 to 4 weeks
  2. 2

    Build the landing zone

    We set up accounts or subscriptions, networks, connectivity to your offices, identity and security controls. SAP infrastructure is built with automation so it can be repeated.

    2 to 4 weeks
  3. 3

    Migrate non-production

    Sandbox, development and quality systems move first. Each move is a rehearsal that tunes the runbook and measures downtime.

    4 to 8 weeks
  4. 4

    Migrate production

    We run the production cutover in an agreed window, validate with business users and switch interfaces over. Rollback options are prepared in advance.

    1 weekend per system
  5. 5

    Stabilise and hand over

    We tune performance, confirm backup and recovery, and hand over to your team or to our managed operations service.

    2 to 4 weeks
Across AWS, Azure and Google Cloud

SAP on each cloud

Native services we use for self-managed SAP on AWS, Microsoft Azure and Google Cloud.

NeedAWSMicrosoft AzureGoogle Cloud
SAP HANA certified computeAmazon EC2 memory optimised and High Memory U7i instancesAzure M-series virtual machinesCompute Engine M-series and X4 machine types
Guided SAP deployment and checksAWS Launch Wizard for SAPAzure Center for SAP solutionsWorkload Manager with Google Cloud's Agent for SAP
SAP aware operationsAWS Systems Manager for SAPAzure Monitor for SAP solutionsGoogle Cloud's Agent for SAP with Cloud Monitoring
SAP HANA backupAWS Backup for SAP HANAAzure Backup for SAP HANABackup and DR Service
Rehost surrounding serversAWS Transform MGNAzure MigrateMigrate to Virtual Machines
Private connection to the cloudAWS Direct ConnectAzure ExpressRouteCloud Interconnect
For SAP landscapes

Self-managed SAP or RISE with SAP

This service is for SAP you run yourself on the cloud, sometimes called bring your own licence. You keep your SAP licences, and you, with us, run the virtual machines, operating system, database and SAP Basis. That is different from RISE with SAP, where SAP runs the infrastructure on a hyperscaler and you do not manage the virtual machines. Both are valid paths. Many customers move ECC to the cloud first to leave the data centre, then choose between a self-managed S/4HANA conversion and a move to SAP Cloud ERP Private under RISE with SAP.

  • ECC 6.0 on EHP 6 to 8 keeps mainstream maintenance until the end of 2027, with optional extended maintenance to the end of 2030.
  • SAP has committed to maintain SAP S/4HANA until the end of 2040.
  • Under self-managed SAP on the cloud, the customer remains responsible for the systems, patches and SAP support compliance, so we design for that from the start.
  • If RISE with SAP is the better fit, we help you choose the cloud and region and connect it to the rest of your estate.

© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice

What you get

Deliverables

  • SAP landscape assessment and migration plan
  • Target cloud architecture on SAP HANA certified infrastructure
  • Landing zone with network, identity and security controls
  • Tested migration runbooks and cutover plan
  • Migrated SAP systems with backup, recovery and monitoring in place
  • Handover pack and S/4HANA readiness recommendations
Questions

Frequently asked

When does support for SAP ECC end?

SAP provides mainstream maintenance for SAP Business Suite 7 core applications, including ECC 6.0 on enhancement packages 6 to 8, until the end of 2027. Optional extended maintenance runs to the end of 2030 at a higher fee. Customers who do not take it move to customer-specific maintenance.

Should we move ECC to the cloud or go straight to S/4HANA?

It depends on your hardware dates, project capacity and how much change the business can absorb. Moving ECC first removes the infrastructure deadline and can include the move to SAP HANA, which shortens the later S/4HANA conversion. Going straight to S/4HANA avoids a second project but takes longer to start.

Can we change the database and operating system during the move?

Yes. An OS and database migration from Oracle, SQL Server, DB2, AIX, HP-UX or Solaris to Linux and SAP HANA is a common part of the move. SAP tools such as Software Update Manager with Database Migration Option are designed for this.

Which cloud is best for SAP?

AWS, Microsoft Azure and Google Cloud all offer SAP HANA certified infrastructure and SAP support. The right choice depends on your existing contracts, skills, nearby regions, and the other applications you run. We compare them on your actual requirements.

How long will the business be down?

Downtime depends on database size, the migration method and the network. We measure it during rehearsals on non-production systems and agree a production window with you before the cutover, usually over a weekend.

Related services

Often paired with this

Migrate & ModerniseRISE with SAP: Cloud & Region Choice→Run & OptimiseHigh Availability, DR & Backup→Advise & PlanBusiness Case & TCO→
Next step

Plan your move with people who know SAP.

One working session with our cloud and SAP architects. You leave with the options, the risks and a first plan.

  • Your landscape reviewed
  • The right cloud and region
  • A first roadmap
Sources

At Mawkish, the Corwell Method is how we keep SAP ECC & S/4HANA to the Cloud work checked, owned and answered for, whoever does the build.

AWS, Microsoft Azure, Google Cloud and SAP are trademarks of their respective owners.

© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice