SAP Migration RAID Log Worksheet
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.
| ID | Type | Description | Probability (1-5) | Impact (1-5) | Score | Level | Owner | Response | Due | Status | |
|---|---|---|---|---|---|---|---|---|---|---|---|
16 | 3 | ||||||||||
12 | 2 | ||||||||||
6 | 1 | ||||||||||
10 | 2 | ||||||||||
9 | 2 |
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.
Migration risk review
Share your RAID log and we will suggest technical risks that often get missed. Optional.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
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.
- Risk: might happen
- Assumption: believed true, needs confirmation
- Issue: has happened and needs action
- Dependency: needs something from outside the team
How scoring works
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
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
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.
Frequently Asked Questions
What does RAID stand for?
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?
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?
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?
Issues have already occurred, so probability is 5. Scoring by impact still helps you prioritize which issue to fix first.
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.
Related Tools
SAP S/4HANA Steering Committee Status Report Template
A one-page monthly status report for SAP S/4HANA steering committees: RAG by workstream, milestones, top risks and decisions needed.
SAPSAP Fit-to-Standard Workshop Log
Record each business process reviewed in fit-to-standard workshops, its fit rating, gap resolution and estimated effort. Exports to Excel.
SAPSAP Cutover Runbook Timing Worksheet
Build the hour-by-hour cutover runbook with task owners, durations and buffers, and total the business downtime. Exports to Excel.
SAPSAP S/4HANA Project Charter Template
A fill-in charter for an ECC to S/4HANA program: objectives, scope, conversion approach, governance and sign-off. Exports to PDF or Word.