An ERPNext go-live checklist should be built around the work people must complete on their first production day, not just a list of enabled modules. An interface can look ready while the warehouse posts against the wrong location or accounting discovers opening balances that do not reconcile. Those problems become more difficult once real transactions depend on the new system. Preparation is therefore a business exercise as much as a technical one.
Start with a real working day rather than module names
Ask sales to create an order, the warehouse to ship part of it and accounting to process the agreed invoice. Follow the same scenario when the customer returns items or cancels the outstanding quantity. Every step needs an owner, an expected record and a clear exception procedure.
A process map should identify which teams receive each handoff and which approvals are mandatory. If the process owner cannot explain an exception before launch, a new screen will not fix that uncertainty.
Clean and approve your master data
Inventory masters need consistent Item codes, units of measure, warehouses and batch or serial rules. Customer and supplier records need valid naming and payment terms. Accounting teams should verify the Chart of Accounts and tax settings. Duplicate or inactive records must be handled deliberately instead of imported wholesale.
Assign a named owner to approve every migration dataset. Opening inventory, receivables, payables and outstanding documents require a common cutover point so teams do not reconcile different dates.
Prove role-based access with employee accounts
Permission testing is part of business testing. Verify who can read, create, submit, cancel and amend documents, including company and warehouse restrictions. The intended approver should be able to act without giving everyone an administrator account.
Use actual role profiles in UAT. A workflow that succeeds only under Administrator is not proof that warehouse staff, buyers or accountants can use it safely.
Test the abnormal day as thoroughly as the normal one
Run scenarios with partial deliveries, backdated stock entries, returns, invoices paid in instalments, supplier cancellations and network retries. For manufacturing, include material shortages, scrap, partial production and quality holds. For integrations, confirm that repeated webhook events do not create duplicate documents.
Each UAT case should have prerequisites, expected results, evidence, severity and an owner. A clear release gate prevents unresolved financial or inventory defects from being hidden behind successful user-interface demonstrations.
Cutover, opening balances and rollback
Agree on the final transaction in the old system, the migration window and the moment the new platform becomes authoritative. Reconcile record counts and balances, not just a total Trial Balance. For stock, consider Item, Warehouse, Batch, quantity and valuation.
Document who signs off each reconciliation and what triggers rollback. A backup is not a recovery strategy until restoration has been tested in a separate environment.
Plan training and hypercare before launch
Training should match tasks: sales, warehouse, purchasing, accounting, managers and approvers need different examples. Make short reference guides for high-frequency transactions and exception handling. Provide a reliable place for users to report defects and record their impact.
During hypercare, assign responsibilities for permission issues, integration failures, accounting differences and stock mismatches. Define priorities and escalation channels before the first live transaction is created.
A final decision gate
Do not approve go-live solely because most checklist rows are marked complete. Check whether all business-critical transactions work for real users, whether opening balances reconcile and whether the team has a safe way to respond to failures.
For more preparation, see ERPNext services, ERP data migration and security and governance. Use those topics as prompts for a focused readiness review.
