Every good nested lab eventually succeeds itself out of a job: the services get used, the lessons get applied, and the training wheels start to chafe. This page covers the graduation — moving your Proxmox world to bare metal — and the ESXi licensing reality that decides the timing for many labs.
A nested lab has a natural life story. It begins as a safe classroom, becomes a rehearsal stage, and then — if it taught you well — its containers and VMs start being services real people use. At that point the two honest limits of nesting, performance and vendor support, stop being footnotes and start being risks. The good news: leaving the nest is a planned migration, not a rescue. Proxmox's own backup format carries your guests to bare metal intact. And hanging over the whole decision is the ESXi licensing question, which deserves a straight answer.
Any one of these is information. Two or more is a decision.
Proxmox's built-in backup (vzdump) is the migration vehicle, and it treats the move kindly: a backup archive contains the guest's disks and configuration, for VMs and containers alike, and restores onto any Proxmox host — nested or bare metal, same version family or newer.
Sometimes the exit is sideways: a guest born in nested Proxmox needs to live on ESXi itself. Proxmox disks (qcow2 or raw) convert to VMware's format with the standard image tool — qemu-img convert can write a vmdk — after which you create a VM shell in ESXi and attach the converted disk. Be honest about the friction: drivers differ (VirtIO devices need VMware equivalents), network identity changes, and Windows guests may need activation attention after the hardware upheaval. It works, it is simply more manual than the Proxmox-to-Proxmox path, which is one more argument for graduating within the platform you learned.
Many nested labs exist because of a licensing fact, so here it is without false precision: Broadcom discontinued the free edition of ESXi (the old free vSphere Hypervisor) when it restructured VMware licensing, and ESXi is now obtained through Broadcom's subscription and evaluation channels. Terms, bundles and evaluation offers have changed more than once since and may change again — anyone's screenshot of last year's portal is not a source. Before planning a lab around an ESXi licence, check Broadcom's current terms for your situation. The strategic point survives every change, though: Proxmox on bare metal carries no licence question at all, which is why "graduate the nest to bare-metal Proxmox" is the exit most labs actually take.
Graduation is not demolition. Once services live on bare metal, the nested Proxmox on your ESXi host returns to its original and best job: scratch space. It is where you trial the next Proxmox version, restore a backup just to inspect it, break a cluster on purpose, or hand a student a hypervisor they cannot hurt anything with. Labs are not failed production systems — they are the reason production systems fail less. Keep yours.
Watch the video to build the nest properly first — graduation only makes sense for a lab that was set up right.
▶️ Watch Full VideoThat is the tempting shortcut and the wrong one. The virtual hardware Proxmox was installed against — disk controller, network adapter, firmware — differs from any real machine, so a transplanted disk typically boots into missing devices and wrong network names. The clean route is a fresh Proxmox install on the hardware, then restoring your guests from vzdump backups, which carries configuration and disks without carrying the virtual hardware assumptions.
Yes. The built-in backup system archives both KVM virtual machines and LXC containers, each with its configuration, into a single restore-ready file per guest. Restoring a container onto the new bare-metal host recreates it with its settings and data. As always, the archive only counts once you have test-restored at least one — do that before the old lab goes anywhere.
Proxmox VE is free to download and use, including commercially; the optional paid subscription buys vendor support and access to the enterprise update repository, and many production users buy it for exactly that. There is no licence key, no feature tier locked behind payment for the core platform. That is the licensing simplicity that makes it the natural graduation target for a nested lab.