Migrating a VMware Cloud Director to a NaoShift Portal
NaoShift reads the structure of a VMware Cloud Director — organizations, organization VDCs, policies, NSX-T edges, vApps and affinity rules — to rebuild each tenant in a NaoShift Portal VDC on Proxmox VE or XCP-ng. Read-only, in early access, for IaaS hosting providers.
An IaaS hosting provider living on VMware Cloud Director carries, in a single product, the technical identity of every tenant: the organization, its VDCs, its networks and their NSX-T gateways, its vApps, its affinity rules and placement policies. Moving all of this elsewhere is not a virtual-machine migration — it is a migration of the structure that holds them together. Since 18 November 2026, NaoShift reads this structure and proposes to rebuild it, tenant by tenant, into a NaoShift Portal VDC served by Proxmox VE or XCP-ng. The connector is in early access: it is written from the public Cloud Director 10.4 to 10.6 API documentation, proven in the lab, and will be put in service with the first hosting providers who ask for it.
Why a dedicated connector for Cloud Director?
The virtual machines of a Cloud Director already run on a vCenter. On the NaoShift side, a vCenter connects as a source: the machines are counted, analysed and operated, exactly like for a single-tenant customer. But a hosting provider needs another layer — who owns what, who has access to what, and how networks and rules stay consistent with one another.
The VMware Cloud Director connector adds that layer. It imports no machine: it lays the tenant map over the machines of the vCenter you already collect. A Cloud Director machine is matched to its vCenter machine by the vCenter's instance UUID and its reference (vm-123) — never by name. Your inventory stays exact: one machine is counted once.
What NaoShift reads inside Cloud Director
Collection is read-only: NaoShift opens a provider session (user@System) with a role that only lets it view, reads, and always closes the session. Nothing is written to Cloud Director.
NaoShift reads at every collection:
- the organizations, enabled or not, and their organization VDCs with their allocation model, their CPU, memory and storage limits, the number of vApps and virtual machines;
- the policies for placement, sizing and storage published in each VDC, with the vCenter VM groups they name;
- the networks of a VDC (routed, isolated, direct), with their gateway, prefix, static pools, DNS, DHCP pools, and what backs them (port group, NSX segment);
- the NSX-T edge gateways, with their public addresses, NAT rules, firewall rules and the addresses of their IP sets, and the number of IPsec tunnels, static routes and load-balanced services;
- the vApps with their own networks and the start order of their machines;
- the virtual machines with their operating system, sizing, storage, placement and sizing policies, and their network adapters;
- the affinity rules, mandatory or soft, "together" or "apart".
Never read: users and roles, passwords and guest customization, NAT and firewall rule names and descriptions, vApp owners, free-text descriptions.
Rebuilding a Portal VDC from a Cloud Director VDC
In the provider console, a tenant's New virtual data center wizard can start from a Cloud Director VDC. NaoShift compares with the chosen site (Proxmox VE or XCP-ng), fills the form with real values — networks with the same subnets, the VLAN of a port group kept when it is free, quotas, tiers — and lists the differences before you save.
Every difference carries a verdict: recreated by NaoShift (when the migration arrives, for example for affinity rules on Proxmox or to keep a machine's address), matched to a Portal equivalent (storage class, placement policy, size template), your choice (a vCPU quota expressed in MHz in Cloud Director, a VLAN that cannot be kept, a policy with no match), runbook step (done by hand during the migration, such as the gateway of a routed network or IOPS limits of a policy), or not carried over (edge services, networks private to a vApp, reservations and shares of a sizing policy).
Saving the VDC opens the tenant's migration case. The waves of the case migrate to the target of the VDC's site. On arrival, each machine enters the VDC: addresses stay reserved in the IPAM, the placement policy is set on the card, and the runbook steps that can run (high availability, affinity rules on Proxmox, start order) are played.
And the edge services — NAT, firewall, IPsec?
NaoShift Portal has no NSX edge gateway. NAT, firewall, VPN and load balancing are taken over by your network team. Before the migration, NaoShift exports an edge handover sheet: one line per rule, with the real addresses, ready to be read by the person who will set these services up elsewhere.
For whom, and under what terms?
The connector is offered to hosting providers and MSPs (MSP mode enabled for the company). It is in early access: it runs in the lab, and will be proven on the first Cloud Director instances of real customers before opening more broadly.
As with every NaoShift connector, collection is read-only by default. Any write — during a migration or a handover — is enabled target by target, with a dedicated account, and traced before execution.
FAQ
Do I need my vCenter connected to NaoShift already?
Yes. Cloud Director runs on a vCenter; NaoShift does not count machines twice. The vCenter attached to your Cloud Director must be collected by NaoShift — through the outbound agent, like any vCenter.
Which Cloud Director versions are supported?
Cloud Director 10.4 to 10.6. NaoShift negotiates the API version it reads (39.0 preferred, falls back to 37.0) and avoids any call specific to a newer version.
Does NaoShift also migrate an NSX-V VDC?
NaoShift sees that an NSX-V edge gateway exists but does not read its services: from Cloud Director 10.5 onwards, only NSX-T is supported by Cloud Director. If your platform still has NSX-V gateways, plan to hand their services over to your network team manually.
Can I migrate to both Proxmox VE and XCP-ng from the same console?
Yes. NaoShift Portal is available on Proxmox VE and, since October 2026, on XCP-ng through Xen Orchestra. A hosting provider can spread tenants across several sites and platforms from the same console, with the same actions.
Going further
For the big picture: the NaoShift Portal page and the integrations catalog. To run the first on-boarding of a Cloud Director together: get in touch, or start for free.