The short answer: "migrating from Pivotal Cloud Foundry" in 2026 usually means a licensing migration, not an application rewrite. Legacy PCF/Tanzu SKUs were retired on 6 May 2024, and core-based TAS customers must move to the Application Instance metric at renewal. Model both metrics before you negotiate.
From Pivotal to Tanzu to Broadcom
Pivotal Cloud Foundry (PCF) became VMware Tanzu Application Service (TAS) after VMware acquired Pivotal, and under Broadcom that same runtime is now branded Tanzu Platform for Cloud Foundry. The Cloud Foundry runtime your applications run on is still supported — but the commercial wrapper around it has changed completely. Every legacy Tanzu and Pivotal SKU was retired as of 6 May 2024, rolling TAS, Tanzu Kubernetes Grid, and Tanzu Mission Control into the consolidated Platform bundle. So in 2026, "migrating from Pivotal Cloud Foundry" is, for most enterprises, a licensing and contract migration first and an engineering project second. For the wider Broadcom context see our Tanzu licensing and Kubernetes guide and the complete VMware licensing guide.
The Per-Core to Application Instance Switch
The change that hits PCF estates hardest is the metric switch. Customers on the legacy core-based TAS/PCF SKU must migrate to the Application Instance (AI) based SKU at their next renewal; those already on the Application Instance model are unaffected. This is not a cosmetic relabel — it changes what you pay for. A core-based estate running few, dense application instances may get cheaper; one running many small instances may get sharply more expensive.
| Metric | You pay for | Who it favours |
|---|---|---|
| Legacy per-core (retiring) | Physical/vCPU cores under the platform | Many small app instances on few cores |
| Application Instance (AI) | Running application instances | Fewer, denser, well-consolidated instances |
The mandatory conversion is exactly why you model both metrics against your real estate before the renewal conversation — the same discipline we apply to Tanzu Application Platform pricing and the broader Tanzu licensing changes after the Broadcom acquisition.
Your Three Migration Options
Every PCF estate facing renewal has three realistic paths, and the right one depends on your application portfolio and in-house skills.
Option 1 — Stay and defend the renewal. Remain on Tanzu Platform for Cloud Foundry, accept the move to the Application Instance SKU, and negotiate a defended renewal with a written support runway. Lowest disruption; you keep the Cloud Foundry developer experience your teams already know.
Option 2 — Migrate applications to Kubernetes. Move workloads onto Kubernetes via Tanzu Application Platform or another distribution. This removes the Cloud Foundry abstraction and the per-instance metric, but adds real engineering effort — and lands you in a different cost model we compare in Tanzu vs OpenShift vs EKS cost.
Option 3 — Leave entirely. Move to an alternative Cloud Foundry provider or a different platform. This is the strongest negotiating backstop and the largest project; it is only credible if you genuinely scope it.
What the Move Actually Costs
The PCF developer experience was built to make the platform "just work", which is why so many estates stayed put — and why Broadcom's renewal pricing has bite. Following the acquisition, many PCF/Tanzu customers have seen significant price increases and changed support terms, with opening Tanzu quotes commonly landing at 2x–5x the prior cost. Against that, a Kubernetes migration carries its own bill: re-platforming effort, new tooling (registry, CI/CD, observability), and the Kubernetes skills to operate it. The honest comparison is three-year total cost of ownership across all three options, including engineering time — not a single renewal quote against a single migration estimate.
Negotiating the Renewal
Treat the forced SKU migration as leverage, not a foregone conclusion. The levers that work: get the support runway for Tanzu Platform for Cloud Foundry in writing so "stay" remains a real option; scope Application Instances to genuine production density rather than accepting a generous default count; keep a credible Kubernetes-migration or exit alternative visibly in play; and commit to a multi-year term only in exchange for a locked price and a documented metric conversion. In our engagements, Broadcom's 2x–5x opening Tanzu quotes typically settle at 1.3x–2x once these levers are deployed. The detailed counter-tactics are in the VMware Broadcom Survival Guide and the Broadcom VMware negotiation playbook. To pressure-test a live PCF renewal quote, request a confidential briefing or start at the VMware/Broadcom vendor hub.