How to Back Up Autodesk Forma and Procore Project Data (And What Happens When You Don’t)

Most construction firms assume their project data is backed up because it lives in the cloud. It isn’t, quite. Autodesk Forma and Procore are highly available platforms, and neither is likely to lose your data through infrastructure failure. But availability protects against their failure modes, not yours — and the overwhelming majority of construction data loss is caused by something happening inside the account, not to it.

Does Autodesk Forma or Procore back up your project data for you?

Not in the way most firms assume. Both platforms maintain infrastructure-level resilience and internal redundancy, but that protects against platform failure, not against deletion, permission changes, project archival, licence lapses or a departing subcontractor taking a folder with them. Under a shared responsibility model, the platform is accountable for the service and your firm is accountable for holding an independently controlled, recoverable copy of the project record.

What causes data loss most often in construction environments?

Rarely a platform outage. In practice the common causes are accidental deletion or overwriting by users, permission and folder-structure changes that hide data rather than delete it, subcontractor and joint-venture offboarding at the end of a work package, project archival or licence expiry that puts historic projects out of reach, and ransomware reaching cloud-synced folders from an infected local machine.

The pattern worth noticing is that most of these are routine administrative events, not disasters. Nobody escalates a folder permission change. That is exactly why the loss usually goes unnoticed for months — typically until someone needs the data for a closeout package or a dispute.

How frequently should construction data be backed up?

Backup frequency should follow how fast the data changes and how costly it would be to reconstruct. Active projects with daily drawing issues, RFIs and site photos generally warrant a daily or near-daily backup; projects in slower phases may be weekly; and completed projects need a full archive captured before the project is closed or the licence lapses. The interval you choose defines how much work your team would have to redo — set it against tolerable rework, not storage cost.

What distinguishes construction-grade backup from generic cloud backup?

Generic backup tools copy files. Construction project data is not just files, it is files plus metadata, version history, revision relationships and folder governance, spread across platforms that each expose data differently. A construction-grade approach connects to the construction platforms directly, preserves metadata and versions, and produces per-file evidence of what was copied, skipped or failed.

How to configure a controlled backup with File Sync

1.   Create a workspace, then create a sync for each project or platform in scope.

2.   Select the source: Autodesk Forma / ACC, BIM 360, Procore, SharePoint, Bluebeam, Egnyte, Dalux or a Windows location, then the project and folder.

3.   Select the destination your firm controls, and enable create source folder in destination so the structure is preserved.

4.   Enable Include Metadata so the archive stays searchable, and Sync All Versions where the full revision trail is required.

5.   Set the schedule to match the project’s change rate, and use filters to exclude file types or sizes that don’t belong in an archive.

6.   Leave “Delete files not found in source” switched off. It keeps a mirror faithful, but it also propagates deletions into your backup, the opposite of what an archive is for.

7.   Run the sync, then review the activity log and retry any failed files directly from it.

How do teams test data recovery processes effectively?

Test the restore, not just the backup. A backup that runs successfully every night still fails you if nobody has confirmed the data comes back usable. An effective test restores a representative folder to a working location and has document control verify file counts, folder structure, metadata and version stacks, performed by someone who did not build the backup, so the process is proven rather than the person.

Run this once per project at minimum, and again before any project is closed or a licence is surrendered. That last window is the one firms most often miss.