Migrating an SVN repository to Git
Companies are afraid to change their versioning systems. They often try to explain themselves by saying that Git is too complicated, it has insufficient features, or even both.
Git is not necessarily better than Subversion (SVN), it's just different. For example, if you are developing on the road with SVN, you cannot commit your changes if the repository can't be reached. Git is decentralized, so your local working copy is a repository. Git is a bit harder to learn than SVN, but it adds complexities such as two modes to create repositories, a checkout/clone, a commit/push, and so on.
In one word, Git is more flexible. There is more than one way to do a task. Also, its backbone is its community that develops ingenious tools (GitHub, add-ons inside editors, and GitLab).
SVN to Git migration is extremely simple, and we can retain the repository's entire history. This is not a sufficient reason to not migrate your repositories. If you want to...
