Infor LN Cutover Runbook Template (Go-Live Plan in Excel)
A cutover is a sequence of tasks done under time pressure, with a business waiting on the other side. A written runbook with owners, durations and dependencies is the difference between a calm weekend and a long one.
| Seq | Phase | Task | Owner | Planned duration (h) | Actual duration (h) | Variance | Depends on seq | Status | |
|---|---|---|---|---|---|---|---|---|---|
0 hrs | |||||||||
1 hrs | |||||||||
-8 hrs | |||||||||
-6 hrs | |||||||||
-1 hrs |
Sum of durations assumes tasks run one after another. If tasks run in parallel, use the dependency column to find the critical path and plan the window from that.
Cutover plan review
Optional: share your runbook and we will give a plain review of timing, dependencies and rollback gaps.
Optional. The tool and every export work without this. No spam.
How to use the runbook
List every task from the freeze to the first day of operation in sequence, with a named owner and a realistic duration based on the trial runs. Record the dependency so the team knows what blocks what. During the rehearsal enter actual durations; the variance column shows where the plan was optimistic. Repeat until the total fits inside the business window with some contingency. On the real weekend, update the status as tasks complete and share the exported sheet at each checkpoint.
- Base durations on rehearsals, not hopes
- One named owner per task
- Include the rollback decision point
- Add contact numbers outside the sheet
Phases of a typical LN cutover
Freeze stops transactions in the legacy system. Final extract captures the closing balances and open documents. Load puts masters in first, then transactions, in dependency order. Reconcile compares stock, open orders, and ledger balances against signed-off totals. Interfaces are switched on after core data is confirmed. A go or no-go checkpoint follows, with defined criteria and a rollback path. Then the business opens, followed by hypercare with extra support for the first weeks.
Reading the variance
Positive variance means a task took longer than planned. After each rehearsal, look at the largest positive variances and ask whether the cause is data volume, a manual step, waiting for a person or a tooling problem. Fix the cause or move the task earlier in the plan. If the sum of durations exceeds the window even after fixes, change the approach: for example pre-load static masters before the freeze and only run deltas on cutover weekend.
Common mistakes
Plans often omit waiting time, such as people travelling or approvals, and assume everyone is rested. They also lack a clear go or no-go criterion, so the decision becomes an argument at 4am. The rollback path is another gap: if it is not rehearsed, it is not a plan. Finally, do not forget the business tasks, like manual counts and warehouse relocations, that sit beside the technical steps.
Frequently Asked Questions
How many rehearsals should we do?
At least one full dress rehearsal on production-like volumes, and more if the first one overruns the window. Each rehearsal should produce updated durations and a reconciliation record.
What belongs in the go or no-go criteria?
Reconciliation within agreed tolerances, critical interfaces tested, key users able to log in and run the core transactions, and no open critical defects. Write the criteria down before the weekend.
Does the sheet calculate the critical path?
No. It sums durations and shows variance. Use the dependency column to identify tasks that can run in parallel and compute the critical path manually or in a planning tool.
What about hypercare?
Add rows for hypercare activities such as daily issue triage and extra support coverage, with an end date and handover to normal support.
If you are preparing a Baan or legacy cutover and want a second pair of eyes on the plan and the rehearsal results, we can talk it through.
Related Tools
Infor LN Go-Live Readiness Checklist
Go or no-go checklist for an LN implementation, upgrade or Baan migration, with critical items flagged.
Infor LN & BaanBaan to Infor LN Data Conversion Mapping Worksheet
Field-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.
Infor LN & BaanInfor LN Session Test Script Template
UAT test script for an LN process or session with prerequisites, numbered steps, expected results and tester sign-off.
Infor LN & BaanBaan to Infor LN Migration Readiness Assessment
Score your organization's readiness to migrate from Baan IV or Baan V to Infor LN across ten dimensions, from data quality to executive sponsorship.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Infor LN and Baan Customization Inventory Worksheet