That's sort of not really the point. Like I said before, enterprise is but a piece of what I would consider end site traffic. I did some time in enterprise in the 1990's, I found that it wasn't for me, now I deal with enterprise types of services that are just that, services that sit in the middle of a far larger network or autonomously in a purpose built environment. Enterprise is arguably the last pieces to change, that's pretty well established. I'm familiar, I'll never argue that. What I will say again is that enterprise networking is just a single piece of a very large picture.
...and I know I'm really just adding fuel, but I stand by my statement that IPv6 isn't more complex, and I'll tell you why. All of the bits to make IPv4 work are just that, bits. They're extra stuff outside of the protocol that need to be kept track of. Much of that is handled within the protocol itself with v6, so in principle you're right, it is more complex because it does or removes many of the things that require helper apps in v4, so overall I'd say that if complexity is the criteria, it's actually more straightforward. Personally I'd rather keep track of a few tools in one toolbox than a bunch of tools in a bunch of boxes that all need to be tracked. That's just me, I'm always trying to keep things simple. Practically speaking, once you learn that the addresses have HEX, it's really not that different. The biggest hurdle I hav ecome across in all the classes I've taught is that engineers, in general, can't memorize IPv6 addresses. I've always advocated against that anyway. It fosters an environment that lacks documentation and proper IPAM/DNS.
To address the SDN comment, SDN is but a buzzword, and yes, all of the current OpenFlow goo is done in IPv4.....however, it's all OpenFlow 1.0. 1.3 supports IPv6 and it is the version I would start to consider as production ready (and even that is a stretch). There are other SDN solutions that support IPv6, too.
As an additional data point, from the AT&T page:
Enterprise Networks and Applications
AT&T's IP backbone network supports IPv6 today, and we are offering enterprise services that support IPv6.
You could probably get it on your connection from 1998 now, too, if you were so inclined.
At the end of the day I'm not trying to convince anyone that they need to go out and convert everything to IPv6, that is a fools errand and I've been around long enough to know better. If you don't want to learn it, no worries. If you're in a small or conservative environment, you may not see it for a while, and that's totally ok. Truthfully, even if it was on everywhere, I don't see a time in my career that there won't be dual stacked environments.
However, if you're working in or with the data center, cloud, content delivery, research, education, service provider, security, SAAS, or any other number of other discipline, you may want to consider learning something about and being prepared for the time that your boss asks if you're "IPv6 ready". Time Warner enables it by default as it rolls out, comcast enables it by default as it rolls out, AT&T is has enabled it across most of their residential infrastructure, it's been in backbones for years.
They're not forcing anyone, it's just getting turned on and when the clients are there, they use it since the content is there and IPv6 is preferred in nearly every modern OS.