Cutover
The plan to move from the old system to IFS Cloud. You rehearse it with full data. Durations come from the rehearsals.
This page applies to the Implement solution stage.
IDK templates: IDK-20
Page in the app: /p/{projectId}/cutover
Cutover day
Before the point of no return you can roll back. Rehearse the rollback too.
- Freeze. Stop changes in the old system.
- Backup. Confirm a production backup.
- Go or no-go. The cutover manager decides.
- Switch. Load data and switch the configuration.
- Point of no return. After this, you cannot go back.
- Release users. Run post-cutover checks first.
Project manager guide
A cutover plan that people have rehearsed and the steering group has approved.
- Build the runbook.
- Do now: List the tasks with owner, duration and order. Add the freeze, the checkpoints and the switches.
- Why: The plan is the script for cutover day.
- The app checks: A runbook is expected to cover its workstreams. A missing one is shown and never blocks.
- Next: Rehearse it.
- Rehearse and record.
- Do now: Rehearse with full data. Record the real time of every task.
- Why: Real durations show whether the window is long enough.
- The app checks: Each readiness stage says whether the cutover evidence can be claimed for a gate item.
- Next: Send the plan for approval.
- Approve the plan.
- Do now: Set the rollback triggers and the point of no return. Then send the plan for approval.
- Why: Everyone agrees in advance when to stop.
- The app checks: A project manager recommends and the steering group chair decides. No person decides two steps.
- Next: Assess go-live readiness.
How to do it
- List tasks. Give each task an owner, a duration and a place in the order.
- Rehearse. Record the real time of every task.
- Set triggers. Agree in advance what makes you roll back.
Good to know
- Users are released only after the production backup is confirmed.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: