MillerCoors v. HCL: When ERP Consolidation Fails

ERP consolidations are among the highest-stakes projects an enterprise runs. They touch payroll, procurement, inventory, and finance at once, they’re expensive, and they’re famously hard to deliver. MillerCoors v. HCL is a well-documented public example of one going to court — and a clear illustration of why these programs make such combustible big-bang bets.

What follows is based on the complaint and countersuit as reported and on contemporaneous coverage. It describes a reported legal matter; it is not a finding of fault and not legal advice. The allegations belonged to the parties, each disputed the other’s account, and the case ended in a private settlement with no public liability judgment.

What the project was supposed to be

By the mid-2010s MillerCoors was reportedly running a fragmented ERP estate — multiple separate SAP instances — and wanted to consolidate onto a single, unified SAP platform, including supply-chain and warehouse-management functionality. In December 2014 it awarded the work to HCL Technologies; reporting put the contract at roughly $53 million, with about $9.6 million added later. The goal was the classic consolidation promise: one system, one source of truth, lower cost to run.

What reportedly went wrong

In its March 2017 complaint, filed in the U.S. District Court for the Northern District of Illinois, MillerCoors alleged that the program failed on several fronts:

• Missed deadlines. HCL was alleged to have repeatedly failed to meet project milestones.
• Defective deliverables. The complaint claimed the software delivered was not free of defects as required.
• Inadequate staffing. MillerCoors alleged HCL did not provide staff with the requisite skills to do the work.
• Gross negligence. The conduct was framed in those terms, alongside breach of contract.

HCL told a very different story. In a June 2017 countersuit, it disputed MillerCoors’s account and argued — as reported — that it was being made a scapegoat for the customer’s own leadership decisions and project governance. As in most of these matters, responsibility was contested on both sides, and no court publicly resolved it.

The numbers, stated conservatively

MillerCoors sought damages it described as “in excess of $100,000,000.” That was its claim, not an awarded sum. The underlying contract was reported at roughly $53 million (plus about $9.6 million added later), which is the more solid figure. The case ultimately settled; the public record does not detail the terms beyond noting that each party would bear its own costs. We won’t characterize the settlement beyond that, because nothing more was publicly confirmed.

Why ERP consolidations are combustible

The structural risk in an ERP consolidation is that it changes the system of record for many functions at the same time. When the new platform goes live, payroll, procurement, warehousing, and finance all depend on it at once — so a defect doesn’t degrade one feature, it can stall operations across the business. That concentration is what turns a delayed project into an existential one, and it’s why these programs so often end up in disputes about whether the delivered system was fit for purpose.

The temptation is to treat consolidation as inherently all-or-nothing: you can’t half-consolidate, the thinking goes, so you must cut over the whole thing. That framing is the trap. We unpack it in big-bang vs. incremental and why software rewrites fail.

How we’d de-risk a consolidation like this

Even an ERP consolidation can be sequenced. We work through it slice by slice — a function, a plant, a process area — behind a strangler facade, so the existing systems keep running production while the consolidated platform takes over one function at a time. Before any slice carries live traffic, we prove it reconciles record-for-record against the system it replaces: same stock figures, same pay calculations, same financial postings. Traffic shifts only on green, and rollback stays a flag away. The “single source of truth” arrives incrementally, validated at each step, rather than as one switch thrown across the whole business.

For an SAP estate specifically, the same logic drives how we approach an SAP ECC to S/4HANA migration. And where the question is what exposure a stalled or aging ERP already carries, a legacy system liability assessment maps it.

Not a verdict on either party

We’re not assigning blame in this matter — there was no public finding against either party, and HCL is a major integrator that delivers large programs successfully. Nor were we involved in any way; we weren’t. The case is valuable purely as a public, well-documented example of how big-bang ERP consolidation concentrates risk. To scope a consolidation that retires that risk slice by slice, book a discovery call at /meet or reach the team at sales@modernlift.ai.

This guide summarizes a reported legal matter for illustration. It is not legal advice, and any judgment about the parties’ conduct belongs to the courts and counsel.