Could be, lots of pros and cons to each scenario - doubt either are easy by any measure. E.g. for about 20% we didn't even have a single piece of documentation

Could be, lots of pros and cons to each scenario - doubt either are easy by any measure. E.g. for about 20% we didn't even have a single piece of documentation other than the server name for who might actually care about the VM going down for the migration we wanted to schedule. Let alone how to test the migration, when it is best to do it, what software was actually running on it, if it's actually managed/monitored integrated with/by other systems whoch need to be looked at too, or if it could just be shit down instead (yay healthcare mergers and acqs). Our migration was also to VMware from (mostly) Hyper-V at the time, so not as much custom tooling needed. On the flip side a cloud provider is going to have all of the owner contact info but no direct control of the guest OS to effect the change so the battle is more with trying to get the customers to care enough to do the migration with you but not be so bothered by it all they up and leave your hosting.Not exactly a walk in the park either. In either case - almost never the tech that's the hard part for sure :).