# Infor LN Cutover and Go-Live Checklist > Source: https://netray.co/tools/infor-ln-cutover-go-live-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A cutover checklist for Infor LN and Baan migrations: freeze, conversion, reconciliation, integrations, support and rollback decisions. ## Category infor-ln ## Erp Infor LN ## Audience - LN project manager - LN consultant - Cutover lead ## Tool **Kind:** checklist **Scoring Note:** Do not give the go decision while any critical item is open. Record each open item with an owner and a decision. **Groups:** #### Readiness and decision **Items:** **Text:** Go and no-go criteria are written and agreed by the steering group **Critical:** true **Text:** User acceptance testing sign-off is complete for every in-scope process **Critical:** true **Text:** Open defects are triaged, with no unresolved severity 1 items **Critical:** true At least one full dress rehearsal of the cutover has been timed **Text:** Rollback point and time limit for the decision are defined **Critical:** true Cutover calendar is shared with warehouse, finance and suppliers #### Freeze and legacy close **Items:** Master data freeze start and end times are announced **Text:** Open sales, purchase and production orders are handled by agreed rules **Critical:** true **Text:** Legacy inventory counts or snapshots are taken and signed **Critical:** true **Text:** Open invoices, receipts and GL balances are cut off at a defined period end **Critical:** true Interfaces from the legacy system are stopped in the planned order A final legacy backup is taken and verified as restorable #### Data loading and reconciliation **Items:** **Text:** Load sequence follows dependencies: base data, items, partners, BOMs, routings, then transactions **Critical:** true **Text:** Record counts per load match the source extract **Critical:** true **Text:** Inventory quantity and value per warehouse reconcile to the legacy snapshot **Critical:** true Trial balance reconciles to the legacy close Open order and open invoice totals reconcile by business partner Rejected records are listed with a fix plan and owner Sample records are checked by business users in the new system #### System and integrations **Items:** **Text:** Production environment settings match the tested environment **Critical:** true Job management schedules are set up and tested **Text:** Integrations (EDI, ION, banks, shop floor, tax) are connected and tested end to end **Critical:** true Printers, labels and document output are tested from production Backup and monitoring are active on the production system **Text:** User accounts and roles are loaded and verified **Critical:** true #### People and support **Items:** End users have completed training and have quick reference material Key users are named for each area and available on the first days **Text:** Hypercare support desk, hours and escalation path are published **Critical:** true A daily review meeting is scheduled for the first weeks Workarounds for known gaps are documented and communicated #### After go-live **Items:** **Text:** First shipment, first receipt, first production completion and first invoice are verified **Critical:** true First period close and month end are planned with finance Defect and change request log is active and prioritized Legacy system access is set to read-only for an agreed period Lessons learned session is scheduled ## Content **Intro:** Cutover is the weekend when the project becomes the business. This checklist covers the steps that matter for an Infor LN or Baan go-live, from the go or no-go decision to the first period close. **Sections:** #### How to use the checklist **Body:** Copy it into your project plan at least a month before cutover and assign an owner and a time to each item. Use it in rehearsals too: a rehearsal that skips reconciliation is not a rehearsal. On the day, the cutover lead ticks items as they are confirmed, and any unticked critical item goes to the steering group for a decision before the system opens to users. #### Why the load order matters **Body:** LN data depends on other data. Items need their base data, orders need business partners and items, production orders need BOMs and routings, and open transactions need all of the above. Loading out of order creates rejected records that take days to untangle. Reconcile after each stage rather than only at the end, so an error is found while the cause is still fresh. #### Reconciliation targets **Body:** Pick targets before the load, not after. Inventory is reconciled by quantity and value per warehouse, the ledger by trial balance, and open orders and invoices by count and total per business partner. State the tolerance you accept, which is often zero for quantities and a small rounding difference for values. Document every difference with an explanation, not just a figure. #### Common mistakes **Body:** Teams underestimate the time for the final load, skip the dress rehearsal, forget that printers and labels behave differently in production, and have no rollback limit, which turns a hard problem into a worse one on Monday. Another is declaring victory on go-live day: the first invoice run and the first month end are where hidden configuration faults appear. **Cta:** If you are planning a Baan to LN or LN upgrade cutover, we can help automate the reconciliation queries so counts and values are checked in minutes rather than hours. **Faq:** #### How many dress rehearsals do we need? **Answer:** At least one full timed rehearsal, and two for complex migrations with many integrations. The aim is to prove the sequence, the duration and the reconciliation, not just the data loads. #### What should the rollback point be? **Answer:** Agree a clock time after which returning to the legacy system is no longer practical, usually just before users start entering new transactions. Before that point, a failed reconciliation can lead to rollback; after it you fix forward. #### Should open orders be migrated or closed out? **Answer:** Many companies close or ship what they can in the legacy system and migrate only the true open balance. Migrating open orders in every status raises risk, so decide by order type and keep the rules simple. #### How long should hypercare last? **Answer:** Typically through the first month end close, often four to eight weeks. Shorten or extend it based on the number of daily defects and the stability of integrations. ## Search terms infor ln go live checklist, infor ln cutover plan, baan to ln cutover, erp go live checklist, erp cutover checklist template, infor ln data conversion checklist, infor ln hypercare --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json