VMotion is not supported on VMC that is actively handling clients and APs, simply because we cannot guarantee that there will not be an interruption or corruption of the VMC database (the multiple databases used cannot be quiesced).
However, if the macaddress or UUID of the VMC is getting changed, then something is wrong with the vMotion config on the VMWare cluster. In a proper vMotion, the vMAC and UUID should be preserved.