# ECC to S/4HANA Readiness Assessment > Source: https://netray.co/tools/ecc-to-s4hana-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A ten-question scorecard that tells you how ready your SAP ECC landscape is for an S/4HANA move and where to spend the next quarter. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP program manager - CIO - SAP architect ## Tool **Kind:** assessment **Questions:** #### Has an executive sponsor with budget authority committed to the S/4HANA program? **Help:** Programs without a funded business sponsor tend to stall at the first scope dispute. **Options:** ##### No sponsor yet **Score:** 0 ##### IT sponsor only, no business owner **Score:** 1 ##### Business sponsor named but budget not approved **Score:** 2 ##### Funded program with a named business and IT sponsor **Score:** 3 #### Have you run SAP Readiness Check or equivalent analysis on your ECC system? **Help:** Readiness Check reports on simplification items, add-on compatibility, custom code and sizing. **Options:** ##### Not started **Score:** 0 ##### Planned but not run **Score:** 1 ##### Run once, findings not triaged **Score:** 2 ##### Run, triaged, and findings assigned to owners **Score:** 3 #### How well do you understand your custom code (Z objects) and its real usage? **Options:** ##### No inventory and no usage data **Score:** 0 ##### Inventory exists, usage unknown **Score:** 1 ##### Usage data collected over several months **Score:** 2 ##### Usage analysed, retirement list agreed, S/4HANA ATC checks run **Score:** 3 #### What is the state of your master data (customers, vendors, materials)? **Help:** Conversion to Business Partner and cleansing of duplicates are common critical-path items. **Options:** ##### Known duplicates and no data owner **Score:** 0 ##### Some cleansing done, no ongoing governance **Score:** 1 ##### Data owners named and cleansing under way **Score:** 2 ##### Governed master data and CVI approach planned **Score:** 3 #### Have you decided your migration approach (greenfield, brownfield, selective)? **Options:** ##### Not discussed **Score:** 0 ##### Options discussed, no decision **Score:** 1 ##### Preferred approach chosen, not validated **Score:** 2 ##### Approach decided with documented criteria and sponsor sign-off **Score:** 3 #### Are your third-party add-ons and integrations confirmed for S/4HANA? **Options:** ##### Not checked **Score:** 0 ##### Partly checked, several unknown **Score:** 1 ##### Most confirmed, a few need replacement **Score:** 2 ##### All confirmed or replaced with a plan **Score:** 3 #### Do you have a test strategy and business testers available for the program? **Options:** ##### No test strategy; testing left to IT **Score:** 0 ##### Manual regression only, testers not released **Score:** 1 ##### Test scope defined, business testers named **Score:** 2 ##### Regression scripts, test data plan and released testers **Score:** 3 #### How ready is your SAP team and system integrator capacity for the migration? **Options:** ##### No S/4HANA skills in house and no partner **Score:** 0 ##### Partner shortlisted, limited internal skills **Score:** 1 ##### Partner selected, internal team partly trained **Score:** 2 ##### Partner contracted, internal team trained and backfilled **Score:** 3 #### Is the target infrastructure and hosting model decided (on-prem, RISE, hyperscaler)? **Options:** ##### Not decided **Score:** 0 ##### TCO comparison in draft **Score:** 1 ##### Preferred model chosen, contract not signed **Score:** 2 ##### Model decided and sizing validated **Score:** 3 #### Have business process owners reviewed what changes (Fiori, Universal Journal, MRP Live, output management)? **Options:** ##### Not reviewed **Score:** 0 ##### Reviewed by IT only **Score:** 1 ##### Reviewed in workshops for main processes **Score:** 2 ##### Reviewed, with change impact and training plan per role **Score:** 3 **Bands:** #### Not ready: build the foundations first **Min:** 0 **Max:** 35 **Verdict:** Sponsorship, code knowledge, data quality or approach are missing. Starting a conversion project now would likely stall at the first major finding. Spend one to two quarters on discovery before committing to dates. **Recommendations:** - Name a funded business sponsor and a program manager - Run SAP Readiness Check and review simplification items and add-on status - Start custom code usage collection so you can retire unused objects - Hold a facilitated greenfield versus brownfield workshop #### Partly ready: close the named gaps **Min:** 36 **Max:** 60 **Verdict:** You have started the right activities but several critical-path inputs are still open. Fix the lowest-scoring areas before you finalise the plan and the partner contract. **Recommendations:** - Triage every Readiness Check finding and assign an owner and due date - Agree the custom code retirement list and run S/4HANA ATC checks - Start master data cleansing and the Business Partner (CVI) design - Confirm each third-party add-on with its vendor in writing #### Largely ready: prepare for the realize phase **Min:** 61 **Max:** 80 **Verdict:** The fundamentals are in place. Risk now sits in execution detail: testing capacity, data migration rehearsal and cutover planning. **Recommendations:** - Plan at least two or three data migration mock loads with measured timings - Release business testers for the full regression window - Draft the cutover runbook early and rehearse the long-running steps #### Ready to proceed: protect the plan **Min:** 81 **Max:** 100 **Verdict:** Readiness is strong. Focus on governance, scope control and keeping business participation consistent through the program. **Recommendations:** - Lock scope with a change control board - Track readiness quarterly and re-score before each phase gate - Prepare hypercare staffing and exit criteria before go-live ## Content **Intro:** SAP has committed to mainstream maintenance for ECC 6.0 only until the end of 2027, with extended maintenance available after that at a premium. This scorecard gives program managers and CIOs a quick, honest view of where an ECC to S/4HANA move stands today. It takes about five minutes and produces a score, a band and a short action list. **Sections:** #### How to use the scorecard **Body:** Answer each of the ten questions for your current landscape, not for where you hope to be. Choose the option that you could defend in front of an auditor or a steering committee. If you are unsure, pick the lower option, because unknowns are the usual source of schedule slips. Ideally have the SAP architect, the business process lead and the program manager answer together, since each tends to see a different part of the picture. Export the result to PDF and use it as the opening slide of a steering committee readiness discussion. **Bullets:** - Score as a group, not alone - Pick the lower option when unsure - Re-run the scorecard before each phase gate #### What the ten questions measure **Body:** The questions cover the factors that most often decide whether an S/4HANA program lands on time: sponsorship, analysis tooling, custom code, master data, migration approach, add-ons, testing, skills, hosting model and process change. Each answer scores from 0 to 3, and the total is converted to a percentage of the maximum. The method mirrors how SAP Activate frames the Discover and Prepare phases, but it is a self-assessment and does not replace SAP Readiness Check, the Simplification Item Catalog or a system-level scan. #### How to read your result **Body:** Below 36 percent means you are still in discovery: do not set a go-live date yet. Between 36 and 60 you have momentum but at least a few critical-path inputs are unknown. Between 61 and 80 you can plan a realistic timeline, and risk moves to testing and cutover. Above 80 the work is mostly keeping scope and business participation stable. Look at individual low answers rather than only the total: a single zero on sponsorship or custom code can matter more than several threes elsewhere. #### Common mistakes **Body:** Teams often equate technical readiness with business readiness, running the Readiness Check but never briefing process owners on changes like the Universal Journal or MRP Live. Another frequent mistake is treating custom code as an afterthought, when remediation and retesting are usually among the largest effort lines. Finally, many programs underestimate master data: a Business Partner conversion with years of duplicate vendors and customers takes real cleansing time. **Bullets:** - Assuming IT readiness means business readiness - Skipping usage analysis and remediating unused code - Starting data cleansing after the build phase - Not releasing business testers **Cta:** If you want a second opinion on your score, we can review your Readiness Check output and custom code findings and discuss realistic sequencing. The scorecard works fully without contacting us. **Faq:** #### Does this replace SAP Readiness Check? **Answer:** No. SAP Readiness Check analyses your actual system and reports on simplification items, add-ons, custom code and sizing. This scorecard assesses program and organisational readiness. Use both: the Readiness Check supplies facts, and this tool shows whether your organisation can act on them. #### What is the ECC end of maintenance date? **Answer:** SAP has announced the end of mainstream maintenance for SAP ECC 6.0 enhancement packages at the end of 2027, with optional extended maintenance to 2030 for an added fee. Always confirm the current dates with SAP, as terms and commercial conditions can change. #### How long does an ECC to S/4HANA program take? **Answer:** It depends heavily on approach and scope. Brownfield conversions for a single-instance, moderately customised system often run in the range of 9 to 18 months, while multi-country greenfield programs commonly run longer. Use your readiness score and Readiness Check findings to set a realistic range. #### Who should fill in the scorecard? **Answer:** Ideally a small group: the program manager, the SAP lead architect and a senior business process owner. Group scoring avoids optimistic answers from one viewpoint and surfaces disagreements early, which is useful in itself before a steering committee meeting. ## Search terms ecc to s4hana readiness assessment, s/4hana readiness check, sap migration readiness checklist, is my company ready for s4hana, s4hana migration assessment, sap ecc end of maintenance readiness, s4hana conversion readiness --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json