Currently, when a migration is run from VMware, the VM PVCs being created with a name based upon the name of the migration plan and VMID. Since you cannot rename a PVC after the fact, Is there any way to influence how these names are generated prior to the PVC being created?

Could there either be a way to manually specify a disk name for the migration, or potentially preserve the same alias name similar to the request here: 

https://issues.redhat.com/browse/MTV-1172

Specific request in  Customers words: 
"The default naming scheme that MTV uses for PVC makes it very cumbersome for support teams to identify PVCs based upon a VM’s name, using the VMID in the name is meaningless after the VM is migrated. Ideally, we would like to use some type of templating to define how the PVC should be named. Additionally, for new VM deployments on OCPV we have an established naming scheme for PVCs and would like migrated workloads to align with that."