Avoiding costly ERP and cloud systems implementation failures: A perspective from the deal room
ERP (enterprise resource planning) and cloud implementations often fail—not due to tech flaws, but because of rushed decisions and poorly defined contracts. In his article on CIO.com, Sean Christy highlights how critical missteps often happen before the project begins. A key issue is the “timing imperative”—the pressure to move fast. This often leads companies to skip due diligence and sign multi-year contracts with vague commitments and limited exit options. One major trap: loosely written Statements of Work (SOWs). Phrases like “assist with data migration” sound supportive but typically place full responsibility on the client. Add in misleading “fixed-fee” models, and costs can quickly spiral. Christy stresses the importance of stakeholder alignment. When legal, IT, and business units aren’t on the same page, contracts fail to reflect real operational needs.
To avoid these failures:
- Fully vet solutions before signing.
- Keep vendor options open until terms are locked in.
- Push for clear, specific SOWs.
- Involve executive sponsors early.
- Resist pressure to rush the deal.
ERP and cloud projects rarely fail at go-live—they fail in the negotiation phase. Preparation and clarity are your best safeguards.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
