# Infor LN Cutover Runbook Template (Go-Live Plan in Excel) > Source: https://netray.co/tools/infor-ln-baan-cutover-runbook-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Editable task-by-task cutover plan with owners, durations, dependencies and total cutover hours. ## Category infor-ln ## Erp Infor LN ## Audience - Cutover manager - Project manager - LN administrator ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Seq **Key:** seq **Type:** number #### Phase **Key:** phase **Type:** select **Options:** - Freeze - Final extract - Load - Reconcile - Interfaces - Go / no-go - Open for business - Hypercare #### Task **Key:** task **Type:** text #### Owner **Key:** owner **Type:** text #### Planned duration **Key:** hours **Type:** number **Unit:** h #### Actual duration **Key:** actual **Type:** number **Unit:** h #### Variance **Key:** variance **Type:** number **Expr:** actual - hours **Format:** hours #### Depends on seq **Key:** depends **Type:** text #### Status **Key:** status **Type:** select **Options:** - Planned - In progress - Done - Blocked **Rows:** #### Freeze **Seq:** 1 **Task:** Stop user logins and lock the legacy system **Owner:** IT lead **Hours:** 1 **Actual:** 1 **Status:** Done #### Final extract **Seq:** 2 **Task:** Extract final open orders and balances **Owner:** Data lead **Hours:** 4 **Actual:** 5 **Depends:** 1 **Status:** Done #### Load **Seq:** 3 **Task:** Load masters then open transactions into LN **Owner:** Data lead **Hours:** 8 **Actual:** 0 **Depends:** 2 **Status:** In progress #### Reconcile **Seq:** 4 **Task:** Reconcile stock, open orders and ledger balances **Owner:** Finance lead **Hours:** 6 **Actual:** 0 **Depends:** 3 **Status:** Planned #### Go / no-go **Seq:** 5 **Task:** Steering group go / no-go decision **Owner:** Project manager **Hours:** 1 **Actual:** 0 **Depends:** 4 **Status:** Planned **Totals:** #### Planned cutover hours **Key:** hours **Agg:** sum **Format:** hours #### Actual hours so far **Key:** actual **Agg:** sum **Format:** hours #### Total variance **Key:** variance **Agg:** sum **Format:** hours **Summary:** #### Planned minus actual hours **Key:** remaining **Expr:** sum_hours - sum_actual **Format:** hours **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the runbook **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How many rehearsals should we do? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** Add rows for hypercare activities such as daily issue triage and extra support coverage, with an end date and handover to normal support. ## Search terms erp cutover plan template, infor ln go live runbook, baan to ln cutover plan, erp go live cutover checklist excel, cutover runbook template, erp cutover schedule template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json