Yes, that’s what i was referring to. The migration path used by this tool does not allow the use of autogrow as you have to land first in a 5.5 version which is backed up by a single vmdk. That seems to be the only thing preventing me to change at the moment.
I tried the tool this morning with an external MSSQL holding a restored dump of vCenter DB (which I have in the same vCenter host) and the tool seemed to work nicely. Congrats for achieving this!
