Hi,  LVM host-based migrations for the most part will likely not be thin-aware if you have logical volumes that consume the entire disk, but maybe the FS is not 100% full.  Having VPLEX at the target changes the answers a little bit because the VPLEX does not support the UNMAP SCSI command. This means that if the migration involves you issuing manual reclaims at the host level after the migration is completed, the VPLEX will not pass those commands to the array to reclaim. This means that you might want to migrate to the native array to get the space savings and then encapsulate as a thin device under VPLEX.  There are a variety of tools that aren't thin aware from a migration perspective (probably too many to list and that I have used given the different array tools out there..haha). What I would do it determine what operating systems you have to migrate, what the source and end migration targets are (sounds like VPLEX in this case) and then you can narrow it down to what is supported. If these VPLEX clusters are in a Metro, you could just create a DR1 device and drop the source leg as another migration alternative as well.
Hello everyone, I have a vmax 20k which uses thin provisioning and allocates tdevs to a vplex. vplex then carves out storage from this tdev and presents to the hosts. There is a need to move the data to another storage array (not necessarily a vmax) using recoverpoint or host based migrations. What type of array based and host based migrations can preserve the thin lun after it is migrated to new array?. I dont want the lun to lose all its unallocated space after the migration so i need to know which methods will preserve the thin feature of the LUN and which ones will not. Please assist. Thank you.  
Tdev migration