If failure is no option and you need a failsafe approach - here is what I do when the vmotion button is out to lunch.
Power off VM.
Remove all snapshots.
Add a snapshot / delta to the valuable 4 tb vmdk only.
Move the empty - because yet unstarted snapshot to the target directory.
Adjust vmx and vmdks.
Power on the VM - it runs the 4tb vmdk from the snapshot in the target location.
Now you can use vmkfstools -i and clone the base-flat.vmdk to the target location too.
You are in no hurry now.
If something goes completely wrong - you still have the original basedisk in untouched state ,,,
Then when the clone is done you need another 5 minutes maintenance window to attach the snapshot back to the base.vmdk in the target location.
You can do this for one or for all disks.
For all disks would be slightly easier - creating a single snapshot for one disk only is straightforward but takes some extra steps.
Looks like a pain at first sight - but it is failsafe.
I always use this approach when I prefer predictable results over convenience.
Anyway - you still have full control when this goes wrong - you just wasted time - if the automatic function fails results will be less favourable.