If you &quot;keep getting besieged to move [your] projects from svn to git&quot;, I can guess that who is asking is probably downstream consumers of your projects. What they might actually be wanting:<p>- Familiarity. Everyone uses git nowadays; like it or not, svn projects are the odd ones out.<p>- Fast, offline querying of the project&#x27;s history. With git, they have a full copy of the project&#x27;s history in their local computer, while with svn, any query has to go to the server. This helps a lot when chasing regressions, or just when browsing the changes between one release and the other.<p>- Easy branching. Branches in git are more lightweight than branches in svn, and git&#x27;s merge functionality is quite good. When they want to propose some change to your code, they can just create a branch in their local copy, make the changes they want, publish the branch somewhere, and ask you to merge it; this is made even easier by sites like github. With svn, unless they have an account in your svn server, they have to do it the old-fashioned way.