When docs, code, resources are scattered around on various team shares, repros, etc and a new team starts up, one of the first things they think about is "hey! we should have all the docs/code in ONE place!". But there's a REASON code/files/docs are in different stores. Because that organization makes sense too.
It's like this great XKCD comic about standards...
It's old-school thinking that digital resources need to be centralized. In today's world with URLs to all resources, sites, repros, etc as long as the resource is in the cloud, it can be linked to! I wish we took better advantage of that.
If you enforce re-organizing bits in a central location, inevitably you end up with people copying files to the new location bc they want to keep them in their original location as well. Then you end up with duplicates and worse out-of-sync files.
Instead of thinking about centralizing all team resources/docs/files/etc, consider centralizing the INDEXING of resources. You can create as many indexes as needed. And index can be a Quip Sheet, a Wiki Page, SharePoint List, or anyplace you can LINK to the resources of interest.
This goes for places you need to "upload a document to", like a Salesforce Project Plan. Instead let's use fields to "Link to Project Plan". That way the uploaded one isn't out of sync the moment the source doc changes or you have to keep re-uploading every time you make a change.
I've been in so many organizations now that think they need to bring all the files into one place. And sometimes that makes sense. But rarely compared to simply creating a good index to point to all the resources of interest. If considering that, be very mindful about that idea and please talk to those that would be 'moving their files' over to understand why they're where they are now and what impact that would have. Maybe it's worth the change, but stay in connection with those affected about it and really consider if it's worth the change. It's rarely been in my experience.
Also see: Store All Files in the Cloud