Cloudstok
SAP on AWS

Move SAP to AWS before the 2027 deadline.

Cloudstok plans and runs SAP migrations to AWS — RISE with SAP, S/4HANA on your own AWS account, or ECC moved as-is — with AWS funding lined up before the build starts.

Compare the three pathsGet a readiness assessment
ECC mainstream support ends
Dec 2027
RISE with SAP on AWS SLA
99.95%
AWS credits back
Up to 65%
SAP-certified HANA memory
32 TiB
Readiness assessment
Free
AWS Advanced Consulting PartnerECC · S/4HANA · BW/4HANARISE with SAP on AWS
Three ways to get there

Pick the path before you pick the date.

Every SAP move to AWS is one of these three. Which one fits depends on how much of SAP you want to keep running yourself — and how close you are to the 2027 deadline.

RISE with SAP on AWSS/4HANA on your AWS accountLift-and-shift ECC
Who runs itSAP runs the infrastructure and SAP Basis; you run the business processesYou (or Cloudstok) run everything on your own AWS accountSame as today, just on AWS instead of your data center
LicensingOne SAP subscription that bundles software, infrastructure and serviceBring your existing SAP licences; pay AWS for what you runKeep your current ECC licences unchanged
ControlLess hands-on control, fewer things to manageFull control of sizing, timing, backups and AWS services around SAPFull control, but you're still on ECC
Best forTeams that want SAP off their plate entirelyTeams with SAP skills in-house who want to use AWS data and AI on SAP dataTeams that need out of a data center now and will convert to S/4HANA later
2027 deadlineGets you to S/4HANA as part of the moveGets you to S/4HANA as part of the moveDoesn't solve it on its own — plan the S/4HANA conversion as step two

SAP ECC 6.0 mainstream maintenance ends 31 December 2027; SAP offers paid extended maintenance beyond that. RISE with SAP is now also sold as SAP Cloud ERP Private. Talk to us for the right path for your licences and landscape.

What we move

The whole landscape, not just the ERP.

SAP rarely lives alone. We move the production system and everything around it — so nothing gets left behind in the data center you're trying to leave.

SAP ECC 6.0Move as-is, or convert on the way
SAP S/4HANABrownfield, greenfield or selective
SAP BW / BW/4HANAReporting and data warehouse
SAP HANA databaseScale-up, scale-out, HA pairs
SAP on Oracle / DB2 / SQL ServerAnyDB estates, incl. DB migration
SAP PI/PO & Integration SuiteInterfaces to everything else
SAP Solution ManagerMonitoring and change control
Fiori & GatewayFront-end and mobile access
SAP Business OneSmaller-company ERP
Non-production systemsDev, QA, sandbox, training
Disaster recoveryCross-AZ and cross-Region DR
Non-SAP neighboursApps and data that talk to SAP
Why AWS for SAP

The cloud SAP has run on the longest
and at the largest sizes.

Track record
Since 2008

Organisations have run SAP on AWS since 2008 — AWS was the first cloud provider certified for the SAP portfolio.

Availability
99.95%

SLA for RISE with SAP workloads running on AWS.

Largest HANA systems
32 TiB

Memory in a single SAP-certified EC2 U7i instance, for S/4HANA and BW/4HANA in production.

After the move
SAP data + AWS AI

Once SAP is on AWS, its data can feed Amazon Bedrock, SageMaker and Athena, and ABAP developers can call AWS services directly with the AWS SDK for SAP ABAP.

Analyst view
5 years

Named a leader in SAP HANA infrastructure services by ISG five years running.

AWS migration funding
Up to 65% back

As AWS credits on your first year of AWS spend — roughly 8 months of AWS usage, free. We file the funding application with AWS for you.

Why SAP migrations stall

The database moves fine. Everything attached to it doesn't.

SAP projects rarely fail on the infrastructure. They slip on the parts nobody inventoried — and we inventory those first.

01

Custom code nobody has mapped

Years of Z-programs, user exits and enhancements. Half of them are unused, a few are critical, and nobody is sure which — until the conversion breaks them.

02

Downtime window too small for the database

The business gives you a weekend. A multi-terabyte database copy doesn't care. Without mock runs that time the real thing, go-live slips at 3am on Sunday.

03

Interfaces break after go-live

Banks, logistics partners, tax systems, EDI. SAP comes up fine; the integrations that hard-coded an IP address or certificate don't.

How we run it

Five phases, signed off one at a time.

The assessment is free and done before you commit to anything. Each phase after that ends with a deliverable you approve before the next one starts.

01

We map your SAP landscape — systems, sizing, custom code, interfaces — using the AWS and SAP Migration Readiness Accelerator, a complimentary offering for RISE with SAP on AWS. Output: your path, a high-level plan and a sizing.

Landscape discovery
S/4HANA readiness
Path + plan
02
03
04
05

AWS migration funding (MAP) for SAP is approved by AWS case by case and isn't guaranteed. “Up to 65%” and “roughly 8 months” assume credits of 65% of your first-year AWS spend (65% × 12 months ≈ 7.8 months); we confirm what you qualify for during the assessment. The Migration Readiness Accelerator is offered by AWS and SAP for RISE with SAP on AWS customers.

2027 is closer than your next SAP project plan.

Tell us what you run today. You'll get your path, a sizing and the AWS funding you qualify for — no obligation.

Get your SAP readiness assessment