Unfortunately not that easy. I remember the issue you were talking about. I did verify each VMDK has a different name. ONe VMDK has _1_1 in the name but migrating everything but that disk has the same error. I also tried to migrate each VMDK by itself. I tried just migrating the configuration files as well and all of them generate the same error.
I'm working on getting a maintenance window to try a cold migration. I also plan on unregistering the VM and just moving the folder of files if a normal cold migration doesn't work. I renamed the VM before trying the migration and also tried changing the name back. Same error.