An ERP implementation timeline becomes predictable when it follows one workflow and names the decisions required at each stage.
Phase 1: map the workflow
Document the trigger, users, records, approvals, exceptions, output, and acceptance result. For a sales-to-dispatch workflow, that means the quotation, confirmed order, material check, production, quality, dispatch, and invoice trail.
Phase 2: prepare data
Clean item codes, units and conversions, parties, warehouses, BOMs, recipes, opening stock, open orders, and active WIP. Assign data owners and compare control totals before import.
Phase 3: configure roles and screens
Set numbering, locations, stages, work centres, permissions, approvals, labels, and reports. Keep each setting tied to the first workflow.
Phase 4: test real cases
Run an ordinary transaction and the exceptions your team sees: partial production, alternate UOMs, rejection, rework, short receipt, split dispatch, and cancellation. Reconcile stock, values, GST, WIP, and order balance.
Phase 5: train and cut over
Train each role on the transactions it owns. Freeze old files, take the final opening position, import and sign off the data, then complete the first live workflow.
Phase 6: stabilise and expand
Review incomplete records, user questions, data quality, and report totals daily during the first week. Expand only after the first workflow is reliable.
FactoStack Factory Go-Live targets seven days for one agreed workflow when inputs are clean and the team is available. Use the checklist, cost guide, Excel migration plan, and pricing page to prepare.
Factory Go-Live covers the agreed first workflow; custom modules, integrations, and historical reconstruction receive their own scope and quote.
Frequently Asked Questions
Written by
Sudharsan GS
Building FactoStack with Indian MSME manufacturers across inventory, production, dispatch, GST, and Tally workflows.
