[fredrik-j]

Yes, regularly. Some archaic code has a surprising longevity. Personally at least once per month I end up with a case where I wonder why some code was implemented or for what purpose. Context that is rarely documented in the source code, but is often exposed at least implicitly through commits, commit messages, date or authors.

I strongly advice against abandoning revision history just because it is easier to just start fresh from a single git commit of the current state of the code. Especially so for code that has been in use more than a couple of years, where the developers may have forgotten the purpose or who did what.

Surely you can convert the svn repository to git with history intact? We did that when we migrated from cvs to mercurial. If it is too complicated to do directly from svn to git, maybe it is easier to convert via mercurial, i.e first from svn to hg, then from hg to git?

https://www.mercurial-scm.org/wiki/ConvertExtension