DotOne teamWhat is ERP implementation?
ERP implementation is the project of taking an ERP from contract to daily use: mapping your processes, configuring the system, moving your data, training your people and switching over. For a small or mid-sized manufacturer on a cloud ERP, it is usually weeks, not years, if the scope is kept tight.
The 6 steps of ERP implementation
- Discovery. Map how orders, purchase, stores, production, quality, dispatch and accounts work today, and list the reports management needs.
- Scope and design. Agree what goes live first (phase 1) and what waits (phase 2). Write it down and freeze it.
- Configuration. Set up items, BOMs, warehouses, approval rules, user roles and document formats in the ERP.
- Data migration. Clean and load masters (items, customers, vendors, BOMs) and opening balances (stock, receivables, payables).
- Testing and training. Run real transactions end to end, then train each person on the screens they will use.
- Go-live and support. Switch over on a fixed date, run the old and new side by side only where you must, and support users through the first month-end.
How long does ERP implementation take?
| Business | Typical scope | Typical time |
|---|---|---|
| Small trading or service business | Sales, stock, purchase, billing | 3 to 6 weeks |
| Single-plant manufacturer | Adds BOM, production, quality | 4 to 10 weeks |
| Multi-plant manufacturer | Adds inter-plant transfers, HR, payroll, integrations | 2 to 4 months, in phases |
| Large enterprise on an on-premise suite | Heavy customisation, many integrations | 6 to 18 months |
The biggest factors are not the software: they are how clean your masters are, how quickly decisions get made, and how much customisation you insist on before go-live.
Data migration: what to move and what to leave
- Move: item master with units, HSN and reorder levels; BOMs; customers and vendors with GSTINs; open sales and purchase orders; opening stock by location; open receivables and payables.
- Leave behind: years of closed transactions. Keep the old system or exports for reference instead of migrating history.
- Clean first: remove duplicate items and parties before loading. See our master data management guide.
Change management: getting people to use it
- Name one owner inside the business with the authority to make decisions, not just a coordinator.
- Involve the people who do the work (stores, supervisors, accounts) in testing, not only managers.
- Switch off the old way. If the Excel sheet keeps running in parallel, the ERP will not be trusted.
- Train by role, on real transactions, and give each person a one-page guide for their daily screens.
- Review weekly for the first month and fix friction quickly.
Common ERP implementation mistakes
- Scope creep. New requests added mid-project push go-live out by months. Park them for phase 2.
- Customising before using. Run the standard process first; customise only what still does not fit.
- Dirty data. Loading duplicates and wrong units breaks stock and costing from day one.
- No decision-maker. A coordinator without authority cannot unblock decisions.
- Training too early. Training six weeks before go-live is forgotten by go-live.
Go-live checklist
- Phase 1 scope signed off, phase 2 list written down
- Masters cleaned and loaded; BOMs checked against one real batch
- Opening stock counted and loaded by location (see stocktaking)
- Approval rules and user roles tested
- Invoice, PO and challan formats approved
- Every user trained on their screens
- Cut-over date fixed and the old process switched off after it
How DotOne implementation works
DotOne implementations run in four stages: we map your workflows and reporting needs; configure BOMs, production, inventory and user roles; migrate master data and connect shop-floor systems; then go live with training and ongoing support. Using fit-to-standard templates and a dedicated onboarding team, most customers are live in 4 to 6 weeks. Scope is agreed as phase 1 and phase 2, and anything new after sign-off goes through a change request, so go-live dates hold.