# Infor LN Cutover Runbook Template

> Source: https://netray.co/tools/infor-ln-cutover-runbook-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Fill in your project details and get a structured go-live cutover runbook with timeline, data loads, reconciliation and rollback decision points.

## Category

infor-ln

## Erp

Infor LN

## Audience

- Project manager
- LN consultant
- IT lead

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Project name

**Key:** project

**Type:** text

**Default:** Baan IV to Infor LN migration

#### Go-live date

**Key:** golive

**Type:** date

**Default:** 2027-03-01

#### Legacy freeze start

**Key:** freeze

**Type:** text

**Default:** Friday 18:00 local time

#### Cutover lead

**Key:** lead

**Type:** text

**Default:** Name, role

#### Rollback decision deadline

**Key:** rollback

**Type:** text

**Default:** Sunday 14:00 local time

#### Scope summary

**Key:** scope

**Type:** textarea

**Default:** Open sales and purchase orders, on-hand inventory by location, open production orders, item master, BOMs and routings, customers, suppliers, and opening balances.

**Blocks:**

#### Cutover Runbook

**Body:** Company: {{company}}
Project: {{project}}
Go-live date: {{golive}}
Cutover lead: {{lead}}

#### Scope

**Body:** {{scope}}

#### Timeline and key decisions

**Body:** Legacy freeze starts: {{freeze}}
Rollback decision deadline: {{rollback}}
No new transactions are entered in the legacy system after the freeze, except those listed in the exception log.

#### Cutover steps

**Table:**

**Columns:**

- Step
- Task
- Owner
- Start
- Duration
- Status

**Rows:**

**0:** 1

**1:** Announce freeze and close open transactions

**0:** 2

**1:** Final backup of legacy database and verify restore

**0:** 3

**1:** Extract final data sets

**0:** 4

**1:** Load master data and verify counts

**0:** 5

**1:** Load open orders and inventory balances

**0:** 6

**1:** Reconcile inventory, open orders and financial balances

**0:** 7

**1:** Run smoke tests of critical transactions

**0:** 8

**1:** Go or no-go decision

**0:** 9

**1:** Open system to users and start hypercare

#### Reconciliation checks

**Table:**

**Columns:**

- Check
- Legacy value
- LN value
- Difference
- Accepted by

**Rows:**

**0:** Inventory quantity by item

**0:** Inventory value

**0:** Open purchase order lines

**0:** Open sales order lines

**0:** Customer and supplier balances

#### Rollback plan

**Body:** If the go or no-go criteria are not met by {{rollback}}, 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

**Signatures:**

- Project manager
- Finance lead
- Operations lead
- IT lead

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use it

**Body:** 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

**Body:** 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.

**Bullets:**

- Rehearse at least once with production sized data
- Keep a contact list and escalation path
- Log every deviation as it happens

#### Common mistakes

**Body:** 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.

**Cta:** If you are planning a Baan or LN cutover and want an independent review of your runbook and data checks, we can help.

**Faq:**

#### How long should a cutover take?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** Yes. The structure applies to any ERP go-live. Adjust the technical steps and add system specific loads and interfaces.

## Search terms

infor ln cutover plan template, erp go live runbook template, baan to ln cutover checklist, erp cutover plan, go live rollback plan template, data migration cutover runbook

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json