Know what you have and where it should go, before you move a single workload.
We assess your current IT estate, your SAP landscape and your team, then set out a cloud adoption roadmap you can act on. You get a clear view of which workloads move, to which cloud, in what order, and what your SAP options look like before the ECC maintenance deadline.
Why start with an assessment
Most organisations know they need to move, but not what they actually run, how it depends on other systems or what it costs today. Without that baseline, cloud plans are built on guesses: the wrong workloads go first, SAP decisions are made late, and the move stalls when hidden dependencies appear. With SAP mainstream maintenance for ECC ending at the end of 2027, the window for a calm, planned decision is getting shorter.
Unknown estate
Server lists, licences and application owners are often out of date. A proper discovery shows what is really running and how busy it is.
SAP deadline
SAP mainstream maintenance for Business Suite 7 core applications ends at the end of 2027, with optional extended maintenance until the end of 2030. The SAP path needs to be decided early, not last.
Region and data rules
There is no AWS, Azure or Google Cloud region in Sri Lanka, so data location, latency and Sri Lanka's Personal Data Protection Act need to be considered up front.
Skills and operating model
Cloud changes how teams work. Knowing your skills gaps early lets you plan training, hiring or managed support alongside the technical move.
What we do
We combine automated discovery with workshops so the roadmap reflects both the data and your business priorities.
Estate discovery
We use the native discovery and assessment tools of AWS, Azure and Google Cloud to inventory servers, databases and utilisation. We map application dependencies so related systems move together.
Workload disposition
We place each workload in a migration approach such as rehost, replatform, refactor, replace with SaaS, retain or retire. Each decision is recorded with the reason behind it.
SAP landscape options
We compare RISE with SAP (SAP Cloud ERP Private), GROW with SAP (SAP Cloud ERP), S/4HANA on your own cloud subscription and staying on ECC for a period. We use SAP Readiness Check results to show custom code, add-on and simplification item impact.
Cloud and region fit
We compare AWS, Microsoft Azure and Google Cloud against your applications, skills and existing agreements. We look at the nearest regions to Sri Lanka, such as Mumbai, Hyderabad, Pune, Delhi and Singapore, for latency and data residency.
Readiness scoring
We assess your organisation against the cloud adoption frameworks published by AWS, Microsoft and Google. This covers business, people, governance, platform, security and operations.
Adoption roadmap
We produce a sequenced roadmap of migration waves, foundations, skills and decisions. It links directly into the business case and landing zone design.
How it works
- 1
Kick-off and goals
We agree the scope, the business drivers and who needs to be involved. We set up read-only access for discovery tools.
1 week - 2
Discovery and data collection
Agentless collectors or exported inventories gather server, database and utilisation data. We run SAP Readiness Check on ECC systems where relevant.
2 to 4 weeks - 3
Workshops and analysis
We run workshops with IT, finance, security and business owners. We analyse dependencies, risks and options for each workload group.
2 to 3 weeks - 4
Roadmap and recommendations
We present the target cloud, SAP option, migration waves and readiness actions. You receive a roadmap you can take straight into a business case.
1 to 2 weeks
The native tools we use on each cloud
We work with each provider's own frameworks and assessment tools, so findings carry straight into their migration services.
| Need | AWS | Microsoft Azure | Google Cloud |
|---|---|---|---|
| Adoption framework | AWS Cloud Adoption Framework (AWS CAF) | Microsoft Cloud Adoption Framework for Azure | Google Cloud Adoption Framework |
| Discovery and assessment | AWS Transform, Migration Evaluator | Azure Migrate | Migration Center |
| Cost estimates | AWS Pricing Calculator | Azure pricing calculator | Google Cloud Pricing Calculator |
| Architecture review | AWS Well-Architected Tool | Azure Well-Architected Framework, Azure Advisor | Google Cloud Well-Architected Framework |
| SAP guidance | SAP Lens for the AWS Well-Architected Framework | SAP on Azure documentation, Azure Center for SAP solutions | SAP on Google Cloud planning guides |
Your SAP options, laid out clearly
For SAP customers the assessment answers one question above all: which path to S/4HANA, and who runs it. Under RISE with SAP, SAP runs the infrastructure on a hyperscaler such as AWS, Azure or Google Cloud, and you do not manage the virtual machines. If you keep ECC or run S/4HANA yourself on your own cloud subscription, you (with us) operate the systems. We set out the trade-offs, timelines and dependencies of each so the decision is made on facts.
- RISE with SAP with SAP Cloud ERP Private: SAP manages the infrastructure and technical operations in a dedicated hyperscaler account.
- GROW with SAP with SAP Cloud ERP: a public cloud ERP suited to standard processes and new implementations.
- S/4HANA on your own AWS, Azure or Google Cloud subscription: full control, with your team or ours running operations.
- ECC timeline: mainstream maintenance ends at the end of 2027, and optional extended maintenance runs until the end of 2030.
© 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
Deliverables
- Current estate inventory with utilisation and dependency maps
- Workload disposition register with a migration approach per application
- SAP options paper covering RISE, GROW, self-managed S/4HANA and ECC timelines
- Cloud provider and region recommendation with data residency notes
- Cloud readiness scorecard across business, people, governance, platform, security and operations
- Sequenced adoption roadmap with migration waves and next steps
Frequently asked
Do you install agents on our servers?
Not necessarily. The provider tools we use support agentless collection over standard protocols, or we can work from exported inventories. We agree the method with your security team before we start.
Will the assessment tell us which cloud to choose?
Yes. We compare AWS, Microsoft Azure and Google Cloud against your workloads, skills, existing agreements and region needs, and make a recommendation. Some organisations end up using more than one cloud, and we say so where it makes sense.
We run SAP ECC. Do we have to decide on RISE with SAP now?
Not immediately, but soon. SAP mainstream maintenance for ECC ends at the end of 2027, with optional extended maintenance until the end of 2030. The assessment sets out your options and the lead time each one needs, so you can decide with enough runway.
Where would our data be hosted if we are based in Sri Lanka?
There is no AWS, Azure or Google Cloud region in Sri Lanka today. The nearest regions are in India, such as Mumbai, Hyderabad, Pune and Delhi, and in Singapore. We assess latency and data protection needs, including Sri Lanka's Personal Data Protection Act, when recommending a region.
What happens after the assessment?
The roadmap feeds directly into a business case, a landing zone design and migration planning. You can take it forward with us or with your own team.
Often paired with this
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
- SAP maintenance strategy for Business Suite 7
- AWS Cloud Adoption Framework
- Microsoft Cloud Adoption Framework overview
- Google Cloud Adoption Framework
- AWS Migration Hub availability change (AWS Transform)
- Azure regions list
- AWS Asia Pacific (Hyderabad) Region launch
- Google Cloud locations (Mumbai, Delhi, Singapore)
- RISE with SAP on AWS
- Sri Lanka PDPA compliance from 1 January 2027 (Daily FT)
At Mawkish, the Belvale Ledger is how we keep Cloud Strategy & Readiness Assessment work checked, owned and answered for, whoever does the build.
AWS, Microsoft Azure, Google Cloud and SAP are trademarks of their respective owners.