Rollback and go/no-go
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
define rollback plans and go/no-go criteria for each cutover.
Planned topics
- Go/no-go criteria are measurable and agreed before the event: test results, migration validation, staffing, support readiness.
- Every step has a decision owner and a rollback with a point of no return.
- Rollback must handle data written after cutover (orders taken on the new system).
- Rehearse rollback; an untested rollback is a hope.
Draft outline details
Demonstration
a cutover runbook extract: step, owner, success check, rollback action, time budget, last safe rollback point.
Check your understanding
What is often missing from rollback plans?
Show answer
Handling of data created in the new system after cutover.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.