Do you have DRS on those vMotion? If yes and it's not pinned to an ESXi Host it's probably have been moving/vMotioning anyway.
I'm not aware of limitations with NSX-v Edge and vMotion.
I'm only aware that NSX-T Edge doesn't support vMotion prior to NSX-T 2.5.1
Documentations seems say no issue with NSX-v and Edge vMotion.
But here are some KBs related to NSX-v Edge and vMotion in case you haven't had a chance to review them
Symptoms: After migrating both NSX Edge Services Gateway and Distributed Logical Router to a different ESXi host using vMotion, the network connectivity for virtual machines relying on the routing services fails for several seconds.
Resolution: To resolve this issue, the Notify Switches option needs to be set to Yes in the Load Balancing and Failover Policy on the ESXi host
Symptoms: If you vMotion the Edge like a normal VM, future redeploys of the edge will revert back to its configuration in NSX. Thus, a normal vMotion of the Edge is never permanent until original configuration (in the NSX view) is modified.
Resolution: steps to redeploy Edge
The above method is the preferred process for migrating an Edge. However, if a manual migration is required, you can use 1 of the 2 workarounds:
Use the VMware vSphere Client to migrate the Edge or DLR Control VM.
Important: In NSX-T, the NSX Edge VM does not support vMotion.Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://nz.linkedin.com/in/bayupw | twitter @bayupw
Hi. Thank you very much. We do not have the NSX appliances pinned to any hosts, only anti-affinity rules. I have vMotion all appliances in the past, I just got very nervous this time. Don't know why. My brain I guess. It sounds like we will be good. Thank you very much for you help! Thanks,,,