@jamerican28, Anything Storage vMotioned to vsanDatastore will be thin-provisioned by default (and thin/thick on destination are actually not selectable options during migration).
For anything where you want the space reserved (e.g. like it would be with non-eager-zero Thick disks), this can be configured in the relevant Storage Policies applied to these Objects (e.g. one with a rule of Object Space Reservation = 100).
Previously there was requirement for some multiwriter vmkds (e.g. Oracle RAC) to be EZT but this requirement no longer exists:
https://blogs.vmware.com/virtualblocks/2019/12/19/eager-zeroed-thick-requirement-multi-writer-disks-...