Why enterprises can't just ditch SAP and move to a competitor!

I've sat in enough boardrooms and discovery calls where a procurement lead or a CFO slides across a competitor brochure and asks, "Why can't we just move off SAP?" It's a fair question on the surface. But every time I hear it, I think about organisations like Sellafield - and the answer becomes obvious very quickly.

Sellafield Limited, which runs Britain's largest and most consequential nuclear site, recently awarded SAP a direct contract, without competition, to begin migrating off its legacy ECC platform onto S/4HANA. No tender. No shortlist. A decision made with full transparency about why any other path was simply not viable.

The deal itself signals the scale of what's at stake. The opening award: just the first of four planned contracts in this programme, came in at £33 million, covering HR SaaS licensing as a deliberate, lower-risk beachhead before the heavier platform work begins. Running in parallel, Sellafield is procuring a separate tech services arrangement covering infrastructure support for over 118 legacy applications, a deal reported to be worth around £90 million. These are not isolated line items, they are the opening chapters of a transformation programme that will run well into the decade.

When you see a government-owned organisation commit at this level without a competitive process, it tells you everything about how deeply embedded the incumbent platform is.

And the core of that embeddedness? Data.

Their SAP environment doesn't just hold financial records. It holds decades of integrated operational data across finance, procurement, warehousing, HR, and critically - enterprise asset management. At a nuclear decommissioning site, asset data isn't a spreadsheet of machinery. It is part of the regulatory and safety infrastructure. Every maintenance record, every inspection log, every compliance entry has a lineage that cannot be broken or approximated during a migration. It must arrive on the other side complete, traceable, and auditable.

Sellafield's own documentation made the stakes explicit: moving to any alternative ERP would require every single interface to be re-architected, re-engineered, and tested for compliance from scratch. The data migration alone, before a single business process is redesigned, would be a multi-year programme with no guarantee of success before existing support expired.

This is what I call data gravity. The longer an organisation runs SAP, the more its data structures, integrations, and compliance obligations become inseparable from the platform itself. Lifting that data out and landing it cleanly in a competing system isn't a migration - it's a reconstruction.

---

The smarter move, as Sellafield concluded, is to migrate within the family. Preserve the investment. Protect the data lineage. And use the transformation to modernise, not to gamble.

---

That's not vendor loyalty. That's risk management and good data thinking.