If you don't know why you're making a change, or the benefits of making a change, you shouldn't be making, it period.
At the risk of making an unpopular statement, you shouldn't be promoting IPv6, let alone changing to it, because for you, you're creating a solution in need of a problem, and the only thing you'll get out of doing that is a headache. Seriously, your asking this question made me think of Joel's article on :Cats.
If you invent something that doesn't solve a problem, it better be entertaining.
And I don't know about you, but building a network from the IP scheme up does not strike me as good entertainment, particularly with IPv6 support leaving so much to be desired at present.
What you should be doing is reading up on IPv6, learning what problems it actually solves, and thinking about how implementing it can benefit your environment. Once you've done that and tested it a lab environment (so you know what new risks it creates and problems it causes), then you're ready to think about how to sell it for use in production up the chain of command.