Failed Projects, Contracts and Official Sources

Why ERP projects overrun, the contract terms that protect you, the data protection and audit trail rules to plan for, and the official sources to check.

Most ERP disappointments follow a small number of patterns: scope that was never written down, data migration left to the last week, customisation that breaks at each upgrade, users who were never trained, and contracts that make leaving expensive. These guides describe those patterns generically, without naming companies, and show how to avoid them.

Start with why ERP projects fail and how to avoid it, which links to every guide in this section. The others cover SaaS contract terms (exit, data export, SLA, auto-renewal), hidden costs, the Digital Personal Data Protection framework and CERT-In reporting, the Companies Act audit trail (edit log) requirement for accounting software, government support for MSME digitisation and a list of official sources.

This is general information, not legal or tax advice. For contracts of significant value, or questions on TDS, GST or data protection obligations, consult a chartered accountant, company secretary or lawyer, and check primary sources such as the e-Gazette, MeitY and CERT-In.

Failed Projects, Contracts and Official Sources

Guides in this topic