ERP Implementation Checklist for Indian SME Manufacturers: 20 Steps Before Go-Live

Most ERP projects don’t fail during implementation. They fail at go-live — when the pressure of running live operations exposes everything that wasn’t properly prepared. This checklist is built from real go-live experience with Indian manufacturing companies.

Data Preparation

• Clean your item master — remove duplicate items, standardise naming conventions, confirm HSN codes for all items

• Validate opening stock — conduct a physical count and reconcile before data entry, not after

• Prepare BOM data — multi-level BOMs should be reviewed by production and QC, not just IT

• Clean supplier and customer master — correct GSTIN, PAN, bank details, and payment terms for every active party

• Define opening balances — accounts opening balances must be signed off by your chartered accountant

Configuration Validation

• GST and e-Invoice tested end to end — generate at least 5 test invoices through the IRP before go-live

• e-Way Bill integration tested — for goods movement above threshold, verify the workflow works before the first real dispatch

• Payroll configuration validated — run a parallel payroll for 1 month before switching to ERPNext payroll

• Workflow approvals set up — purchase orders, payment vouchers, and journal entries should have defined approval chains

• User roles and permissions audited — confirm no one has more access than they need

Training

• Role-specific training done — accounts team trained separately from store team trained separately from production team

• Training done in production environment, not demo — training on demo data creates false confidence

• SOPs documented for every key workflow — especially stock entry, payment entry, and production workflows

• Escalation path defined — users must know who to call when something doesn’t work on day one

Go-Live Readiness

• Cutover date agreed by all departments — accounts, production, and warehouse must all go live on the same date

• Parallel run plan defined — decide for how long you will maintain old records alongside ERPNext

• Backup of all legacy data — before you stop using the old system, export and archive everything

• IT infrastructure ready — internet connectivity at plant/warehouse, hardware tested, printer setup complete

• Support coverage confirmed — your consultant should be reachable for at least 30 days post go-live

• Success metrics defined — what does a successful go-live look like? Define it before you start, not after

The Most Common Reason Indian Manufacturers’ ERP Projects Fail at Go-Live

1. Opening stock was not properly validated — the first stock entry fails because quantities don’t match

2. GST configuration was not tested end to end — first invoice can’t be submitted to IRP

3. Key user went on leave during go-live week — no backup trained for critical workflows

4. Too many modules went live simultaneously — overwhelming the team on day one

I’ve managed 12+ ERP go-lives for manufacturing companies in India. If you’re approaching your go-live and want a pre-launch review, reach out directly.