An ERP implementation has eight phases: discovery and process mapping, solution design and fit-gap, configuration and build, data migration, integrations and compliance set-up, testing, training and go-live, and hypercare. For a mid-sized Indian manufacturer, the first go-live typically takes 4 to 5 months for a single plant and 6 to 10 months for several plants or entities, according to Pothera ERP’s implementation guide. Clean data and an empowered internal owner affect the schedule more than the software does.

What are the 8 phases of an ERP implementation?

The eight phases run in this order, after a short preparation stage before kick-off.

Phase Name One-line purpose Gate that closes it
Before kick-off Preparation Agree the business case, owners and go-live window Project charter approved
1 Discovery and process mapping Document how work really happens today Requirements prioritised
2 Solution design and fit-gap Decide how the ERP will support each process Design sign-off
3 Configuration and build Set up the system for your company Configuration reviewed
4 Data migration Clean and load masters, balances and stock Mock load 2 passed
5 Integrations and compliance set-up Connect e-invoice, e-way bill, banks, machines Live tests passed
6 Testing Prove the system works on real scenarios UAT sign-off
7 Training, cutover and go-live Prepare people and switch over Go/no-go decision
8 Hypercare and stabilisation Support users until reports are trusted Stabilisation exit

How long does each stage take?

There is no single answer, because timelines depend on scope, plants and data quality. Pothera’s ERP implementation roadmap guide gives these planning ranges for time to first go-live:

Scenario Time to first go-live
Single plant, focused scope 4 to 5 months
2 to 3 plants or warehouses 6 to 7 months
Multi-entity or multi-country (for example India and UAE) 8 to 10 months

For context, Panorama Consulting’s 2026 ERP Report (170 organisations) found a median timeline of 9 months. Its sample had a median revenue of about $200 million, so it skews larger than a typical Indian mid-sized manufacturer.

Before kick-off: what should you prepare?

Spend two to four weeks confirming why you are doing the project and who owns it. Agree three to five outcomes you can measure, such as faster month-end close or accurate stock. Appoint an executive sponsor and an internal project owner. Start cleaning your master data and choose a go-live window.

Skipping this stage is the most common reason projects drift later.

Phase 1: Discovery and process mapping

Discovery documents how your business actually runs today, including the workarounds. Sit with sales, purchase, stores, production, quality and finance, and map each process as it is, not as the manual says. Then rank every requirement as must-have, should-have or later.

  • Output: a prioritised requirements list and process maps
  • Common mistake: mapping the official process and missing the Excel sheets that really run the plant

Phase 2: Solution design and fit-gap

Fit-gap analysis compares your processes with what the ERP does, and decides how to close each gap. For every gap you have three choices: change the process, configure the system, or customise as a last resort. Pothera’s guide recommends changing the process before changing the software, because customisation adds cost and makes upgrades harder.

  • Output: a signed-off design
  • Gate: design sign-off
  • Common mistake: discovering a fit gap late. Panorama’s 2026 report found that unexpected need for additional technology was the most common cause of budget overruns.

Phase 3: Configuration and build

Configuration sets the system up for your company. This includes the company structure, GST registrations, chart of accounts, bills of materials (BOMs), routings, approval flows and reports. Review in short cycles with the process owners, so problems appear early.

  • Output: a configured system the team has seen and approved
  • Common mistake: letting scope grow during build

Phase 4: Data migration

Data migration starts in the first month, not the last. Clean and map your item, party and account masters, then plan opening balances and opening stock for the cut-over. Run at least two mock loads and reconcile each one against your existing books.

If you are moving from Tally and Excel, read how to migrate data from Tally and Excel to a steel ERP.

  • Output: reconciled data and a rehearsed final load
  • Gate: second mock load passed
  • Common mistake: loading dirty data and fixing it after go-live

Phase 5: Integrations and compliance set-up

This phase connects the ERP to the outside world and verifies Indian compliance. Set up e-invoicing, e-way bills, banks and, where relevant, machines. Check GST, HSN codes, TDS, MSME tags and the audit trail with your CA. Test each connection live, not only in a sandbox.

  • Output: working integrations and a CA-reviewed compliance set-up
  • Common mistake: leaving compliance checks until the week before go-live

Phase 6: Testing

Testing proves the system works on your real scenarios, not just the happy path. Run system and integration tests first, then user acceptance testing (UAT) with the people who will use the system. Use awkward cases: a rush order, a rejected batch, a job-work challan, a credit note and a month-end close.

  • Output: signed-off test scenarios
  • Gate: UAT sign-off
  • Common mistake: testing only the cases that work

Phase 7: Training, cutover and go-live

Train by role, led by internal champions, and rehearse the cut-over hour by hour. Plan the physical stock count, the final data load and who is on call. Go live at the start of a month, and avoid peak season, festival dispatch rushes and GST return due dates. Most plants do not need a full stoppage. A weekend or planned shutdown, a short freeze on non-urgent transactions and a paper backup for critical dispatches are usually enough.

  • Output: trained users, a rehearsed cut-over and a recorded go decision
  • Gate: go/no-go
  • Common mistake: training too early or too generally

Phase 8: Hypercare and stabilisation

Hypercare is four to six weeks of intensive support after go-live. It ends when the first month-end close is complete and the team trusts the reports. Keep a visible support desk, fix issues quickly and track what users still struggle with.

  • Output: a stable system and trusted reports
  • Gate: stabilisation exit

Who does what in an ERP implementation?

An ERP project needs both internal owners and an implementation partner. Pothera’s guide suggests these time commitments:

 

 

Role

Who Time commitment
Executive sponsor MD, promoter or CFO 2 to 4 hours a fortnight
Internal project owner Senior manager 50 to 100% during the project
Process owners Heads of sales, purchase, stores, production, quality, finance 20 to 30%, more during design and testing
Key users (champions) 1 to 2 per department 30 to 50% during testing and training
Data lead Accounts or MIS lead 30 to 50% during migration
CA or auditor External Review points only
Implementation partner ERP vendor team Full project

What are the five decision gates?

Gates are points where you pause and decide whether to continue. They are design sign-off, the second mock load passed, UAT sign-off, the go/no-go decision and the stabilisation exit. Each gate needs a named person who can say no.

What derails ERP implementations?

Six things cause most problems:

  1. Fit gaps discovered late
  2. Scope creep during build
  3. Dirty data
  4. Core team members with no time for the project
  5. Testing only the happy path
  6. Training too early or too generic

Panorama’s 2026 report also found that fewer than 25% of organisations put intense focus on change management, which is why training and champions matter.

How does this apply to a steel or wire and cable manufacturer?

The phases are the same, but the data and tests are industry-specific. A steel plant should test heat-wise stock, yield and cost per tonne in Phase 6. A cable plant should test length-based stock, drum tracking and metal-price costing. See ERP for steel pipe and tube manufacturers and the wire and cable ERP checklist for examples of what to test.

In the configuration phase, you will set up inventory management and production and planning management, so ask to see both working on your own data.

What does an ERP implementation cost?

Cost depends on users, modules, plants and deployment (cloud or on-premise). Get a starting range from the Bsquare ERP cost estimator, then ask each vendor for a phase-wise quote.

Frequently asked questions

  1. What are the phases of an ERP implementation?
    There are eight: discovery, solution design and fit-gap, configuration, data migration, integrations and compliance set-up, testing, training and go-live, and hypercare.
  2. How long does an ERP implementation take for a manufacturer in India?
    Pothera’s guide suggests 4 to 5 months to first go-live for a single plant, 6 to 7 months for 2 to 3 plants, and 8 to 10 months for multi-entity or multi-country setups.
  3. Which phase takes the most effort?
    Data migration and testing usually need the most internal time, because clean data and real scenarios depend on your own team.
  4. What is fit-gap analysis in ERP?
    It is a comparison of your processes with the ERP’s standard features, and a decision for each gap: change the process, configure the system or customise.
  5. What is ERP hypercare?
    Hypercare is four to six weeks of intensive support after go-live, ending when the first month-end close is done and the reports are trusted.
  6. When is the best time to go live with a new ERP?
    At the start of a month, away from peak season, festival dispatch rushes and GST return due dates.
  7. Do we need to stop production during go-live?
    Usually not a full stoppage. Many plants use a weekend or planned shutdown and a short freeze on non-urgent transactions.
  8. How much internal time does an ERP project need from our team?
    The project owner may need 50 to 100% of their time, process owners 20 to 30%, and key users 30 to 50% during testing and training.

Plan your ERP implementation with Pothera

Pothera ERP is built by Bsquare Solutions in Noida, India. According to the Pothera implementation guide, the company has been implementing ERP for manufacturing and trading businesses for 25 years and serves 1,000+ clients across India, the Middle East and Africa.

Read the full ERP implementation roadmap guide, then book a free implementation consultation to get a draft phase-by-phase plan for your plant. You can also visit Pothera ERP or Bsquare Solutions.

 

Leave a Reply

Your email address will not be published. Required fields are marked *