This kind of depends. Many years ago we migrated an SVN project to git(largely because of my constant complaining about SVN which I truly hate) but we didn't bo

This kind of depends. Many years ago we migrated an SVN project to git(largely because of my constant complaining about SVN which I truly hate) but we didn't bother with keeping the history. We simply kept the SVN repo for another ~2 years if we ever wanted to check something. At a certain point when we felt like the project was stable, we got rid of it. I've gone to looking back to where something came from on a number of occasions so I would say it is valuable. Which applies to any project on which a number of people is working on. Especially when there is a bug, git blame is a life savior. Which potentially has a lot to do with me being annoyingly pedantic about commit messages and branches. I did however had the "pleasure" of working with a guy who's branches were commonly called "bugfix102015" and commit messages along the lines of "fix some bug". In such cases there is not much you can do when shit hits the fan. For my very personal projects - hardly. Much like you, if something has been done 2 years ago, chances are it's working fine as it is, or you are not using it at all. So for personal projects, digging years back is something I don't ever recall doing.