Story
IBM
EniEni Modernizes Workload Migration with IBM
Eni, an energy organization in Italy, uses IBM watsonx from IBM to support datacenter exit planning for migration squads.
Teams at Eni moved workload migration onto IBM after local tools started to collide.
“Eni is based in Italy and runs energy operations at a scale where workload migration cannot live in side channels.”
“Migration squads were reconciling competing copies of the same work, which slowed datacenter exit planning and hid who owned the next step.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Migration squads work from the same IBM watsonx record for workload migration |
| Capability | Workload migration can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for workload migration |
Story
Eni is based in Italy and runs energy operations at a scale where workload migration cannot live in side channels. Migration squads were reconciling competing copies of the same work, which slowed datacenter exit planning and hid who owned the next step.
The company runs datacenter exit planning on IBM, with IBM watsonx as the product migration squads actually open. IBM offers hybrid cloud, AI, and automation software, including watsonx, Red Hat OpenShift, and observability products for large enterprises. For Eni, that means migration squads can open one workflow, see workload migration, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for workload migration.
