It feels like every tool we use either provides or requires its own file storage—SharePoint, OneDrive, Bluebeam, Autodesk, Adobe, Propeller, Dropbox, Outlook, and others. How do organizations keep track of where important project data lives, especially after a project closes and someone needs records several years later?
One option would be to require everyone to archive everything into a single platform, but copying files may lose important metadata, permissions, version history, or links. How do you handle both day-to-day organization and reliable long-term retrieval?
3 Answers
Data owners should be responsible for deciding what needs to be retained and requesting archival when a project ends. Everything else can follow the normal backup policy. For important records, I’d keep an inventory showing the platform, project, owner, retention date, and any special restoration requirements.
I’d separate this into two problems. Active-project storage is mostly about establishing ownership, naming conventions, and a documented system of record. Long-term retrieval is more about taxonomy and metadata: project ID, client, document type, retention period, and the original system should be captured in a central index. That way, people can find where something lives without forcing every platform to be flattened into one repository.
The simplest way to reduce the problem is to limit the number of approved storage systems. Disable or restrict unnecessary integrations where possible, define which platform is authoritative for each type of record, and back up critical cloud data to storage you control. You may not preserve every feature or piece of application metadata when exporting, so test restores and document those limitations instead of assuming a generic file copy is enough.

That makes sense for ownership, but backups are part of the concern too. The backup strategy still needs to cover all of these separate cloud platforms, or at least clearly identify which ones are protected by their own retention and recovery features.