Back to the archive

The encyclopedia · Software & IT · Technical decision · 2025

Zimmer Biomet's botched SAP rollout ended in a $172 million claim against Deloitte

A medical device giant paid Deloitte $94 million for a new SAP system that, once live, was so broken it sued for $172 million.

Zimmer Biomet · Deloitte · 2025-09-04

What happened

On 4 September 2025 Zimmer Biomet, a publicly traded maker of orthopaedic and surgical devices, sued Deloitte Consulting LLP in New York Supreme Court for at least $172 million over a failed SAP S/4HANA implementation. It was a fight between a manufacturer and a consultancy over an enterprise software project that went badly wrong at the company whose products end up inside patients.

Zimmer Biomet alleged Deloitte won the project by falsely assuring it had the skills, methodology, tools and accelerators to deliver the new system within the agreed time and budget and with minimal customisation. Instead, the case alleged, the Deloitte team assigned to the job was unskilled and inexperienced, and it delivered an overly customised system riddled with defects and functionality gaps.

The bill was large. Zimmer Biomet said it paid Deloitte about $94 million for the failed implementation, then had to spend tens of millions more remediating the flawed system and recovering from the disruption to its operations and supply chain after the flawed go-live. The claims were fraud, breach of contract, negligent misrepresentation and violation of New York's deceptive trade practices act.

The case is a reminder that a failed enterprise-migration is not just a cost overrun — it is a legal liability. A consultancy that sells a smooth rollout and delivers a broken system can be taken to court for the difference, and at a medical device company the operational chaos had a direct bearing on patient-facing production.

Why it happened

  • Zimmer Biomet trusted a vendor's promise of skill and a fixed budget for a system that needed deep customisation, so the mismatch did not surface until go-live
  • The implementing team lacked the experience the project needed, so defects were shipped to production rather than caught in build
  • There was no effective gate before go-live: the system went live broken, turning a software problem into prolonged operational and supply-chain disruption
  • The vendor's assurance pushed the customer to commit to a fixed price and deadline, so the failure could not be absorbed as ordinary overrun — it became a $172 million claim
What it cost$94 million paid to Deloitte, $172 million claimedcostly

The lesson

A fixed-price enterprise migration is only as safe as the go-live gate that stops a broken system from reaching production — test the customised build before you let it run the business.

Sources

spotted an error? The club wants to know.

Comments · 0

    Sign in to join the comments.

    More like this

    Somewhere, someone solved the problem this company failed at. 2nd Opinion →