What ERP implementation actually costs in India
Nobody publishes numbers, so every conversation starts from zero. Here are the variables that move them.
Licence cost is the number everyone compares and the least important one. Implementation, data migration, and the change in how people work are where the money and the risk actually sit.
Asking what an ERP implementation costs is like asking what a building costs. The honest answer is a range so wide it is useless without knowing what is being built — which is why most firms decline to answer at all and ask you to get in touch.
That is unhelpful, because you need a rough shape before you can have a sensible conversation. So rather than a number, here is what actually moves the number, and what tends to be missing from the quote you will receive.
The four things that move the cost
In descending order of impact. Notice that none of them is the licence.
How many processes change
The single biggest driver. Moving one process is a project. Moving procurement, production, dispatch, and finance together is a programme, and it multiplies rather than adds — because they interact.
The state of your data
Clean, consistent master data makes migration routine. Duplicate customers, inconsistent item codes, and fifteen years of accumulated variation make it the longest task in the plan. This is usually the biggest surprise in the timeline.
Integrations
Every system that must exchange data adds work — and integrations to old software with no proper interface add much more. Tally, legacy desktop applications, and machine data are all doable and none are quick.
Whether people change how they work
The cost nobody quotes. Training, parallel running, and the productivity dip during transition are real. Implementations that skip this line item do not avoid the cost; they just pay it in failure.
What is missing from most quotes
Ask about each of these explicitly. The answers separate serious proposals from optimistic ones.
- Data migration — is it in scope, and for how much history?
- Data cleansing — who does it, you or them, and is it costed?
- Integration to your existing systems, named individually.
- Training, and whether it is a session or a programme.
- Parallel running — is it included, and for how long?
- Post-go-live support, and what happens when the implementation team leaves.
- Annual licence and maintenance escalation for years two and three.
Two quotes for 'the same' project
This is the most common trap. The cheaper proposal is frequently the more expensive project.
The lower quote
- Licences and configuration only
- Data migration listed as 'client responsibility'
- Training: two days, at go-live
- Integrations 'to be scoped separately'
- No parallel run
- Support billed hourly after handover
The higher quote
- Licences, configuration, and process design
- Migration and cleansing of agreed history
- Role-based training with follow-up
- Named integrations, specified and priced
- Parallel run until reconciliation passes
- Fixed support period after go-live
How to make this cheaper, honestly
Reduce scope before you negotiate rate. A smaller first phase costs less, delivers sooner, and tells you whether the partner is any good while the stakes are low. Negotiating a lower day rate on an oversized scope saves the least and risks the most.
Clean your master data before migration starts, using your own people. It is unglamorous and it is the single most effective cost reduction available to you, because your team knows which of the four 'Sharma Traders' records is real and an implementation consultant does not.
Be realistic about history. Migrating three years instead of fifteen removes a large amount of work, and older records stay searchable in the old system. Almost nobody queries a twelve-year-old transaction in an operational system.
And be honest about how distinctive your process really is. Most requests for customisation are habit rather than requirement, and each one costs at implementation and again at every upgrade.
The cheapest implementation is the one with the smallest first phase, not the lowest day rate.
ERP cost — questions we get asked
Why will nobody give a straight number?
Partly because the range is genuinely wide, and partly because whoever quotes first anchors the negotiation. A serious partner should still give you a rough band after a discovery conversation — and if they cannot after understanding your processes, that tells you something.
Is a fixed price better than time and materials?
Fixed price is safer for you when scope is genuinely well understood, which usually means after a discovery phase rather than before one. Fixed price agreed on a vague scope gets recovered through change requests, which is the worst of both.
Should we do discovery with the firm that will implement?
There is a real conflict — discovery that concludes 'you do not need this' costs them the project. Paying for discovery separately, or from someone not bidding on delivery, buys you a more honest answer. We do both and will tell you when we think you should get a second view.
The work this leads to
Moving from Tally to a real ERP
Most businesses do not need to leave Tally. They need to stop using it for the things it was never built for, and move those onto something else first.
Read itMigrationModernizing FoxPro, VB6 and Access systems
These systems usually encode two decades of business rules that exist nowhere else. The migration risk is not the code — it is losing the rules.
Read itOther guides
Custom software or an off-the-shelf ERP?
A packaged ERP is the right answer more often than software firms admit. Here is how to tell which side of the line you are on, before anyone quotes you.
ComparisonCloud or on-premise, for an Indian business
The cost comparison people run is the wrong one, because it compares a server against a server and ignores everything the server needs to keep working.
Still weighing it up?
Most of these questions are quicker to settle in a conversation than in an article — particularly the ones where the answer depends on your numbers.