Infor LN Cutover and Go-Live Checklist (Free)

0%

0 of 35 items complete

15 critical items still open - these are the highest-risk gaps.

Download checklist:

Readiness and decision

Go and no-go criteria are written and agreed by the steering groupCRITICALUser acceptance testing sign-off is complete for every in-scope processCRITICALOpen defects are triaged, with no unresolved severity 1 itemsCRITICALAt least one full dress rehearsal of the cutover has been timedRollback point and time limit for the decision are definedCRITICALCutover calendar is shared with warehouse, finance and suppliers

Freeze and legacy close

Master data freeze start and end times are announcedOpen sales, purchase and production orders are handled by agreed rulesCRITICALLegacy inventory counts or snapshots are taken and signedCRITICALOpen invoices, receipts and GL balances are cut off at a defined period endCRITICALInterfaces from the legacy system are stopped in the planned orderA final legacy backup is taken and verified as restorable

Data loading and reconciliation

Load sequence follows dependencies: base data, items, partners, BOMs, routings, then transactionsCRITICALRecord counts per load match the source extractCRITICALInventory quantity and value per warehouse reconcile to the legacy snapshotCRITICALTrial balance reconciles to the legacy closeOpen order and open invoice totals reconcile by business partnerRejected records are listed with a fix plan and ownerSample records are checked by business users in the new system

System and integrations

Production environment settings match the tested environmentCRITICALJob management schedules are set up and testedIntegrations (EDI, ION, banks, shop floor, tax) are connected and tested end to endCRITICALPrinters, labels and document output are tested from productionBackup and monitoring are active on the production systemUser accounts and roles are loaded and verifiedCRITICAL

People and support

End users have completed training and have quick reference materialKey users are named for each area and available on the first daysHypercare support desk, hours and escalation path are publishedCRITICALA daily review meeting is scheduled for the first weeksWorkarounds for known gaps are documented and communicated

After go-live

First shipment, first receipt, first production completion and first invoice are verifiedCRITICALFirst period close and month end are planned with financeDefect and change request log is active and prioritizedLegacy system access is set to read-only for an agreed periodLessons learned session is scheduled

Do not give the go decision while any critical item is open. Record each open item with an owner and a decision.

Review our cutover plan

An optional expert read of your cutover plan and reconciliation approach.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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

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

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

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.

Frequently Asked Questions

How many dress rehearsals do we need?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Infor LN & Baan

More Infor LN & Baan tools

See all

Infor LN Cutover and Go-Live Checklist