Why most ERP projects in India go wrong

There is a pattern you see again and again with mid-size companies in India. Someone in leadership watches a vendor demo, gets excited about dashboards and automation, signs a contract and then spends the next eighteen months trying to force the software to match the way the company actually works. The problem is rarely the software itself. The problem is that nobody mapped the real workflows first.

Before you open a single vendor website, sit down with the people who do the daily work. Talk to the accounts team about how they handle GST returns. Talk to the warehouse staff about how goods move in and out. Talk to HR about leave tracking and payroll. Write down what actually happens, not what management thinks happens. That gap between the two is where most ERP projects fail.

According to a Gartner study on ERP implementation success factors, organisations that invest at least eight weeks in process mapping before vendor selection are significantly more likely to go live on time. That research holds true in Indian markets where regulatory complexity around GST, TDS and state-level labour laws adds another layer of configuration work.

Indian compliance is not optional and not simple

Map the Indian tax and reporting requirements that apply to your business with your finance team and advisers. Then test how each ERP supports those workflows, including invoicing, relevant GST statements and integrations where needed. A bundled feature list is not evidence that a particular business is compliant. Assess native modules and add-ons by their actual fit, maintenance and total cost.

Beyond GST, think about TDS deduction and filing, Professional Tax which varies by state, Provident Fund and ESI contributions and the Shops and Establishments Act registrations that differ between Maharashtra, Karnataka, Tamil Nadu and every other state. A system built for the American or European market will not handle these out of the box no matter what the sales team promises.

The Ministry of Corporate Affairs requires companies to file financial statements in XBRL format. Your ERP should either generate XBRL-compliant reports directly or export data in a format that your auditors can convert without re-keying numbers. Check this before you sign anything.

Cloud versus on-premise and what makes sense now

Five years ago, many Indian businesses preferred on-premise ERP because they worried about data leaving their servers. That concern has not disappeared but the practical reality has shifted. Cloud ERP providers now offer Indian data centre hosting through AWS Mumbai, Azure Pune and Google Cloud Mumbai regions. Your data stays in India and you avoid the capital expense of buying and maintaining your own servers.

Cloud also makes sense for companies with multiple locations. If you have a factory in Rajkot, a warehouse in Bhiwandi and an office in Gurgaon, a cloud ERP gives everyone the same real-time view without VPN headaches. The National Informatics Centre has published guidelines on cloud adoption for government and public sector organisations that provide a useful framework even for private businesses evaluating hosting decisions.

That said, there are situations where on-premise still wins. If your factory floor runs offline for hours at a time due to connectivity issues, if you process extremely sensitive defence or pharmaceutical data, or if your IT team already manages servers well, on-premise may be the better choice. Just make sure you budget for ongoing maintenance, backups and security patches.

What to look for in a vendor demo

Vendor demos are designed to impress you. The sales team will show you the fastest workflows, the prettiest dashboards and the features that look best in a boardroom. Your job is to ignore all of that and focus on three things. First, ask them to show your actual workflow. Bring a real purchase order, a real GST invoice and a real payroll scenario. Watch how the system handles them without shortcuts.

Second, ask about the implementation partner. In India most ERP implementations are done by third-party consultants, not the software company itself. The quality of the implementation partner matters more than the quality of the software. Ask for references from companies in your industry and your size range. Call those references and ask them what went wrong, not what went right.

Third, ask about the total cost. The licence fee is just the beginning. Add implementation consulting, data migration, training, annual maintenance and the inevitable customisation requests. Get all of this in writing. The India Brand Equity Foundation regularly publishes reports on the IT services landscape that can help you benchmark pricing.

Practical steps before you commit

  • Map every daily workflow across accounts, inventory, payroll and compliance before contacting vendors.
  • List your GST, TDS, PF and ESI requirements and confirm the ERP handles them natively.
  • Ask for a pilot with real company data, not a canned demo with sample transactions.
  • Check the implementation partner's track record with Indian companies of similar size.
  • Get the total three-year cost in writing including licence, implementation, training and support.
  • Confirm the system can generate XBRL-ready reports for MCA annual filings.

If you are evaluating ERP options and want a second opinion before committing, we are happy to review your requirements and give you an honest assessment. Share your current workflow pain points, compliance needs and rough budget through our enquiry page. We will tell you what we think without a sales pitch.

Sources & further reading

Sources checked 2 August 2026. Confirm current requirements for your specific activity with the responsible professionals.

Discuss your requirementTechnology services