TCO Worked Examples and Selection Checklists
ERP implementation timeline: phases, realistic durations and go-live timing
How long ERP implementation takes for Indian MSMEs, phase by phase, what stretches timelines, and how to time go-live around GST returns and financial year-end.
There is no reliable single figure for how long an ERP takes to implement, and published survey numbers vary widely with the size and scope of the projects surveyed. As a rough guide, a packaged accounting-plus-inventory tool for a small trader can go live within weeks, a multi-module cloud ERP for a small manufacturer commonly takes a few months, and a multi-entity or heavily customised project can run much longer. What reliably stretches timelines is the same everywhere: unclear scope, late data cleaning, customisation and key users without time for the project. This guide sets out the phases, illustrative durations and how to time go-live around Indian compliance dates.
It belongs to the 3–5-year ERP TCO guide section.
The phases
| Phase | What happens | Illustrative duration, small cloud ERP | Illustrative duration, multi-module manufacturer |
|---|---|---|---|
| Selection | Requirements, RFP, demos, negotiation | 4–8 weeks | 6–12 weeks |
| Design | Workshops, solution design, sign-off | 1–2 weeks | 3–6 weeks |
| Build and configuration | Masters, workflows, print formats, integrations | 2–4 weeks | 6–12 weeks |
| Data migration | Cleaning, test loads, final load | In parallel, 2–4 weeks | In parallel, 4–8 weeks |
| Testing (UAT) | Scenario tests by key users | 1–2 weeks | 3–6 weeks |
| Training | Key users, then end users | 1–2 weeks | 2–4 weeks |
| Go-live and hyper-care | Cut-over, parallel checks, intensive support | 2–4 weeks | 4–8 weeks |
These ranges are illustrative, not benchmarks. Ask each implementation partner for a plan with named phases, dates and the time they need from your staff, and ask their references whether the plan held.
Choosing a go-live date in India
Financial year start (1 April)
Going live on 1 April means opening balances are the audited closing balances of the previous year and the whole year sits in one system. The catch: March is the busiest month for accounts teams, and year-end closing in the old system overlaps with final testing. Many businesses prefer a go-live at the start of a quarter instead.
Start of a month or quarter
A go-live on the first day of a month keeps a GST return period in one system. Under the quarterly return (QRMP) scheme, starting with a quarter avoids splitting GSTR-1 data. Avoid going live in the days before GSTR-1 and GSTR-3B are due.
Around e-invoicing deadlines
If your AATO is ₹10 crore or more, invoices must be reported to the IRP within 30 days. A go-live problem that stops IRN generation for more than a few days creates a real compliance risk. Keep a fallback: the ability to generate IRNs through another route (for example, the portal or a GSP tool) during the first weeks.
Payroll
Change payroll systems at the start of a month, ideally at the start of a financial year so that TDS on salary and annual statements are in one system. See the payroll module guide.
What stretches timelines, and how to prevent it
| Cause | Prevention |
|---|---|
| Scope not written down; new requirements keep appearing | Sign off a solution design; route changes through a change-request process |
| Masters and opening balances not clean | Start data cleaning on day one; assign an owner per data set |
| Key users busy with daily work | Plan their hours; backfill routine work during peak project weeks |
| Heavy customisation | Prefer standard features; challenge each customisation by its business value |
| Integrations depending on third parties (banks, marketplaces, device makers) | Start integration conversations early and test separately |
| Decision-makers unavailable for sign-offs | Fix a weekly steering meeting with the owner or finance head |
| Partner staff changing mid-project | Name the team in the contract and agree replacement terms |
Illustrative plan for a 25-user rollout
| Weeks | Activity |
|---|---|
| 1–2 | Design workshops; data cleaning starts |
| 3–7 | Configuration; first test data load; e-invoice and e-way bill connection in sandbox |
| 8–9 | Second data load; integration testing (bank, attendance devices) |
| 10–11 | UAT by key users on scripted scenarios; fixes |
| 12 | End-user training; cut-over rehearsal |
| 13 | Go-live on the first day of the month; final opening balances loaded |
| 13–16 | Hyper-care; daily check of invoices, IRNs, e-way bills and stock |
| 17 | First month-end close and GST return data from the new system |
About four months from design to first month-end, plus selection beforehand. Use it as a template, not a promise.
Phased vs "big bang" go-live
| Approach | How it works | Advantages | Risks |
|---|---|---|---|
| Big bang | All modules and sites go live together | One cut-over, no temporary interfaces | High risk if something fails |
| Phased by module | Accounts and GST first, then inventory, then production | Smaller steps; earlier benefits | Temporary interfaces, longer total time |
| Phased by site | One branch or plant first, then others | Lessons learnt before rollout | Two systems running for a while |
For most MSMEs, a phased approach by module or site lowers risk, at the cost of a longer overall timeline. Price the temporary interfaces into the TCO, and read why ERP projects fail before you fix the plan.
FAQ
Can we run the old and new systems in parallel?
A short parallel run for critical processes, such as invoicing and stock, can catch errors, but full parallel running doubles work. Many projects instead reconcile key figures daily during hyper-care.
When should the subscription start?
Negotiate for the subscription to start at go-live or to include a free implementation period. If it starts at signing, delays add cost.
How do I know the project is ready to go live?
Use explicit criteria: UAT signed off, opening balances reconciled, IRN and e-way bill generation tested in production, users trained, rollback plan agreed.
Sources
- GST e-invoice portal (NIC IRP) — reporting time limit advisory
- CBIC GST — return periods and QRMP
- GST portal — return due dates
- Ministry of Corporate Affairs — financial year and books of account rules
