Key takeaways
- Stages
- Study, configure, migrate, train, go live, stabilise
- Typical time
- 4–6 weeks for one plant; longer for groups and many drawings
- Biggest risk
- Dirty masters and no internal owner
- Cut-over
- A fixed date, opening stock counted, old registers closed
- After go-live
- Daily checks for two weeks, then weekly
What an ERP implementation actually involves
Installing ERP software takes an afternoon. Implementing it, so that the gate, store, floor, quality, dispatch and accounts all work in it every day, is a project of a few weeks. The work is mostly about the plant, not the software: agreeing how each record will be made, setting up the masters that describe your items and processes, moving opening data across, and training people who have used registers for years.
The plan below is the one our engineers follow for single-plant implementations. Multi-plant groups follow the same stages, repeated or overlapped per plant.
| Week | Stage | Main output |
|---|---|---|
| 1 | Process study on the floor | Map of every register, document and approval; scope agreed |
| 2–3 | Configuration | Masters, routings, print formats, approvals and user roles set up |
| 4 | Data migration and testing | Opening balances, stock and open orders loaded; dry run |
| 4–5 | Training | Each role trained on its own screens with its own documents |
| 6 | Go-live | Cut-over date; first dispatch and first GST entries on the ERP |
| 7–12 | Stabilisation | Daily then weekly checks; reports and costing switched on |
Stage 1: Process study on the floor
The implementation starts where the work happens. Engineers walk the plant with each department head and list every register, document, approval and report in use. For each one they record who makes it, when, from what source, and who reads it.
The output is a short document that answers three questions: which records the ERP will replace, which documents it must print in which format, and which approvals it must enforce. It also identifies the exceptions, such as material sent for job work without a challan or verbal purchase approvals, that need a decision before the system can model them.
In a fastener plant the study found that heat numbers were written on the coil tag at receipt but not carried onto the job card. The rule agreed: the heat goes on the lot at GRN and prints on every document after that. It is a one-line decision that makes traceability possible.
Stage 2: Configuration
Configuration turns the study into the system. With an industry edition most of the structure already exists; the work is filling it with your data and rules.
- Company, plants, stores and racks
- Item masters with units, HSN codes and conversions
- Bills of material, routings and process stages
- Party masters with GSTINs and terms
- Print formats: invoice, challan, label, job card
- Approval rules for purchase, dispatch and credit
- User roles: who sees and edits what
- Number series for every document
Masters deserve the most care. Duplicate parties, inconsistent item names and wrong units cause more go-live trouble than any software issue. Clean them once, with one owner in the plant responsible for approving new masters after go-live.
Customise the documents, controls and reports that are truly yours. Where the system already does something a slightly different way from your register, try its way for a month first: many old habits exist only because the register could not do better.
Stage 3: Data migration
Migration moves your opening position into the ERP. It does not need to move years of history; that stays in the old system for reference.
| Data | Source | How it is checked |
|---|---|---|
| Masters | Tally, Excel, registers | De-duplicated and approved by the plant owner of masters |
| Ledger balances | Tally or accounts | Trial balance matches on the cut-over date |
| Outstanding bills | Accounts | Party-wise totals match ledger balances |
| Opening stock | Physical count | Counted by item and lot on the cut-over date |
| Open orders and POs | Sales and purchase files | Pending quantities confirmed with each department |
| Material at job workers | Challan book | Confirmed with each processor before go-live |
A dry run, entering a few real days of transactions into a test copy, catches most migration mistakes before they matter.
Stage 4: Training, role by role
Training works when each person learns only their own screens, using their own documents. A guard does not need the accounts module; a storekeeper needs the gate, receipt, issue and stock screens, and needs to practise them with this week's real challans.
- Department heads first. They decide how work is done and will answer their team's questions.
- Operators next, in small groups. Gate, store, supervisors, inspectors, dispatch, accounts.
- Practice on real documents. Yesterday's receipts, today's job cards, this week's invoices.
- In their words. Training uses the terms the team already uses on the floor.
- A one-page guide per role. Kept at the workstation for the first weeks.
Stage 5: Go-live and cut-over
Go-live is a date, not a gradual drift. On the agreed day, old registers are closed, opening stock is counted, and every new transaction is entered in the ERP. Running two systems for operations "until people are comfortable" usually means the ERP is never trusted.
The go-live checklist
- Opening stock counted and entered by item and lot
- Ledger and bill balances agreed with the accountant
- Open orders, POs and job-work challans loaded
- Print formats tested on the actual printers
- Scales, scanners and phones tested at each station
- Users created with the right roles and passwords
- E-invoice and e-way bill credentials configured and tested
- Old registers signed and closed on the cut-over date
The first dispatch and the first GST entries made on the ERP are the real milestones. Our engineers are on site for go-live day and the days after it.
Stage 6: The first 90 days
Most questions arrive in the first two weeks, when real situations meet the new system: a supplier sends a partial delivery, a job worker returns two challans' worth on one, an urgent order skips a stage. Plan for them:
- Weeks 1–2: daily review of entries with each department; fix masters and rules as issues appear.
- Weeks 3–6: weekly reviews; switch on planning, costing and owner reports once data is reliable.
- Month 3: first full-month reports compared with the old method; retire remaining spreadsheets.
A named support engineer who knows your plant answers questions on phone and WhatsApp, which matters more in this period than at any other time.
Who needs to be involved from your side
| Role | Responsibility | Time needed |
|---|---|---|
| Owner or director | Agrees scope and rules; settles disputes between departments | A few hours a week |
| Project champion | Single point of contact; follows up on every open item | Half their time during the project |
| Masters owner | Approves items, parties and BOMs; keeps them clean afterwards | Daily during configuration |
| Department heads | Confirm their process; train and supervise their teams | Several sessions each |
| Accountant | Opening balances, GST settings, ledger mapping | Concentrated around migration |
What delays go-live, and how to avoid it
- No internal owner. When nobody in the plant owns the project, open items wait. Name a champion on day one.
- Dirty masters. Clean parties and items before import, not after.
- Scope that keeps growing. Record new ideas for phase two; go live with what was agreed.
- Training too early or too generic. Train close to go-live, on real documents.
- A soft cut-over. Running registers and ERP side by side for operations splits the truth.
- Stock not counted. An uncounted opening stock haunts every report for months.
Questions buyers ask
How long does ERP implementation take?
For a single plant on an industry edition, four to six weeks on site is typical. Multi-plant groups, foundries with many drawings and plants needing significant customisation take longer, often six to ten weeks or more.
What are the main steps of ERP implementation?
Process study, configuration of masters and documents, data migration, role-by-role training, go-live with a fixed cut-over date, and a stabilisation period with close support.
Should we run the old system in parallel?
For accounts, a one-month parallel run that compares trial balances is sensible. For operations such as stock and production, a clean cut-over on a fixed date works better than running two systems.
What data has to be migrated?
Masters, ledger balances, outstanding bills, opening stock by item and lot, open sale and purchase orders, and material at job workers. History usually stays in the old system.
Who does the implementation at eManage?
eManage's own implementation engineers from Ludhiana, on site at your plant. The same team provides support after go-live.
What does implementation cost?
It is usually quoted as a one-time fee based on scope, number of plants and on-site days, separately from licences. See how much ERP costs.