> But I also think that in a typical corporate environment (which they now claim to be their main target market) this is far more likely to be management failure and a "that's the way we've always done it" attitude than any *real* need.
A good reason to use SVN is (was?) maturity. Not sure about now but a few years ago there was already a number of great SVN GUIs while the git CLI was still evolving.
Once SVN is here and does the job, depending on the "real needs" there can be very little reason for a costly migration. Migration cost is not just about finding a silver "svn2git" bullet, it's also about re-writing build scripts, training users, etc.