@WoodyZ - You're right - the vCenter standalone is the tool to use. It is what I used to begin-with, and it is how I ended up with a 160GB VMDK.
Maybe I should've thought about it before I gave back my old Dell Latitude (from which I imaged-off), and cleaned it up nicely.
But I didn't... so I had to work with what I had - A bloated VMDK on a very fast Mac with very limited disk space.
(BTW exchanging big files between Win and Mac is by itself a story to tell... it is anything but strightforward, if you happen to have a larger-than-2GB file, which I did).
Re issues with "Migrate your PC" - Maybe you're right... I didn't have any problem with it, maybe because I migrated off of a VM running locally on my Mac (V2V, if you will 
). So I used the 4-digit code and it worked like a charm (~30 MB/sec R/W, which is not too shabby... about 50% of the max rate of the SSD, while running 2 OSes).
If you had to do it between 2 physicals, you'd be better off using the standalone vCenter P2V and an external drive.
If you're moving from PC to Mac (a path that has SERIOUS file-system compatibility issues), you can just take a good ol' ethernet cable (provided you have a thunderbolt-to-RJ45 adapter), plug 'em to each other, discover the temp IP addresses, and have a go at it.
Cheers.