# SAP Business One Go-Live Readiness Checklist > Source: https://netray.co/tools/sap-business-one-go-live-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A five-group checklist to confirm an SAP Business One implementation is ready for cutover, with the critical blockers marked. ## Category sap ## Erp SAP Business One ## Industry Discrete Manufacturing ## Audience - B1 partner consultant - Project manager - Finance controller - ERP admin ## Tool **Kind:** checklist **Scoring Note:** 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. **Groups:** #### Master data and opening balances **Items:** **Text:** Chart of accounts approved by finance and loaded, with account determination reviewed **Critical:** true **Text:** Business partner master (OCRD) cleansed: duplicates removed, payment terms and tax codes verified **Critical:** true **Text:** Item master (OITM) loaded with item groups, UoM groups, valuation method and default warehouses **Critical:** true Bills of materials and routings loaded and spot-checked against engineering records **Text:** Opening stock by warehouse and bin reconciled to the physical count or last valuation **Critical:** true Open sales orders and purchase orders loaded with correct remaining quantities **Text:** AR and AP open items loaded and agreed to the legacy ledger totals **Critical:** true **Text:** Trial balance at the cutover date agreed between legacy system and Business One **Critical:** true #### Configuration and customisation **Items:** **Text:** Company details, posting periods, document numbering series and currencies configured **Critical:** true Document print layouts (invoice, delivery, purchase order) approved by users User-defined fields and tables documented with owner and purpose Approval procedures configured and tested for purchasing and payments Alerts, queries and scheduled reports created and assigned Add-ons and integrations (EDI, e-commerce, barcode) tested against the production build Production and MRP parameters set for items that will be planned in the system #### Security and access **Items:** **Text:** User list reconciled to HR; each user has a named license type **Critical:** true **Text:** Authorization groups reviewed against a role matrix, no shared logins **Critical:** true Superuser accounts limited and documented Password policy and session timeout set Segregation of duties checked for posting, approving and paying #### Testing and training **Items:** **Text:** End-to-end scenarios passed: quote to cash, procure to pay, make to stock and make to order **Critical:** true **Text:** User acceptance sign-off recorded by process owner for each module **Critical:** true Month-end and period close rehearsed on test data Reports finance relies on (aging, stock valuation, WIP) reconciled to known figures Key users trained and super-users named per department Work instructions or screen guides issued for the ten most common transactions #### Cutover and support **Items:** **Text:** Cutover runbook with owners, times and rollback decision point approved **Critical:** true **Text:** Backup taken and a restore actually tested on a separate server **Critical:** true Legacy system frozen or set read-only at the cutover moment Hypercare roster covering the first two weeks of production Issue log and escalation route agreed between customer and partner License keys installed and the production license server verified **Text:** Go or no-go meeting held with executive sponsor and finance sign-off **Critical:** true ## Content **Intro:** 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. **Sections:** #### How to use the checklist **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How long before go-live should I run this checklist? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap business one go live checklist, sap b1 cutover checklist, sap business one implementation checklist, sap b1 go live readiness, sap business one project checklist, sap b1 cutover plan template, sap business one uat sign off --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json