A complete virtualization platform built from the hypervisor up, then used to move existing tenants off an aging NSX-v environment onto NSX-T without asking them to start over.
Delivered by ThirtyZero's founder in senior technical and compliance roles prior to founding the company. Client names and identifying details are withheld under confidentiality.
The client's virtualization platform was still running on VMware NSX-v, a network virtualization product VMware ended support for in January 2022, alongside an older release of vCloud Director. Every tenant on the platform depended on that stack staying online while a next-generation replacement got built underneath them.
There was no clean, single cutover available. The new platform had to be built in parallel, validated, and then used to move live tenants across one at a time, treating the rebuild as an upgrade rather than an excuse to take the service down.
Installed and configured the ESXi hypervisor layer, stood up vCenter for centralized management, and deployed a new vCloud Director instance to replace the aging release.
Deployed VMware NSX-T as the new network virtualization layer, running it alongside the existing NSX-v environment so tenants could be moved individually rather than all at once.
Moved existing customer workloads from NSX-v to NSX-T, and from the old vCloud Director release to the new one, tenant by tenant, using the new infrastructure as the landing zone.
VMware ended support for NSX-v in January 2022. Running tenants on an end-of-life network virtualization layer means no further security patches and no vendor support if something breaks. Migrating to NSX-T while the platform was still stable, rather than waiting for a forced deadline, kept the move on our own schedule instead of an emergency one.
Tenants were migrated individually onto the new platform rather than in a single cutover, which is the standard way to keep a multi-tenant migration controlled. Exact downtime windows depended on each tenant's workload and are not tracked here, since this is a scope description rather than a per-tenant report.
A ground-up platform build (hypervisor, vCenter, vCloud Director, NSX-T), a parallel run alongside the legacy NSX-v environment, and a phased migration plan per tenant. The scale and timeline depend on tenant count and how much custom networking each one has configured.
Yes. This work was delivered by ThirtyZero's founder in a senior infrastructure role prior to founding the company. Client details are withheld under confidentiality, and the engagement is described here to show the kind of platform rebuild and migration work we can scope and deliver.
Hardware, hypervisors, and vCenter stood up across two major metro markets to give a newly entered telecom operator the compute foundation for its own SDN-based infrastructure.
Read case studyLed the move of a client's entire on-premises virtualization footprint into Microsoft Azure, replacing physical infrastructure ownership with a managed cloud platform.
Read case studyTell us what you are working with and what is not working. We will give you a straight answer on scope, approach, and whether it is a fit.
