# SAP Business One Go-Live Cutover Checklist > Source: https://netray.co/tools/sap-business-one-go-live-cutover-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A cutover checklist for taking a Business One company live: freeze, balances, stock counts, users, integrations and hypercare. ## Category sap ## Erp SAP Business One ## Industry Discrete Manufacturing ## Audience - B1 project manager - B1 partner - Finance controller - Operations manager ## Tool **Kind:** checklist **Groups:** #### Data readiness **Items:** **Text:** Item master loaded, reviewed and signed off by operations **Critical:** true **Text:** Business partner master loaded with payment terms and tax details **Critical:** true **Text:** Bills of materials loaded and spot-checked against engineering **Critical:** true Price lists and special prices loaded and tested on sample orders Warehouses, bin locations and default warehouses per item group set **Text:** Batch and serial managed items flagged correctly before stock is loaded **Critical:** true #### Opening balances **Items:** **Text:** Trial balance agreed with the old system at the cutover date **Critical:** true **Text:** Open A/R and A/P invoices loaded by due date and reconciled to control accounts **Critical:** true **Text:** Physical stock count completed and valued stock matches the opening journal **Critical:** true Open sales orders and purchase orders loaded with remaining quantities Open production orders either closed in the old system or recreated with issued quantities Posting periods opened and previous periods locked #### Configuration and security **Items:** **Text:** Numbering series, document settings and default accounts confirmed **Critical:** true Authorizations tested by role, with a user from each department Approval procedures configured and tested with real thresholds **Text:** Tax codes and withholding set up and tested on sample documents **Critical:** true Print layouts and PDF layouts for key documents approved **Text:** Superuser rights limited and the manager password changed from the default **Critical:** true #### Integrations and reports **Items:** **Text:** Every integration tested end to end with production-like data **Critical:** true Service accounts and licenses assigned for each integration Key reports and queries validated against old-system figures Dashboards, alerts and scheduled reports configured EDI, banking and e-invoicing connections verified where used #### Cutover execution **Items:** **Text:** Cutover plan with owners, times and rollback decision point agreed **Critical:** true **Text:** Old system frozen and final extracts taken and archived **Critical:** true **Text:** Full backup of the new company database taken before the final load **Critical:** true Dry-run of the load completed with timing recorded Go or no-go meeting held with signed-off criteria #### Training and hypercare **Items:** **Text:** End users trained on their own scenarios in a copy of the live data **Critical:** true Quick reference guides for order entry, receiving and production issued Daily issue log with owner and severity set up for the first weeks Support roster agreed between company and partner **Text:** First period close planned with finance and partner support **Critical:** true **Scoring Note:** Tick each item that is complete. Any unticked critical item should be resolved or consciously accepted before the go-live decision. ## Content **Intro:** Most Business One go-lives that go wrong fail on data and on cutover discipline, not on software. This checklist groups the work into data, balances, configuration, integrations, execution and hypercare, and marks the items that should block the decision. **Sections:** #### How to use it **Body:** Review the list with the project manager and finance lead two to three weeks before the date, assign an owner to every unticked item and rerun it at the go or no-go meeting. Critical items are those whose failure produces wrong money or wrong stock on day one. Print or export the result and attach it to the sign-off. #### Why balances come first **Body:** Opening balances set the base that every later report depends on. Agree the trial balance, open invoices and valued stock with the legacy system on the same cutoff date, then freeze that date. A stock value that differs from the opening journal will show up in the first month close as unexplained variance, and unwinding it live is expensive. **Bullets:** - One cutoff date for GL, AR, AP and stock - Count stock, do not trust the old on-hand figure - Reconcile control accounts before releasing users - Keep the old system read-only for audit #### Common mistakes **Body:** Loading open production orders without issued quantities creates false shortages. Leaving default users and superuser rights in place is a control gap. Skipping a dry run means the real load is also the first timing test. And ending support on day three removes help just when the first month-end shows what was missed. **Cta:** Netray works with Business One partners on reporting and AI over live ERP data after go-live, read-only and on your servers, if that helps your first months. **Faq:** #### How long before go-live should the cutover plan exist? **Answer:** At least four weeks for a manufacturer, so the dry run and the stock count fit. The plan should list the tasks, owners, durations and the rollback decision point with a time attached. #### Should we go live at month start or mid-month? **Answer:** Most teams prefer the first working day of a period, since the opening balances then match a period boundary and the first close is cleaner. Mid-month is possible but needs careful handling of open documents. #### Can we run the old and new system in parallel? **Answer:** Briefly for reporting reconciliation, yes. Running both for transactions doubles the work and creates conflicting master data, so choose one system of record per process from the cutover date. #### What does hypercare usually cover? **Answer:** Daily triage of issues, fast fixes to configuration and layouts, extra training and support through the first period close. Two to six weeks is typical, set by the size and number of sites. ## Search terms sap business one go live checklist, sap b1 cutover plan, sap business one implementation checklist, sap b1 opening balances, sap b1 go live readiness, sap b1 data migration checklist, sap business one hypercare, erp go live checklist manufacturing --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json