In my case this was because Git has a model of version control that is nowhere as straightforward as SVNs and several hundred command line options without any g

In my case this was because Git has a model of version control that is nowhere as straightforward as SVNs and several hundred command line options without any good indication of what to do when. We also had a lot of problems with what I think of as "Linux Arrogance" - the person who took the lead on rolling out git refused to even try to help anyone not using git in a bash shell, which is an issue when all the devs are .net developers with no cygwin experience. Once you can figure out the commands you need to use git is very nice, but it's a nightmare to start and requires a big mental step backwards to teach someone with no exposure to it.