What Tanzu to OpenShift migration economics actually look like in 2026.

The Tanzu to OpenShift conversation in 2026 splits into two postures the buyer almost never sees together. The seller's posture is that the migration is technically possible but economically prohibitive across any realistic timeline. The migration vendor's posture is that the migration is technically straightforward and economically favourable from year two. Neither posture is the buyer side reading. The numbers that matter sit between the two claims, and they have moved meaningfully across the last 18 months as Tanzu pricing has restructured and OpenShift's pricing has stabilised. This piece sets out what the migration economics actually look like in 2026, what the seller and the migration vendor each leave out, and where the buyer should price the optionality.

Three buyer side decisions are relevant here. The first is whether to migrate at all, against the current Tanzu renewal economics. The second is what the migration would cost if executed, in capital outlay and in operational disruption, against the deal value being protected. The third is what the optionality of migration is worth in a renewal negotiation even if the migration never happens. All three are different questions. The seller treats them as one. The buyer should not.

What the seller leaves out

The seller's economic case against migration leans on three figures. The migration capex, calculated against a worst case rewrite assumption. The operational disruption window, calculated against a sequential cluster migration with no parallel run. The retraining cost, calculated against the assumption that the entire platform engineering function needs to be retrained from scratch. All three figures are calculable. All three are systematically high because they assume the most expensive form of every variable.

The seller does not run the comparison against the realistic form of the migration. Most workloads on a typical Tanzu Application Platform deployment are already running in container form against a Kubernetes substrate. The migration to OpenShift, at the container layer, is mechanical rather than transformational. The capex falls when the buyer scopes the migration as a substrate replacement rather than a rewrite. The disruption window collapses when the buyer scopes a parallel run rather than a sequential cutover. The retraining cost shrinks when the buyer scopes role specific upskilling rather than wholesale function replacement.

What the migration vendor leaves out

The migration vendor's economic case for the migration leans on three figures of its own. The list rate gap between Tanzu and OpenShift. The operational efficiency gain from consolidating onto a single substrate. The escape from the Broadcom renewal escalator. All three figures are real. All three are systematically high in the migration vendor's framing because they assume the buyer captures the full theoretical benefit.

The list rate gap is meaningful but not as large as the migration vendor's slide suggests. Tanzu's actual closing rate in the buyer's region is not the list rate. The closing rate sits 30 to 50 percent below list, particularly inside a wider VCF commitment. The operational efficiency gain depends on substrate consolidation that takes 12 to 24 months to realise. The escape from the Broadcom escalator is real, but it transfers the buyer into the OpenShift escalator, which is lower but not absent. The migration vendor's economic case, run against realistic figures, is favourable but not as favourable as the slide.

"The seller's case overstates the cost of leaving. The migration vendor's case overstates the benefit of leaving. The buyer side reading sits between them, and the optionality is worth more than either side will admit."Renewals Lead, The Desk

The buyer side numbers

The Desk has scoped six Tanzu to OpenShift migrations in the last 14 months. None have closed at the seller's worst case scenario. None have closed at the migration vendor's best case scenario. The closing band, across the six engagements, sits in a defined range. Migration capex runs $850K to $2.4M depending on workload count and complexity. Operational disruption windows run 9 to 18 months from kickoff to full cutover, with a parallel run period of 4 to 9 months. Retraining cost runs $180K to $420K depending on the platform engineering function's existing Kubernetes posture.

The recurring savings against the prior Tanzu envelope, after migration, run 22 to 41 percent of the prior annual run rate. The variance comes from how aggressive the buyer was in negotiating the Tanzu price during the renewal motion that preceded the migration. Buyers who closed at the top of the Tanzu price band see the larger savings. Buyers who closed at the bottom see the smaller savings, because the Tanzu price they were paying was already close to the OpenShift price they will be paying.

The payback period

Payback periods across the six engagements ran from 16 months at the fastest to 34 months at the slowest. The median sat at 24 months. The variance correlates with the prior Tanzu negotiation outcome and with the operational efficiency gains the buyer was able to capture in the first 12 months after cutover. Buyers who scoped the migration tightly, on a parallel substrate consolidation rather than a full rewrite, hit the lower end of the payback range. Buyers who scoped broadly, with a rewrite of application code alongside the substrate change, hit the upper end.

The implication for the renewal motion is direct. A buyer who is preparing to negotiate a Tanzu renewal in 2026 has, on the buyer side numbers, a defensible 24 month payback alternative pathway. The seller's account team knows this whether the buyer raises it or not. The buyer who raises it explicitly carries it into the renewal as an exit optionality. The buyer who does not raise it carries it as an unseen lever. The optionality is worth what the buyer can credibly demonstrate, not what the buyer claims.

What the optionality is worth in a renewal

Across the Tanzu renewals where the buyer brought a documented migration alternative to the table, the seller's quote moved 11 to 23 percent below the seller's prior best offer. The movement was not because the buyer threatened to migrate. The movement was because the buyer demonstrated that the seller's worst case figures could be substantiated against a realistic alternative. The seller's account team carries the alternative back into the internal pricing model. The pricing model adjusts. The next quote reflects the adjustment.

A buyer who walks into the renewal without the documented alternative carries no anchor against the seller's framing. The seller's framing wins by default. The yield from documenting the alternative does not require the buyer to execute the migration. It requires the buyer to have done the work of pricing the alternative, with sufficient detail that the seller's account team has to engage the numbers rather than dismissing them.

When the migration actually makes sense

Across the six engagements, two of the buyers executed the full migration after the renewal motion. Four of the buyers signed a Tanzu renewal at the adjusted price and kept the migration as a documented option for the next cycle. Both outcomes were defensible. The buyers who migrated had structural reasons beyond the price, including a wider substrate consolidation programme and a separate platform engineering function reorganisation. The buyers who renewed had operational reasons to remain, including a complex set of in flight workload modernisation projects on the Tanzu platform that the migration would have disrupted.

The migration is not the right answer in every case. The optionality is the right answer in every case. The optionality, properly documented and brought to the renewal motion, produces yield regardless of whether the migration executes.

What we have seen on live deals

A financial services group brought a Tanzu Application Platform renewal to the Desk with a documented OpenShift migration alternative the buyer had scoped internally over the prior 18 months. The seller's opening quote ran $7.4M annually. The Desk presented the alternative as a 22 month payback against a $1.6M migration capex. The seller's account team engaged the numbers. The renewal closed at $5.6M annually, a 24 percent reduction. The buyer did not migrate. The optionality was the yield.

A retail group ran the other shape. The buyer's executive sponsor had concluded the migration was the right answer regardless of the renewal outcome. The Desk scoped the migration at $2.1M capex with a 28 month payback. The buyer executed the migration starting in q3 2025 and completed cutover in q1 2026. The Tanzu envelope was wound down. The OpenShift envelope is in year one of its own renewal cycle. The total cost of the platform across the buyer's three year horizon, including migration capex, comes in 31 percent below what a renewed Tanzu envelope at the seller's opening quote would have produced.

The takeaway

• The seller's case against the migration overstates the cost of leaving. The migration vendor's case for the migration overstates the benefit of leaving. The buyer side reading sits between them, with a 22 to 41 percent recurring saving against a 16 to 34 month payback.
• Documenting the migration alternative produces 11 to 23 percent yield in the renewal motion, whether the buyer executes the migration or not. The optionality is the yield. The execution is a separate decision.
• Two of six recent engagements executed the migration. Four kept it as documented optionality. Both outcomes were defensible. The migration is not the answer in every case. The optionality is the answer in every case.