Change costs
I don't believe it is fear of change most IT admins have. It's not wanting to:
* Learn new systems
* Document new systems
* Learn the incompatibilities between the existing systems and the new
* Research solutions for the incompatibilities
* Document the incompatibilities
* Train your staff in the new system (or hire new staff)
* Find workarounds for things that don't work at all on the new system
* etc etc
Unless the payoff is large, it's not going to counter the significant cost of change. And when you're flat-out doing other, more productive work, that payoff had better be huge to make you stop and do all the above work just to support a system that is functionally basically the same, but just happens to be a personal preference of some employees because "it's what I use at home" or "it looks cooler".
