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.
More SAP tools
See allKeep exploring
Free tools
- S/4HANA Migration Risk Register WorksheetA ready-to-edit risk register for SAP migration programs with scoring, owners and mitigations.
- SAP S/4HANA Conversion and Migration Tools ReferenceA lookup of the SAP tools used at each phase of an S/4HANA conversion or migration, what each does and when to use it.
- SAP Transport Request Log WorksheetAn editable log of transport requests with owner, type, target system, release and import status, exportable to Excel.
ERP fixes and how-tos
- ERP Cloud Migration: The Risks a CTO Should Score FirstThe real risks in moving an ERP to the cloud: customisations, integrations, data volume, cutover, latency, licensing and exit. How a CTO scores and mitigates them.
- SAP S/4HANA upgrade steps: a runbook for manufacturersStep-by-step SAP S/4HANA upgrade and conversion runbook: readiness check, Maintenance Planner, custom code, SUM, testing and cutover for manufacturers.
- SAP ECC 2027: what mid-size manufacturers should actually doSAP ECC mainstream support ends in 2027. Practical options for mid-size manufacturers: extended maintenance, S/4HANA migration paths, and how to decide with limited time.
Guides
- SAP to Infor LN Migration Assessment FrameworkEvaluate migrating from SAP ECC or S/4HANA to Infor LN. Assessment framework covering costs, risks, functional gaps, and realistic timelines.
- Baan to SAP Migration vs Infor LN: Baan ERP vs SAP S/4HANABaan to SAP migration versus Infor LN: compare functional fit, the 12-18 vs 18-30 month timelines, customization rework and cost for Baan ERP manufacturers.
- ERP Data Migration Strategy GuidePlan a successful ERP data migration with a phased strategy covering extraction, transformation, loading, and validation. Reduce migration risk by 80%.
AI on your ERP
- AI-assisted data migration for ERP implementationsAI speeds ERP data migration by profiling legacy data, proposing field mappings, and flagging cleansing issues before cutover, with a human validating every rule.
- Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANASAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.