Hi Ryan,
Thanks for the comments
1) In this initial release, this is not a configuration we currently support. From a workflow standpoint, is that what you would expect? If you can provide some more feedback on what you like to see and expectation, this would be helpful to Engineering.
2) This was something we had considered but most folks would want to keep the same IP of their VC after the migration to VCSA, else that might have other implications when talking about other VMware solutions or 3rd Party Solutions tied to that VC. In the case of our demo, VUM was running on a separate host so after the migration VUM continues to work as the VCSA can still point to VUM. In your scenario, since it also runs on VC you would need to change the IP/Hostname and re-register the plugin with VCSA after the migration, that would be an approach to that.
If you feel more comfortable sharing details of your environment privately or would like to further engage with us regarding your requirements feel free to shoot an email to Todd tvalentine@vmware.com