Haleon Chooses SAP Solutions to Replace Legacy

Haleon, the global consumer health company behind brands including Sensodyne, Advil and Panadol, has chosen SAP Business Suite to replace its legacy SAP ERP Central Component environment and build what both companies are calling an AI-ready enterprise foundation. The deal is a prominent ECC-to-cloud migration in the consumer health sector and sets a template for how large multinationals can tie digital transformation directly to commercial growth targets.

Impact for Technology Leaders

The Haleon decision illustrates a shift in how cloud ERP projects are being scoped and sold. Rather than framing migration as a technology refresh, Haleon and SAP are explicitly connecting the SAP Business Suite investment to the company’s “Win as One” commercial growth strategy, giving technology leaders a clearer line of business justification to bring to the board.

Day to day, the transition from ECC to SAP Cloud ERP means finance, supply chain, HR and sales teams that currently navigate fragmented workflows will converge on one connected system with real-time data. SAP’s Peter Maier framed it plainly: “AI outcomes depend on connected processes and trusted data.” For operations leaders, that means fewer manual handoffs across planning and procurement cycles, faster exception resolution when supply signals shift, and dashboards that reflect the same version of the truth regardless of market or function.

Haleon is also deploying SAP Business Data Cloud to harmonize SAP and third-party data in a single governed source of truth — a pattern SAP calls central to enabling agentic AI, where software agents can identify issues and recommend actions without waiting for human-driven queries. As SAP CEO Christian Klein has described it, AI has to operate in the system of record where work actually happens so that outcomes are auditable and secure. For teams still on ECC, the message is direct: the path to production AI runs through a clean, cloud-native data foundation.

How to Evaluate and Execute a Move Like Haleon’s

For SAP customers benchmarking against Haleon’s approach, several evaluation criteria stand out. Depth of AI readiness matters more than feature parity alone; organizations should assess whether a proposed cloud ERP target will support embedded Joule agents, multi-agent orchestration and no-copy data sharing with existing analytics platforms before committing to a migration path. SAP’s Business Data Cloud now supports zero-copy connectivity with Databricks and has BigQuery support planned for the first half of 2026, widening the ecosystem in which harmonized SAP data can power AI use cases.

The most common challenge in ECC migrations of this scale is preserving institutional process knowledge while eliminating customizations that block continuous updates. Best practices include a fit-to-standard assessment early in the program, phased cutover by region or function rather than a single global go-live, and leveraging SAP’s clean-core extension model on SAP Business Technology Platform to handle edge-case requirements without modifying the core. Haleon’s phased approach, with the ECC transition beginning later in 2026, reflects this discipline and gives its newly appointed Chief Transformation Officer time to align process redesign, operating model changes and technology delivery in parallel.

What This Means for SAPinsiders

AI readiness now drives ERP migration business cases. Haleon’s decision signals that organizations moving from ECC to SAP Cloud ERP are no longer justifying migration on cost or support timelines alone. They are anchoring it to agentic AI and Business Data Cloud capabilities, setting a new standard for how GSIs and enterprise architects should frame transformation investments.

SAP Business Data Cloud becomes a strategic differentiator. By deploying Business Data Cloud alongside Cloud ERP to create a governed single source of truth for SAP and third-party data, Haleon reinforces that data harmonization is a prerequisite for production AI. This pushes SAP vendors and partners to treat BDC as a core platform component rather than an optional add-on.

Clean-core discipline will define program success at scale. As global consumer companies like Haleon restructure operating models while simultaneously migrating ERP, transformation leaders must enforce fit-to-standard design and BTP-based extensions from the start, creating pressure on GSIs to build delivery methodologies that protect core integrity across multi-market, multi-wave rollouts.