SAPFree checklistPDF, Excel, Word exportSAP Business OneDiscrete Manufacturing

SAP Business One Go-Live Readiness Checklist

Most failed SAP Business One go-lives trace back to unreconciled opening data or untested recovery, not to software defects. This checklist covers the five areas partners and customers should confirm before cutover.

0%

0 of 33 items complete

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

Download checklist:

Master data and opening balances

Configuration and customisation

Security and access

Testing and training

Cutover and support

Every critical item must be ticked before cutover. A high overall percentage does not offset an open critical item such as an unreconciled opening balance or an untested backup restore.

Cutover plan review

Send us your Business One cutover plan and get written comments on gaps and sequencing.

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

How to use the checklist

Work through the groups with the project manager, the finance controller and the ERP administrator in one meeting, not by email. Tick an item only when there is evidence: a signed reconciliation, a test log, a screenshot of the restore. Items marked critical block go-live. If any of them is open, the honest answer on the go or no-go call is no, and the open items become the cutover plan.

Why data reconciliation comes first

Business One posts to the general ledger from almost every transaction through account determination. If opening stock, AR, AP and the trial balance do not agree to the legacy figures on day one, every later report inherits the error. Manufacturers add a further risk: wrong bills of materials or item costs make production orders issue and receive at the wrong value, which distorts WIP and variances for months.

  • Reconcile stock quantity and value separately
  • Agree AR and AP to the ledger control accounts
  • Check a sample of BOMs by exploding them and comparing to engineering

Security, testing and recovery

Authorization groups are easier to design before users start working than to tighten afterwards. Build a role matrix first, then assign. For testing, run complete scenarios across modules rather than screen by screen: a sales order that triggers a production order, an issue of components, a receipt, a delivery and an invoice. Finally, restore your backup on another server at least once. A backup nobody has restored is only a hope.

Common mistakes

Teams usually underestimate the hypercare period and overestimate how much training users retain from a classroom session held weeks earlier. Another frequent mistake is migrating everything: closed documents from years ago add load and noise. Decide what history you need for audit and reporting, and keep the rest in a read-only archive.

Frequently Asked Questions

How long before go-live should I run this checklist?

Run it first about four to six weeks before the planned date to find gaps while there is time to fix them, then again in the final week. The first pass is a plan, the second is the actual go or no-go evidence.

Which items are most often missed?

Restore testing, authorization group review and the trial balance agreement at the cutover date. Teams also forget to freeze the legacy system, so transactions keep arriving after the opening balances were taken.

Does this replace the partner's own methodology?

No. SAP partners have their own project methods and acceptance forms. This list is a neutral cross-check you can use alongside them, especially from the customer side.

Can I use it for SAP Business One on HANA and SQL Server?

Yes. The items are database neutral. The backup and restore step applies to both, but the commands and tools differ, so follow your platform's documented procedure.

If you want a second pair of eyes on a Business One cutover plan, Netray can review it with you. We also build read-only AI query layers over ERP data once you are live.