svMotion is not supported with CDP replicas as it creates many extra files that are left behind thus breaking the replication.
Currently the only workaround is:
- Remove VM from job/policy
- Remove replica vm from vsphere
- Manually move the files from datastore to datastore
- Re-add the vm in vsphere
- Re-add the vm in the job/policy and use replica mapping to point to the just re-added vm