VMware defends ending downloads of SDK that helps VM backups– or migrations to rivals

VMware ended public downloads of its Virtual Disk Development Kit (VDDK), restricting access to select Technology Alliance Partners for its licensed backup-and-recovery use case. The SDK had been widely used by Nutanix, Red Hat, CloudStack integrators and migration consultancies to move virtual machines from VMware environments to competing platforms. The move may disrupt migration projects already underway and reinforces concerns that Broadcom-era licensing changes are encouraging customers and channel partners to reduce VMware exposure, although service providers have workarounds and VDDK is only one component of a full migration.

Analysis

This is marginally negative for AVGO because restricting interoperability is more likely to raise customer switching intent than preserve VMware revenue. Migration tooling friction can delay a project by weeks, but it rarely changes the board-level cost/lock-in decision that follows a licensing reset; instead, it shifts spend toward systems integrators, conversion tooling, and parallel-run infrastructure. The relevant KPI is not near-term VMware renewal retention, but whether larger accounts shorten contract duration, reduce committed cores, or explicitly fund multi-hypervisor architectures at renewal.

NTNX faces a mixed near-term setup: projects dependent on streamlined conversion may slip, delaying license recognition and services attach over the next 1-3 months. Over 6-18 months, however, higher perceived VMware switching costs strengthen Nutanix's value proposition as a lower-risk operating alternative, especially where customers choose phased modernization rather than a direct lift-and-shift. Red Hat/IBM and cloud platforms are likely secondary beneficiaries because a delayed migration often becomes an opportunity to re-platform onto KVM, OpenShift, or cloud-native infrastructure rather than replicate legacy VMware architecture.

The contrarian view is that this action is too small to materially alter AVGO's financial trajectory by itself: data, network dependencies, security controls, and application certification—not disk conversion—drive the majority of migration cost. A meaningful bearish AVGO signal would require corroboration in renewal-cycle evidence: rising churn, lower remaining-performance-obligation expectations, or material incremental concessions in partner/channel commentary. Conversely, strong VMware bookings or stable renewal metrics through the next two reporting cycles would show that migration friction is creating delay rather than durable competitive loss.

Key Decisions for Investors

• Maintain AVGO as a watch-short rather than initiating solely on this development; reassess after the next earnings call for VMware renewal duration, net retention, and any change in software-segment guidance. A short becomes actionable only if management acknowledges elevated concessions or contract downsizing; absent that, the event lacks sufficient earnings sensitivity.
• Accumulate NTNX on migration-related execution weakness over the next 1-3 months, rather than chase an immediate reaction. Target a 6-18 month long thesis based on conversion pipeline growth and expanding subscription/ARR guidance; invalidate if delayed migrations do not translate into pipeline conversion or if competitive discounting materially pressures billings growth.
• Use a relative-value expression—long NTNX versus short AVGO—in a modest sizing only if VMware renewal commentary deteriorates while Nutanix reports sustained pipeline acceleration. The pair reduces broad infrastructure-software beta; close if AVGO demonstrates stable VMware retention and NTNX misses billings or ARR expectations.
• Monitor RXT for a services-led second-order benefit rather than treat it as a clean beneficiary: migration demand can lift professional-services utilization, but project delays and customer budget constraints can defer revenue. Require evidence of higher VMware-exit bookings and utilization before establishing exposure.