I'd imagine that with 300 developers, a good fraction of them already use git and github for their own projects, and so they would be comfortable with using the

I'd imagine that with 300 developers, a good fraction of them already use git and github for their own projects, and so they would be comfortable with using the interface. Not that SVN is a bad choice -- depending on your company's workflow, familiarity with git and the need for more localized version tracking there are tradeoffs in either solution. However, even if you're counting 60.000 euro per year, it's not really such a large number when you consider that you have 300 developers. Saving on average 7~ hours per developer per year in work efficiency would more than make up for the fees, but the costs of switching over and perhaps picking up a new version control is also something to consider.