Log entry Nº 305 · the stack watch

Bearing SW 225° · October 20, 2026 · 3 min read

Customer Data & CDPSW 225°Watch log

HP Shifts Customer Data Platform to Databricks, Targets 40% Cost Cut

HP has migrated its customer data platform to Databricks and targets a 40% cost reduction — but the baseline and scope behind the figure remain undisclosed.

By James Calloway3 min read565 words

HP Moves Customer Data Platform Into Databricks, Eyes 40% Lower Costs - HPCwire
Fix Nº 305HP Moves Customer Data Platform Into Databricks, Eyes 40% Lower Costs - HPCwire — Tumisu / pixabay

HP has moved its customer data platform onto Databricks and expects the migration to cut related costs by 40%, according to a report from HPCwire. That's the headline number, and it's a big one — but, as always, the figure deserves a closer look before anyone copies the playbook.

The company has not, at least in what has been disclosed so far, broken down how it arrived at the 40% estimate. Practitioners will want to know the baseline. Forty percent cheaper than what — an on-premises warehouse, a competing cloud platform, a legacy CDP contract? Without that baseline, the number is a claim, not a benchmark.

What does the move actually involve?

HP's customer data platform now runs on Databricks. That means the lakehouse vendor hosts the data layer that powers HP's customer-facing analytics, personalization and downstream marketing operations. The shift matters because it signals where large enterprises are taking their customer data stacks: away from siloed CDP appliances and toward open lakehouse architectures where compute and storage scale independently.

For marketing technology teams, the pattern is familiar. Raw customer data lands in open table formats. Teams query it with SQL, Python or whatever engine they prefer. Downstream activation tools — campaign platforms, segmentation engines, journey orchestration — plug in from there.

What is HP promising?

The claim is straightforward: 40% lower costs. HPCwire reports the figure as a target HP has set for the migration, and the framing matters. "Eyes 40% lower costs" is not the same as "has achieved 40% lower costs." Companies routinely announce savings targets alongside platform migrations; verified, audited post-migration numbers appear far less often.

What HP has not said, based on the available reporting:

  • Which workloads move to Databricks and which stay put
  • Timeline for the migration's completion, or whether it is already finished
  • Any pricing or contract terms with Databricks
  • Whether the 40% covers total cost of ownership or a narrower cost line

Each of those gaps is a caveat. Each one shapes whether the 40% is repeatable for another company or unique to HP's starting point.

Why should martech teams care?

Customer data platforms are under real cost pressure. Licensing fees for traditional CDPs have climbed, and data volumes keep growing. When a company of HP's scale — a global hardware and personal-systems business with customer data spanning consumer and commercial lines — moves its CDP layer to a lakehouse, vendors in the CDP market should take note.

Databricks, for its part, has been pushing hard into this territory. The company positions its platform as the foundation for customer data workloads that once lived in dedicated CDPs, with the pitch that open architecture beats proprietary lock-in on both cost and flexibility. HP's migration gives that pitch a marquee logo.

The skeptic's bottom line

A 40% cost reduction would be a strong result. But announced targets and realized savings are different animals, and we don't yet have the fine print: baselines, timelines, scope. Watch for HP to publish actuals. Until then, treat this as a directional signal about lakehouse adoption in customer data — not a certified case study.

If your own CDP renewal is on the horizon, the lesson isn't "move to Databricks." It's that large buyers are now pricing customer data infrastructure like infrastructure, not like marketing software. That shift changes every negotiation at the table.

Plot points

  1. HP has moved its customer data platform onto Databricks, HPCwire reports.
  2. HP expects the migration to deliver 40% lower costs.
  3. The 40% figure is a target; HP has not disclosed the cost baseline or timeline.
  4. The migration signals large enterprises shifting customer data stacks toward lakehouse architectures.

via Google News: customer data platform (Source)

Filed under

  • hp
  • databricks
  • customer-data-platform
  • lakehouse
  • cloud-migration
Share this article:

More from James Calloway

James Calloway

Show full bio

Correspondent covering people, launches and day-to-day practice in marketing technology at Martech Beacon.

30 articles

Neighbouring fixes

‹ Previous articleNext article ›