Yes, you are completely correct. It was such a PITA to switch from microsoft's visual sourcesafe to svn in the company I work for. That happened cca. 6 years ago. My coworkers were so entrenched in their ways that they mostly simply refused to listen to anyone, least of all to me. I was baffled then, but I think I know what is the problem: making a change to a work process means a certain amount of effort from all participants in that process. And people don't want to bother with new stuff exactly for this reason.
Needless to say, even when we finally switched to SVN, we still had problems. Coworkers mostly didn't read the svn manual or didn't care to understand what SVN is or does. My mailbox was literally burning with semi-hostile messages and for weeks I couldn't do anything except sit at coworkers' desks and explain the same thing over and over ...
I think it's mostly about risk aversion. I've seen the exact same thing trying to push SVN over VSS. No one honestly thinks that VSS is the superior product, but once you have 5 plus years of history with it, it's what you know, and no matter what the reasons are, that is a risky proposition.
We're talking about people who would never shave a Yak because they'd wrangle 100 hairy Yaks than spend 20 minutes reading how the automatic Yak shearers work.
Well, yes, that's probably ultimately true in a lot of cases, but if you approach it constructively, you have a much greater chance of success than if you just assume laziness.
Needless to say, even when we finally switched to SVN, we still had problems. Coworkers mostly didn't read the svn manual or didn't care to understand what SVN is or does. My mailbox was literally burning with semi-hostile messages and for weeks I couldn't do anything except sit at coworkers' desks and explain the same thing over and over ...