ERP Implementation Guide

The ERP Implementation Roadmap for Mid-Sized Manufacturers: Phases, Roles and Timelines

This guide is a practical roadmap for those decisions. It sets out the eight phases of a manufacturing ERP implementation, who does what, how long each phase realistically takes, and the checkpoints that keep the project on track. An interactive roadmap shows how the timeline stretches as plants and entities are added.

Book my implementation consultation →

The short answer

An ERP implementation for a mid-sized manufacturer moves through eight phases: discovery, solution design, configuration, data migration, integration and compliance set-up, testing, training and cutover, then hypercare. A single-plant project with focused scope typically reaches go-live in four to seven months. Clean data, an empowered internal owner and disciplined scope decide the timeline more than the software.

On the Friday before go-live, the plant head walks the stores with a clipboard. Every rack has been counted, every open purchase order checked, every half-finished job on the shop floor tagged. On Monday morning, the first sales order will flow through the new system to purchase, production and dispatch without anyone opening a spreadsheet. That Monday is the moment everyone remembers. But it is decided months earlier, in a series of quieter decisions about scope, data, people and testing.

How long does an ERP implementation take?

There is no single number, but there are reliable reference points. Panorama Consulting’s 2026 ERP Report, based on 170 organisations surveyed between January 2025 and January 2026, found a median project timeline of 9 months. That sample has a median revenue of about $200 million and many multinational organisations, so it describes larger projects than a typical Indian mid-sized manufacturer.

Scenario Typical time to first go-live What drives it
Single plant, focused scope (inventory, purchase, sales, production, finance) 4–5 months Clean masters, standard processes, few integrations
Mid-sized manufacturer, 2–3 plants or warehouses 6–7 months Inter-unit transfers, multi-GSTIN, job work, more users to train
Multi-entity or multi-country (for example India + UAE) 8–10 months Consolidation, multiple tax regimes, staggered rollouts

These are planning ranges, not promises. The same software can take very different times in different plants. Scope, data condition and how much time your own people can give move the date more than anything else.

The implementation roadmap at a glance

The roadmap below shows a typical plan for a mid-sized manufacturer. Switch between scenarios to see how the phases stretch. Notice that data migration and change management start early and run in parallel; they are not tasks to leave until the end.

Indicative plan. Bars show when each phase is active; diamonds mark decision gates.

The eight phases, step by step

Before you start: readiness (2–4 weeks before kick-off)

Confirm the business case and the three to five outcomes the project must deliver, such as inventory accuracy, faster month-end close or on-time delivery. Appoint the internal project owner and process owners, free up their time, and start cleaning item, customer and vendor masters. Decide your target go-live window now.

Phase 1: Discovery and process mapping

The implementation team walks every process as it actually runs today: order to cash, procure to pay, plan to produce, record to report. That includes the spreadsheets, the phone calls and the workarounds. The output is a documented set of current processes, pain points and requirements, prioritised as must-have, should-have and later.

Phase 2: Solution design and fit-gap

Each process is mapped to how the ERP will run it. Where the standard system does not fit, the team decides between changing the process, configuring the system or, as a last resort, customising it. This is the phase where scope is won or lost.

Pothera’s view: Change the process before you change the software. Every customisation is code your business must test and maintain at every upgrade. Reserve it for what genuinely differentiates you.

Phase 3: Configuration and build

The system is set up to the agreed design: company structure, plants and warehouses, GST registrations, chart of accounts, item categories, bills of materials and routings, approval workflows, document formats, reports and dashboards. Process owners review the configuration in short cycles rather than waiting for one big demonstration.

Phase 4: Data migration

Data work starts in the first month and runs through to cutover. Masters are cleaned and de-duplicated, mapped to the new structure and loaded in at least two trial runs (“mock loads”) before the final load. Opening balances, open orders, stock by location and batch, and work in progress are planned for cutover day.

Phase 5: Integrations and compliance set-up

Connections to the e-invoice and e-way bill portals, banks, e-commerce channels, weighbridges or machines are built and tested. Compliance settings are verified: GST and HSN masters, TDS sections under the Income-tax Act, 2025, MSME vendor tags and the audit trail. Your CA should review these before testing begins.

Phase 6: Testing

System and integration testing proves that each process works end to end. User acceptance testing (UAT) then has your own key users run real scenarios with real data: a rush order, a rejected batch, a job-work challan, a credit note, a month-end close. Defects are fixed and retested until process owners sign off.

Phase 7: Training, cutover and go-live

Users are trained by role, ideally by your own key users (“champions”) in the language and terms the shop floor already uses. Cutover is planned hour by hour: final stock count, last transactions in the old system, final data load, verification and the first live transactions.

Phase 8: Hypercare and stabilisation

For four to six weeks after go-live, the implementation team stays close with a fast-response support desk, daily issue reviews and help with the first month-end close in the new system. Stabilisation ends when the first close is complete, key reports are trusted and support requests have fallen to normal levels. Optimisation and the next phase of scope follow.

Who does what: the implementation team

Most ERP problems are people problems first. Panorama’s 2026 report found that fewer than 25% of organisations put an intense focus on change management during implementation. Define the roles below before kick-off and protect the time they need.

Role Who Responsibilities Time commitment (plan for)
Executive sponsor MD, promoter or CFO Owns the outcomes, resolves conflicts between departments, approves scope changes, attends steering reviews 2–4 hours a fortnight
Internal project owner A respected senior manager Runs the plan with the partner, chases decisions, owns the issue log and go/no-go 50–100% during the project
Process owners Heads of sales, purchase, stores, production, quality, finance Define requirements, approve design for their area, sign off UAT 20–30%; more during design and testing
Key users (champions) 1–2 per department Test with real transactions, train colleagues, first line of support after go-live 30–50% during testing and training
Data lead Someone who knows your masters Cleans and validates masters, checks every mock load 30–50% during migration
IT lead Internal IT or a trusted provider Devices, access, connectivity, integrations, security As needed
CA / auditor Your statutory or tax advisor Reviews tax configuration, audit trail and opening balances Review points only
Implementation partner Project manager and consultants Methodology, configuration, migration tooling, training material, hypercare Full project

Five decision gates that keep the project on track

  1. Design sign-off. Process owners approve the to-be design and the list of any customisations. Nothing new enters scope without the sponsor’s approval.
  2. Data mock load 2 passed. The second trial load reconciles to the old system on stock, receivables, payables and open orders within agreed tolerances.
  3. UAT sign-off. Every priority scenario has passed with real data, and no critical defects remain open.
  4. Go/no-go. The sponsor, project owner and partner review the checklist below and decide formally. A short delay is cheaper than a failed go-live.
  5. Stabilisation exit. The first month-end close is complete in the new system, key reports are trusted and support volumes are back to normal.

Go-live readiness checklist

  • All priority UAT scenarios passed and signed off by process owners
  • Final data load rehearsed; stock, balances and open orders reconcile
  • E-invoice, e-way bill and bank integrations tested in the live environment
  • Every user trained for their role, with logins and devices working
  • Champions named for each department and shift
  • Cutover plan agreed hour by hour, including the physical stock count
  • Hypercare support desk, contacts and escalation path published
  • Rollback or contingency plan agreed for critical processes
  • Sponsor’s formal go decision recorded

Choosing your go-live date

Go live at the start of a month so that the first close is clean, and avoid your peak season, festival dispatch rush and the weeks around GST return due dates. 1 April is popular but rarely the calmest choice: year-end closing, audits and new financial-year changes compete for the same people. The start of a quarter after the audit has closed is often a better window. If you must go live on 1 April, start the project earlier so testing ends well before March.

Most mid-sized manufacturers do not need to stop production. Plan the cutover over a weekend or a planned shutdown, freeze non-urgent transactions for a day or two, and keep paper back-up for critical dispatches during the first week.

Phased or big-bang go-live?

Approach How it works Best when Watch out for
Big bang All modules and sites go live on one date Single plant, tightly connected processes, strong team Higher risk on go-live day; needs thorough testing
Phased by module Core (inventory, purchase, sales, finance) first; production, quality or HR later Teams with limited time, or complex production Temporary interfaces with old systems
Phased by site One plant first, then the rest Multiple plants or entities Inter-unit transactions across old and new systems

For most mid-sized manufacturers, Pothera recommends going live with all core modules together at the first site, then rolling out to further sites in quick succession. Production planning is the exception: if it is complex, it can follow a few weeks later.

Six things that derail implementations, and how to prevent them

  • Fit gaps found too late. Panorama found that an unexpected need for additional technology was the most common cause of budget overruns. Prevent it with scripted demos on your real processes during selection, and a thorough fit-gap in Phase 2.
  • Scope creep. New requests appear once people see the system. Keep a “later” list and protect the go-live scope.
  • Dirty data. Duplicated items and inconsistent BOMs surface during testing. Start cleansing before kick-off and run at least two mock loads.
  • No time for the core team. Key users still doing their full day jobs cannot test properly. Back-fill or rebalance workloads during design and testing.
  • Testing with ideal transactions. Test returns, rejections, partial dispatches, job work and month-end, not just the happy path.
  • Training too early or too generic. Train close to go-live, by role, with your own data and your own champions.

Get a draft implementation plan for your plant

Book a 30-minute implementation plan consultation. Tell us your plants, users and current systems, and we will share a draft phase-by-phase plan with a realistic go-live window.

Book my implementation consultation →

Frequently asked questions

How long does ERP implementation take for a mid-sized manufacturer?

A single-plant manufacturer with focused scope typically reaches go-live in four to five months; two to three plants usually take six to seven months; multi-entity or multi-country rollouts take eight to ten months or more. Panorama Consulting’s 2026 ERP Report found a median of nine months across a sample of larger organisations.

What are the phases of ERP implementation?

Discovery and process mapping, solution design and fit-gap, configuration and build, data migration, integrations and compliance set-up, testing, training and cutover, and hypercare. Data migration and change management run in parallel from the first month.

How much time will our own team need to give?

Plan for a project owner at 50–100% of their time, process owners at 20–30% (more during design and testing) and key users at 30–50% during testing and training. Under-resourcing the internal team is one of the most common reasons projects slip.

Should we go live on 1 April?

It is possible, but rarely the calmest choice, because year-end closing and audits compete for the same people. The start of a quarter after the audit closes is often better. Always go live at the start of a month.

Do we have to stop production during go-live?

Usually not. Most cutovers happen over a weekend or planned shutdown, with a short freeze on non-urgent transactions and a physical stock count before the final data load.

What is hypercare?

Hypercare is the four to six weeks after go-live when the implementation team provides intensive support: a fast-response help desk, daily issue reviews and help with the first month-end close in the new system.

Phased or big-bang: which is better?

Big bang suits a single plant with tightly connected processes and a strong team. Phasing by module or site reduces risk when time is limited or there are multiple plants, at the cost of temporary interfaces with old systems.

What should we do if the go-live date starts to slip?

Hold the go/no-go decision honestly. Reduce scope to what is ready, move non-critical items to the next phase, and delay a few weeks if critical tests have not passed. A short, planned delay costs far less than an unstable go-live.

About Pothera ERP

Pothera ERP by Bsquare Solutions (Noida, India) has implemented ERP for manufacturing and trading businesses for 25 years, with 1,000+ enterprise clients across India, the Middle East and Africa. Pothera’s implementation team works on the shop floor alongside your people, from process mapping and data migration to go-live and hypercare.

Talk to an ERP specialist →