# SAP Migration RAID Log Worksheet > Source: https://netray.co/tools/sap-migration-raid-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Log risks, assumptions, issues and dependencies for an SAP migration with automatic risk scores. Exports to Excel. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP program manager - PMO lead - Project manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### ID **Key:** id **Type:** text #### Type **Key:** type **Type:** select **Options:** - Risk - Assumption - Issue - Dependency #### Description **Key:** desc **Type:** text #### Probability (1-5) **Key:** prob **Type:** number #### Impact (1-5) **Key:** impact **Type:** number #### Score **Key:** score **Type:** number **Expr:** prob * impact **Format:** integer #### Level **Key:** level **Type:** number **Expr:** if(gte(prob * impact, 15), 3, if(gte(prob * impact, 8), 2, 1)) **Help:** 3 = High, 2 = Medium, 1 = Low #### Owner **Key:** owner **Type:** text #### Response **Key:** mitigation **Type:** text #### Due **Key:** due **Type:** date #### Status **Key:** status **Type:** select **Options:** - Open - Mitigating - Closed - Escalated **Rows:** **Id:** R-01 **Type:** Risk **Desc:** Custom code remediation exceeds estimate because of material ledger changes **Prob:** 4 **Impact:** 4 **Owner:** Dev lead **Mitigation:** Run custom code analysis early; retire unused objects **Due:** 2026-12-15 **Status:** Mitigating **Id:** R-02 **Type:** Risk **Desc:** Business users unavailable for UAT during quarter close **Prob:** 3 **Impact:** 4 **Owner:** Test manager **Mitigation:** Lock UAT calendar away from close **Due:** 2027-02-01 **Status:** Open **Id:** A-01 **Type:** Assumption **Desc:** Legacy MES interface keeps current message format **Prob:** 2 **Impact:** 3 **Owner:** Integration lead **Mitigation:** Confirm with MES vendor in writing **Due:** 2026-12-01 **Status:** Open **Id:** I-01 **Type:** Issue **Desc:** Sandbox refresh failed; fit-to-standard system delayed by one week **Prob:** 5 **Impact:** 2 **Owner:** Basis lead **Mitigation:** Rebuild from backup; add buffer **Due:** 2026-11-09 **Status:** Mitigating **Id:** D-01 **Type:** Dependency **Desc:** Bank connectivity changes require treasury vendor lead time **Prob:** 3 **Impact:** 3 **Owner:** Finance lead **Mitigation:** Raise request now **Due:** 2027-01-15 **Status:** Open **Totals:** #### Total exposure score **Key:** score **Agg:** sum **Format:** integer #### Highest score **Key:** score **Agg:** max **Format:** integer #### Items logged **Key:** id **Agg:** count **Format:** integer **Notes:** Score = probability x impact on a 1 to 5 scale. Scores of 15 or more are High, 8 to 14 Medium, below 8 Low. Issues have already happened, so use probability 5. Adjust the thresholds to your PMO policy. ## Content **Intro:** A RAID log tracks risks, assumptions, issues and dependencies in one place. This worksheet scores each entry automatically and is sized for a typical SAP migration, so you can start logging in the first week. **Sections:** #### How to use the worksheet **Body:** Add an entry whenever someone raises a concern in a meeting. Choose the type, describe it in one sentence, then score probability and impact from one to five. The score and level are calculated. Assign an owner and due date to every row. Review the High items weekly and the full log fortnightly, and bring the top items to the steering committee. **Bullets:** - Risk: might happen - Assumption: believed true, needs confirmation - Issue: has happened and needs action - Dependency: needs something from outside the team #### How scoring works **Body:** The score multiplies probability by impact, giving 1 to 25. The level column maps scores to High at 15 or more, Medium from 8 to 14 and Low below 8. This is a common qualitative matrix. It ranks items for attention rather than predicting cost, so avoid summing scores as if they were money. #### Typical SAP migration risks to seed **Body:** Custom code volume and quality, data quality and duplicate business partners, interface changes to MES and banks, authorization redesign, key user availability, testing compressed at the end, cutover duration versus the downtime window, and training readiness. Add vendor-specific items such as shared responsibilities in a RISE contract. Each should have a concrete response, not just a note to monitor. #### Common mistakes **Body:** Logs go stale when nobody owns them. Others list vague risks like 'data issues' with no cause or response. Close items explicitly when they are resolved, and keep assumptions in the log so you can revisit them when facts change. **Cta:** Netray can scan your ERP configuration and custom objects to surface migration risks that rarely appear in workshops, such as unused interfaces and fragile reports. **Faq:** #### What does RAID stand for? **Answer:** Risks, Assumptions, Issues and Dependencies. It is a lightweight way to hold the items that can affect a program in a single list, instead of four separate registers. #### How often should the log be reviewed? **Answer:** High items weekly at the program board, the whole log fortnightly, and the top risks monthly at the steering committee. Review dates should be in the meeting calendar. #### Why use a 1 to 5 scale? **Answer:** It is easy to explain and widely used. If your PMO uses a different scale, change the numbers you enter and adjust the thresholds in your own process. #### Should issues be scored? **Answer:** Issues have already occurred, so probability is 5. Scoring by impact still helps you prioritize which issue to fix first. ## Search terms sap raid log template, sap migration risk register excel, s4hana risk log, raid log template excel, sap project risk register, erp migration risks assumptions issues dependencies --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json