SAP Business One Go-Live Cutover Checklist
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.
0 of 33 items complete
16 critical items still open - these are the highest-risk gaps.
Data readiness
Opening balances
Configuration and security
Integrations and reports
Cutover execution
Training and hypercare
Tick each item that is complete. Any unticked critical item should be resolved or consciously accepted before the go-live decision.
Second opinion on your cutover plan
Optional: a short review of your cutover plan and hypercare approach.
Optional. The tool and every export work without this. No spam.
How to use it
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
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.
- 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
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.
Frequently Asked Questions
How long before go-live should the cutover plan exist?
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?
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?
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?
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.
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.
Related Tools
SAP Business One User-Defined Field Planning Worksheet
An editable worksheet to specify every user-defined field before it is created: table, name, type, size, valid values and reason.
SAPSAP Business One Manufacturing Fit Assessment
Answer ten questions about your manufacturing complexity and see whether Business One fits as is, needs add-ons or needs a closer look.
SAPSAP Business One Database Tables Reference
Searchable lookup of the core SAP Business One tables, with the matching row table and what each one stores.
SAPSAP Business One Production Component Shortage SQL Generator
Pick a status, due date and warehouse and get a query that shows components short against on-hand stock for open production orders.
More SAP tools
See all- SAP Business One Production Order Checklist
- SAP B1 Item Master Import Template (DTW)
- SAP B1 MRP Setup Readiness Assessment
- SAP B1 Implementation Cost Calculator
- SAP Business One Go-Live Readiness Checklist
- SAP Business One Implementation Project Charter Template
- SAP Business One BOM Cost Rollup Worksheet
- SAP Business One Cycle Count Variance Worksheet
- SAP Business One License and 5-Year TCO Calculator
New to SAP Business One? Start with the SAP Business One guide and toolkit.
Keep exploring
Free tools
- SAP Business One Go-Live Readiness ChecklistA five-group checklist to confirm an SAP Business One implementation is ready for cutover, with the critical blockers marked.
- SAP QM Go-Live and Cutover ChecklistA checklist of what to confirm before switching on SAP Quality Management: master data, integration, authorizations, migration and hypercare.
- SAP SD Go-Live and Cutover Readiness ChecklistA readiness checklist for sales and distribution cutover: data, configuration, interfaces, testing and hypercare.
ERP fixes and how-tos
- Private AI for SAP Business One: Service Layer, a read replica and a local modelAdd a private AI assistant to SAP Business One: Service Layer reads, SQL Server or HANA replica, document index, local LLM, permissions and approvals.
- SAP Business One production planning: MRP, production orders, cost and variancesSAP Business One production planning end to end: MRP, planned to released orders, cost rollup, variance reporting and when you need a manufacturing add-on.
- What is the latest version of SAP Business One, and how to plan an upgradeHow SAP Business One is versioned (10.0 plus quarterly feature packages), how to find the current one, and a practical upgrade checklist for on-prem setups.
Guides
- ERP Go-Live Readiness Assessment ChecklistValidate ERP go-live readiness with a 100-point checklist covering data, integrations, training, cutover, and support. Prevent post-go-live emergencies.
- ERP Cutover Planning Best PracticesPlan and execute a flawless ERP cutover with rehearsal strategies, task sequencing, and rollback procedures. Minimize downtime and operational disruption.
AI on your ERP
- AI for SAP Business One Inventory: Stock, Batches, Bins and ValuationPrivate AI over SAP Business One inventory: OITW stock, batches, serials, bins and valuation. Answers grounded in live data via Service Layer or SQL views.
- AI for SAP Business One, Without Sending Your Books to a Public APIAdd AI to SAP Business One without sending customer data or financials to a public API. Service Layer and DI API integration, sized for an SMB budget.
Integrations
- How to use ChatGPT with SAP Business OneUsing ChatGPT with SAP Business One: exports versus live Service Layer access, custom GPT actions, enterprise data controls, and when a private model fits better.
- How to add AI agents to SAP Business OneHow to put AI agents on SAP Business One: Service Layer tool design, read-only first, draft documents for human approval, and an on-prem model option.