While I'd like to switch to IPv6 it just doesn't make sense for us to do so at the moment, even with APNICs IPv4 exhaustion issues.
Of course I may have spend another couple of hours this week when I asked the tunnels, but this was first a good opportunity to learn.
I'm hosting my sites on Hurricane Electric, which is a big supporter of IPv6. All my computers have IPv6 support - even my DSL modem. The only missing link was I had not spend any time configuring it.
But tust being able to ssh from HE to my laptop or other device when I will forget it at home (which happens to me time to time), without having to setup port forwarding will save me more time that that. I know how much time I spend on port-forwarding.
Fixing issues once and for good just seems "better" - and even more when I get to learn something new that will become mainstream very soon with IPv4 exhaustion.
Where was your testing and from all locations used by your corporate clients? Where was the part where you had to predict the impact on end users with incorrectly set up dual stack trying to access the IPv6 site first and get buy in from the people affected? When did you produce the change request documentation and have it approved?
Things that are trivial for home and development environments are not trivial once you have a production site that need to stay up.
I suggest not to wait that long, go ahead & start testing what your IPv6 readiness is. taking example Deployment story of heise.de, dual stack can be implemented without causing much problems.
A perfect day to do this will be June 8, 2011 which is World IPv6 Day, also known as "Test Drive Day".[1]