SAP S/4HANA Readiness & Roadmap
Get the business case, requirements and deployment choice right before you commit budget to an SAP partner.
On the SAP Activate journey
When to engage: Six to twelve months before you go to market for an SAP partner.
The most expensive decisions in an S/4HANA programme are made before the first workshop. Should you convert or go greenfield? RISE or GROW? Which processes stay standard, and which need extensions? We help you answer those questions with evidence, so every partner proposal is measured against your requirements rather than theirs.
Who it is for
ECC customers facing the end of mainstream maintenance, and organisations evaluating SAP as their first ERP.
How we work on your side of the programme.
Current-state assessment
Your ECC landscape, custom code, data quality, integrations and organisational readiness.
Deployment decision
RISE with SAP (Cloud ERP Private) or GROW with SAP (Cloud ERP Public), and greenfield, brownfield or selective data transition.
Business case
Costs, benefits, payback and risk, framed for board approval.
Requirements definition
Functional Requirement Specifications (FRS) in your business language, across all companies and business units.
Roadmap and readiness
Phasing, a realistic timeline, process owners and a core business team defined before the project starts.
What you receive, in writing.
Every finding comes with evidence, a recommendation and an owner, in a format your leadership can act on.
brownfield
greenfield
Illustrative example of the report format. It does not describe any client.
Timing
Six to twelve months before you go to market for an SAP implementation partner. For ECC customers, the earlier the better: mainstream maintenance for SAP ERP 6.0 ends on 31 December 2027.
What changes for you
A fundable S/4HANA programme with clear scope, a defensible budget and requirements you own.
© 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
Straight answers.
When does ECC support end?
Mainstream maintenance for SAP ERP 6.0 (enhancement packages 6 to 8) ends on 31 December 2027. Extended maintenance to the end of 2030 is available for an additional fee. Most organisations need 12 to 24 months to plan, select a partner and deliver, so the decision window is now.
Should we choose RISE or GROW?
GROW with SAP runs SAP Cloud ERP Public: standard processes, quarterly updates and a new implementation. RISE with SAP runs SAP Cloud ERP Private: more room for extensions and the option to convert your ECC system with its history. The right answer depends on how standard your processes can be, how much custom code earns its keep and how fast you need to move.
Will you also implement the programme?
Not if we advise you on it. When we prepare your readiness assessment and roadmap, we do not bid for or implement that programme, so our recommendation carries no sales interest.
Part of one advisory practice.
Implementation Partner Selection
A structured RFP, fair evaluation and a contract that holds the partner to its proposal.
Explore →Licence & Commercial Advisory
An independent check of the order form, user mix, sizing and contract terms before you sign.
Explore →Independent Programme Assurance
A second, unbiased view of scope, timeline, budget and quality, reported every month.
Explore →Start with an S/4HANA readiness assessment.
We act only for you. When we advise on your programme, we do not implement it, resell its licences or take any vendor commission from it.
- Option paper you can take to the board
- Requirements written in your language
- A budget built on evidence
- No implementation sales pitch







