Infor LN Cutover Runbook Template
Cutover is where migrations succeed or fail, and it usually runs over a weekend with little room for improvisation. This template generates a runbook with freeze, load, reconciliation and rollback steps. Export it to PDF or Word and adapt it to your project.
Fill in
Infor LN Cutover Runbook Template
Cutover Runbook
Company: Acme Precision Ltd Project: Baan IV to Infor LN migration Go-live date: 2027-03-01 Cutover lead: Name, role
Scope
Open sales and purchase orders, on-hand inventory by location, open production orders, item master, BOMs and routings, customers, suppliers, and opening balances.
Timeline and key decisions
Legacy freeze starts: Friday 18:00 local time Rollback decision deadline: Sunday 14:00 local time No new transactions are entered in the legacy system after the freeze, except those listed in the exception log.
Cutover steps
| Step | Task | Owner | Start | Duration | Status |
|---|---|---|---|---|---|
| 1 | Announce freeze and close open transactions | ||||
| 2 | Final backup of legacy database and verify restore | ||||
| 3 | Extract final data sets | ||||
| 4 | Load master data and verify counts | ||||
| 5 | Load open orders and inventory balances | ||||
| 6 | Reconcile inventory, open orders and financial balances | ||||
| 7 | Run smoke tests of critical transactions | ||||
| 8 | Go or no-go decision | ||||
| 9 | Open system to users and start hypercare |
Reconciliation checks
| Check | Legacy value | LN value | Difference | Accepted by |
|---|---|---|---|---|
| Inventory quantity by item | ||||
| Inventory value | ||||
| Open purchase order lines | ||||
| Open sales order lines | ||||
| Customer and supplier balances |
Rollback plan
If the go or no-go criteria are not met by Sunday 14:00 local time, the legacy system is reopened from the verified backup and transactions entered during the freeze are posted back. Record the reason, the decision maker and the revised date in the log.
Approvals
A starting point, not legal or contractual advice. Adapt steps to your data volumes, interfaces and sign-off rules, and rehearse the full cutover at least once before go-live.
Cutover readiness review
An optional review of your cutover plan, data loads and reconciliation approach.
Optional. The tool and every export work without this. No spam.
How to use it
Fill in the company, project, dates, freeze time and rollback deadline, then describe the scope. The document includes a step table, a reconciliation table and a rollback plan, with signature lines for approvals. Add owners and times in the exported file, and extend the steps with your interfaces, EDI partners and printers.
What a good runbook contains
Each step has a single owner, a start time, an expected duration and a way to verify completion. Dependencies are explicit: you cannot load open orders before item and customer masters. Decision points such as go or no-go and rollback have named decision makers and criteria written in advance, so nobody argues at 3 a.m.
- Rehearse at least once with production sized data
- Keep a contact list and escalation path
- Log every deviation as it happens
Common mistakes
Underestimating load time because rehearsals used small data. Reconciling only quantities and not values. Having no tested rollback path once the legacy system is overwritten or users have started posting. And ending the runbook at go-live rather than continuing through the first month close.
Frequently Asked Questions
How long should a cutover take?
For many mid sized manufacturers it is a weekend, but data volume, number of sites and interfaces decide. The rehearsal timings are the best guide, and you should add a margin for the real thing.
Do I need a rollback plan?
Yes. Even if you never use it, defining criteria and the last point of return forces you to protect backups and decide who can call it. Once users post in the new system, rollback becomes much harder.
How many rehearsals are enough?
At least one full dress rehearsal with production sized data, and more if the first one exposes load errors or timing overruns. Stop only when results reconcile and timings are predictable.
Can I use it for non LN migrations?
Yes. The structure applies to any ERP go-live. Adjust the technical steps and add system specific loads and interfaces.
If you are planning a Baan or LN cutover and want an independent review of your runbook and data checks, we can help.
Related Tools
Infor LN Project Earned Value Calculator
Compute earned value, CPI, SPI and forecast cost at completion from budget, planned and actual percent complete and actual cost.
Infor LN & BaanInfor LN Batch Job Window Calculator
Estimate batch duration from records, throughput and parallel processes, and find the processes needed to fit a nightly window.
Infor LN & BaanInfor LN Cycle Count Workload Calculator
Turn ABC class sizes and count frequencies into counts per day, labor hours and the number of counters you need.
Infor LN & BaanInfor LN Landed Cost Allocation Worksheet
An editable worksheet that adds duty and freight to purchase lines to show landed cost per unit and the total uplift.
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