I've done it both ways. I've had to partition a years old code base, keeping an old SVN repo up to a certain date, then using my own limited git-svn skill to pr

I've done it both ways. I've had to partition a years old code base, keeping an old SVN repo up to a certain date, then using my own limited git-svn skill to promote some recent months to git, to establish a git repo for use from there forward. At another company we had a magician who ported maybe 10 years of SVN history to git over a weekend, and we were able to abandon the SVN repo. In the first case, I don't recall ever needing to go back into the old SVN repo, spelunking for "how we used to do it". But the capability was there, with the minor hassle of not having a single repository to search. The git repo, with some minimal recentish history, soon became the authoritative source, and we never looked back. [edited to clarify the partitioning of the first codebase]