We are currently in the process of moving to Stash GIT/ Bamboo. Although we have .Net projects, we have VB6, C, C++ and Cobol projects dated back to the late 90's that are still in service. That's another topic. 
We have over 3000 software projects that make up 25 different applications that, when combined, make one product. 30k files at 17 gig. We only modify a fraction of those each release but they are all valid and could be subject to change in any release.
So my question is: Would we need a repo for each of the 3000 projects or should we only have a repo for each of the 25 application folders that contains a few hundred projects each? I think it would be infeasible to have one repo for all of them because of the size of the repo during clones. I'm also thinking that 3000 repos would be unmanageable branch-wise since we are planning on a model like http://nvie.com/posts/a-successful-git-branching-model/ . We are also using SourceTree on the developer end. I would like to hear if anyone has faced this dilemma and the route they took. Please note my definition of a project is what you would create in Visual Studio or similar. For example a Hello World project.
All responses are welcome! Thanks very much!
