A Fortune 500 Enterprise had already absorbed one round of a vendor licensing increase on Tanzu TAS. Prices had climbed nearly 400%, and each year remaining on the platform cost an additional $12M. The organization knew about the change but had not made plans. Many teams had lived through the original migration to PCF years earlier and still remembered how difficult and unpredictable it had been. Teams were reluctant to move and had not prepared their applications, tooling, or processes for migration. The mission was to complete the migration before the next renewal, with a hard deadline: dev complete by Cyber 5.
The Engagement
I built a three-tier organizational model to drive the migration. The first was a steering group: leaders representing all aspects of the business who defined the end state, removed blockers, agreed on technical trade-offs, and ensured accurate messaging across the organization. The second was a concierge group: my most highly skilled engineers, who built the patterns needed to move applications, designed the developer experience, and handled network and data concerns. They were the technical experts who built, trained, led, and rapidly responded to questions and problems during migration. The third was the ambassador group: graduates from engineering teams who had successfully migrated their own applications and were willing to lead others. Their mission was to scale capability and knowledge within their own groups, so each team could move its own applications with concierge support when unknown patterns or technical debt became blockers.
Migration velocity was tracked through burn-down charts showing expected completion dates based on current commitment, velocity, team size, and number of applications. This was included in quarterly planning for visibility across the organization. I started with boilerplate examples, ran lunch-and-learns, and led multiple workshops and training sessions. Per-application migration time dropped from 8 hours to 20 minutes through iterative refinement.
The biggest challenge was organizational. As teams fell behind, some wanted to push the migration timeframe. The burn-down analysis constantly raised visibility of where each team stood and the realities that remained. Quarterly planning ensured teams prioritized correctly rather than deferring.
Results
- $12M per year in licensing savings by completing the migration off Tanzu TAS.
- 2,500+ applications migrated in 9 months. Industry standard for migrations at this scale is 18 to 24 months.
- Zero downtime through Cyber 5. The first holiday period in 8 years without needing to restart services to carry the load.
- Per-application migration time dropped from 8 hours to 20 minutes through iterative workflow refinement.
- Full capability transfer. Internal engineering teams owned the platform, the methodology, and the operational knowledge when the migration was complete.