Quote - The conversion process leaves NO original dress bones.  A cape is just rigged to the figure so unless it's got movement morphs it's basically useless.  I just tried converting the Sorceress to Genesis, that was a joke too because the movement bones on the skirt were gone replaced by Genesis default leg bones and the billowing long sleeves... the weight mapping was a mess on that.

I'm taking more on theory side because I don't know how to make autofit clones, but SickleYield shown that you can have custom bones in autofit - her/his autofitted skirts don't follow the legs. Extending this idea, you probably can have a special autofit rig for dresses that adds some basic 4-8 bones for skirt (front-back-left-right), like Wancow's rig have, instead of 4 leg-likes (thighs-shins) that we currently have. It is still not full transfer with custom bones but it could be better.

Custom bones are difficult because they aren't predictable. I can add two custom bones, I can add twenty - how you'd deal with it? If I knew how to program plugins like autofit, I'd add in template to each figure a list of figure bones, and everything that isn't from this list (like skirt bones, scarves with multiple parts) would be just proportionally scaled to an closest parent figure bone(s), along with zones of influence and repositioned slightly to some adjustment algorithm (if, say, hips of the figure are higher), but generally left unchanged.

Quote - As a customer, I don't think that you'll have to worry about conversion because Dawn's poser and DS version share the same topology, polycount, shape and rigging.

Topology/polycound/shape - yes. Rigging - no. Both are WMs, but weightmaps in DS and Poser are different (this is why all problems with Genesis import, I think). And while shapes are same, DS and Poser use different morph injection systems (dufs and pmds). So no, it won't be automatic useablility for both figures. My question is how much trouble would it be.