@olivierlambert and honestly, that's more than fair because I was paying VMUG $500 a year for the privilege of maintaining skills on their platform. I've never looked back and other than load balancing being locked behind the highest tier, I don't feel the pricing needs too much tweaking to be attractive to SMBs, but working in that space a lot I know pennies are dollars so I'm sure it will help with market penetration. I'd much rather suggest SMBs deploy XCP-NG and XOA than get tangled up in the VMWare/Broadcom madness.

@olivierlambert no suspicion here of an agenda, just want to make sure that I have reasonable expectations. I’m relatively new to XCP-NG and XO, just migrated my lab from VMWare earlier this year and didn’t know building from sources was an option. I just followed Tom’s tutorial and deployed XOA.

FWIW I think the pricing is very reasonable, especially being flat rate, for businesses.

@Danp Perfect, thanks.

I searched for existing threads but didn't find anything - surprised this hasn't been talked about. Maybe my search-fu sucks or I used the wrong keywords.

Title says it all, I currently have some XCP-NG hosts managed by XOA and want to migrate to XO from sources. I don't need help following the build directions, they are very clear and within my technical ability to follow. My question is, how can I gracefully (as possible) migrate from XOA to an XO built from sources? This is a lab and I'm more interested in the features than supportability.

Also, what are the reasons not to do this? Even the entry $80/mo is more than I want to pay to run the lab and the core feature set in free XOA is lacking.

I had XOA die once and I assume this would be a similar recovery, topology and VMs will be intact, users will need recreated. What else should be on my radar?

Thanks
Anthony