ERP Implementation Process: Avoid a Stalled Go-Live

Quick answer: A sound ERP implementation process runs in six phases: discovery and planning, process design, configuration and build, data migration, testing and training, and go-live with stabilisation. Most failures come from weak planning and dirty data, not from the software. Fix ownership, scope and data quality early, and test with real transactions before you switch over.

Many ERP projects in India start with energy and end in frustration. The go-live date slips twice, users keep their old Excel sheets "just in case", stock figures do not match the warehouse, and the finance team spends the first month-end fixing entries by hand. Leadership starts asking whether the ERP was a mistake.

In most cases the software is not the problem. The ERP implementation process was rushed or skipped steps that seemed optional. This guide explains each phase, the common traps at every stage, and a practical checklist to keep your project on track, whether you are moving from Tally or replacing an older system.

Why ERP Implementations Stall

The same causes appear again and again:

• No single owner. The project sits between IT, finance and operations, and nobody can make final decisions.
• Scope creep. Every department adds requests during the build, and the timeline stretches.
• Dirty master data. Duplicate customers, wrong item codes and old balances are migrated as they are.
• Too much customisation. The ERP is changed to copy old habits, making upgrades and support harder.
• Thin testing and training. Users see the system properly for the first time on go-live day.

There are also quieter causes. Vendors and consultants may be chosen on the lowest quote with an unrealistic timeline. Key users may be expected to work on the project after their normal duties. Integrations with banks, GST systems or existing software may be discovered late. None of these is unusual, and all of them can be planned for. Each phase below is designed to block one or more of these causes.

The Six Phases of the ERP Implementation Process

Phase 1: Discovery and planning

Define the business goals, modules in scope, locations and legal entities, budget and timeline. Appoint a project sponsor from leadership, a full-time project manager and key users from each department. If you are still deciding whether you need ERP at all, read when to move from Tally to ERP.

Phase 2: Process design

Map how each process will run in the ERP: order to cash, procure to pay, inventory, production, and record to report. Compare current processes with the ERP's standard flow and decide where you will change your process and where a real gap needs configuration or development. Document every decision.

Phase 3: Configuration and build

Set up the chart of accounts, tax settings, approval workflows, number series, print formats and user roles. Build only the custom reports and integrations that are truly needed, such as GST e-invoicing integration, banking files or a link to an existing HRMS.

Phase 4: Data migration

Clean and load master data (customers, vendors, items, bills of materials, assets) and opening balances (ledgers, stock, open orders, outstanding invoices). Plan at least one trial migration before the final one. Our article on ERP data migration mistakes lists the errors to avoid.

Phase 5: Testing and training

Test each process end to end with real examples, including returns, partial deliveries, credit notes and month-end closing. Then run user acceptance testing where key users sign off. Train users by role with their own transactions, not generic demos.

Phase 6: Go-live and stabilisation

Choose a cut-over date, freeze transactions in the old system, load final balances and go live. Keep extra support in place for the first one or two month-end closes, track issues daily and fix the most common problems quickly.

Change Management: Getting People to Use the ERP

An ERP changes how people work every day. Storekeepers, accountants, sales coordinators and plant supervisors all lose familiar shortcuts. If they do not understand why the change matters, they will find ways around the system, and data quality will suffer.

• Explain the reason early. Tell each department what problems the ERP will solve for them, such as fewer stock mismatches or faster month-end closing.
• Involve key users in design. People who help shape the process are more likely to support it and train others.
• Remove the old paths. After go-live, stop accepting reports or approvals from the old spreadsheets, or the ERP will never become the single source of truth.
• Celebrate early wins. Share results such as the first on-time closing or improved stock accuracy.
• Keep listening. Collect user issues weekly in the first months and fix the most common pain points quickly.

Plan time and budget for this work. It is often the difference between an ERP that is technically live and one that the business actually relies on.

Phased vs Big-Bang Go-Live: A Comparison

Factor	Big-bang (all at once)	Phased (by module or location)	Pilot first (one site, then rollout)
Speed to full use	Fastest	Slower	Medium
Risk on go-live day	Highest	Lower, spread over time	Low at the pilot site
Need for temporary integrations	None	Often needed between old and new systems	Some, until rollout ends
Load on users and support	Very high for a short time	Moderate over a longer time	Concentrated at one site first
Best fit	Smaller firms with simple operations	Larger firms with many modules	Multi-plant or multi-branch companies

ERP Implementation Checklist: What to Do at Each Step

Use this checklist as the backbone of your project plan. Review it at every steering meeting and mark each item as done, in progress or at risk, with a named owner.

1. Appoint an owner and a steering group. Name a business sponsor with authority, a project manager and one key user per department, and set a fortnightly review meeting.
2. Freeze the phase-one scope. Agree in writing which modules, entities and reports go live first, and park new requests for a later phase.
3. Design processes before configuring. Sign off process maps for each department so configuration follows agreed rules.
4. Prefer standard features. Change a process before you change the software, and approve every customisation with a clear business reason.
5. Clean data early. Start master data cleanup in the first month, assign owners for each data type and run at least one trial migration.
6. Test with real scenarios. Build test cases from last year's actual transactions, including exceptions, and get key users to sign off.
7. Train by role. Give each user group hands-on training on their own daily tasks, with short guides they can refer to later.
8. Plan cut-over in detail. List every cut-over task with owner and time, including stock count, final balances and access to the old system.
9. Support the first month-ends. Keep consultants and key users available for the first one or two closings, and track issues until they are closed.

After go-live: the first 90 days

Go-live is not the finish line. In the first three months, track a short list of measures: open support tickets, transactions still done outside the ERP, time taken for month-end closing, and stock accuracy after cycle counts. Hold a review at the end of each month with key users and decide which fixes and small improvements to make next. Once the system is stable, plan phase two, such as advanced reports, more integrations or additional locations, based on what the business has learned.

What Affects ERP Timelines and Cost

Each project is different, so avoid comparing timelines without comparing scope. The main drivers are:

• Number of modules, legal entities and locations.
• Industry complexity, such as production planning in manufacturing ERP or project costing in construction.
• Volume and quality of data to migrate.
• Number of integrations and custom reports.
• Availability of key users, who usually still have their day jobs.

Hidden costs often appear after go-live: extra licences as more users join, report changes, additional training for new staff and annual support. Ask vendors to include these in a three-year cost estimate, so the comparison between options is fair.

The most controllable factor is your own team's time. Projects move faster when key users get dedicated hours for the ERP each week.

Frequently Asked Questions

What are the main steps in the ERP implementation process?

Discovery and planning, process design, configuration and build, data migration, testing and training, and go-live with stabilisation. Some teams add a post-go-live optimisation phase.

How long does ERP implementation take?

It depends on scope, data and integrations. A focused rollout for a small company can take a few months, while multi-site or manufacturing projects take longer. A phased plan reduces risk.

Who should lead an ERP project?

A senior business leader should sponsor it, supported by a dedicated project manager. IT plays a key role, but ERP changes business processes, so the business must own decisions.

Should we customise our ERP?

Only where there is a real business need that standard features cannot meet. Heavy customisation increases cost and makes upgrades harder.

What is the biggest cause of ERP failure?

Weak ownership and poor data quality are the most common causes, followed by limited testing and training. All of them can be addressed with the checklist above.

How Affix Center Can Help

Affix Center helps Indian businesses plan and run ERP projects with clear ownership and realistic timelines. Our ERP and HRMS team handles process design, configuration, integrations and data migration, and our enterprise advisory services help with selection, scope and project governance. Where a standard product does not fit, we can build customised ERP modules.

If your ERP project is about to start or has stalled, contact us for a practical review.