Keep Procore and Autodesk Forma / ACC in Sync | Graitec - UK

Keep Procore and Autodesk Forma / ACC in Sync

Connect the construction platforms your teams already use – without forcing project teams into one system or relying on manual file transfers.

Graitec File Sync helps construction teams synchronize, migrate, and back up project data across Procore, Autodesk Forma – formerly Autodesk Construction Cloud (ACC), SharePoint, OneDrive, Bluebeam, Egnyte, Dalux, and Windows-based file environments.

Whether your teams are managing RFIs and submittals in Procore, coordinating design and documents in Autodesk Forma/ACC, or collaborating through SharePoint and Bluebeam, File Sync provides a controlled way to keep project information moving between systems.

Book a File Sync workflow assessment

I agree with GRAITEC’s Terms of Use and Privacy Policy

Notes: GRAITEC group, the controller, processes personal data with the ultimate aim of safeguarding information relating to the visitor’s identity in order to send to him/her information on GRAITEC products and services.

Can Procore and Autodesk Forma / ACC stay in sync?

Yes. With the right integration and sync strategy, construction teams can keep key project information aligned between Procore and Autodesk Forma / ACC. Graitec File Sync supports synchronization between Procore and ACC for files, documents, sheets, RFIs, submittals, photos, metadata, attachments, and version history where supported by the connected platforms. It can also export supported project data into other systems such as SharePoint, OneDrive, Windows folders, BIM 360, Bluebeam, Egnyte, and Dalux for backup, sharing, or handover workflows.

Keep Procore and Autodesk Forma / ACC in Sync | Graitec - UK

Why construction teams use Procore and Autodesk Forma / ACC together

Most construction teams do not operate across multiple platforms because they want complexity. They do it because different stakeholders have different responsibilities, contracts, workflows, and technology standards.

  • Procore supports project management workflows. Many contractors rely on Procore for day-to-day project execution, including workflows such as RFIs, submittals, drawings, photos, and project documentation.
  • Autodesk Forma / ACC supports Autodesk-centered project delivery. Owners, designers, BIM/VDC teams, and delivery partners often use Autodesk cloud environments to manage design collaboration, documents, models, and project information.
  • SharePoint, OneDrive, Bluebeam, Egnyte, Dalux, and Windows folders remain part of the ecosystem. Project data does not live in a single place. Teams still need to share, archive, review, and back up information across many environments.

The goal is not to replace one platform with another. The goal is to make the systems construction teams already use work together more reliably.

The challenge: manual transfers create avoidable risk

When project information has to be downloaded, renamed, re-uploaded, rechecked, or manually reconciled between systems, small delays can become project risk. Drawings may drift between platforms. RFI or submittal packages may need to be recreated. Metadata can become inconsistent. Version history can be difficult to validate. Backup and closeout teams may not know which platform contains the latest record.

These issues are not a failure of Procore or Autodesk Forma / ACC. They are a natural result of project teams working across multiple valid systems. File Sync addresses the seams between those systems by automating controlled data movement between them.

How Graitec File Sync connects Procore and Autodesk Forma / ACC

Graitec File Sync is a desktop application that connects supported cloud and on-premise platforms through secure connections, workspaces, and syncs. Teams can define the source, destination, folders, data categories, metadata, versioning, filters, and schedules for each sync workflow.

  • Connect Procore and Autodesk Forma / ACC using supported integrations.
  • Sync files and documents between Procore and ACC in either direction.
  • Synchronize sheets and drawings between ACC Sheets and Procore Drawings.
  • Synchronize RFIs and submittals between ACC and Procore, including attachments where supported.
  • Sync project photos and export project records as standard files when needed.
  • Preserve file structure, metadata, and version history where supported by source and destination platforms.
  • Run syncs manually, on a schedule, or as part of controlled migration, backup, or collaboration workflows.
  • Use logs, activity views, filters, and retry tools to monitor and validate sync outcomes.

What can be synchronized between Procore and Autodesk Forma / ACC?

Project data type Supported File Sync workflow
Documents and project files Sync between Autodesk Forma and Procore. Supports standard document copies, file versions, and custom metadata where the connected platforms support them.
Sheets / drawings Sync PDF sheets between Forma Sheets and Procore Drawings. Sheets can also be exported as PDF files to supported destinations.
RFIs 1-to-1 RFI synchronization between Forma (ACC) and Procore, including attachments where supported. RFIs can also be exported as PDFs with attachments to other supported platforms.
Submittals 1-to-1 submittal synchronization between Autodesk Forma (ACC) and Procore, including attachments where supported. Submittals can also be exported as PDFs with attachments.
Photos Sync photos between Autodesk Forma and Procore where supported, and export photos as image files to other supported platforms.
Metadata Synchronize supported metadata fields. For Procore, metadata population is update-only and requires the fields to already exist in Procore.
Version history Sync the latest file version by default, or sync all available historical versions for one-time migration and audit-focused workflows where supported.

Use case 1: Keep project documents aligned across Procore and Forma / ACC

When one stakeholder publishes documents in Autodesk Forma / ACC and another team works from Procore, File Sync can help keep the relevant project files aligned so teams are not relying on manual uploads or email-based file movement.

  • Select source and destination projects.
  • Choose specific folders, full project file areas, or multiple folders.
  • Preserve folder structure when needed.
  • Use incremental copy so only new or modified files are transferred after the initial sync.
  • Use logs to review what was copied, skipped, updated, or flagged for attention.

Use case 2: Sync drawings, RFIs, submittals, and photos

Project collaboration is not limited to documents. File Sync also supports Procore and Autodesk Forma workflows for drawings/sheets, RFIs, submittals, and photos. This helps teams keep key project records visible across systems without rebuilding the same information manually.

For example, teams can synchronize RFIs between Autodesk Forma and Procore, including attachments where supported. They can also sync sheets between Forma Sheets and Procore Drawings, or export structured records as PDFs and attachments to other platforms for backup, reporting, or closeout purposes.

Use case 3: Preserve metadata and version history during controlled migration

Some teams need ongoing platform-to-platform sync. Others need a one-time migration, such as moving active or historical project information into Autodesk Forma. In both cases, project context matters. File names alone are not enough.

File Sync can help preserve folder structures, supported metadata, and version history where the source and destination systems expose and support those details. For full migration scenarios, teams can choose to sync all available historical file versions rather than only the latest version. For ongoing syncs, versioning can be used to create a new destination version when a source file changes.

Because version and metadata support depends on the connected platforms, Graitec experts recommend scoping these requirements before migration or sync setup.

Use case 4: Back up project data to a location your firm controls

Sync is not only about collaboration. It is also about resilience. File Sync can copy project data from cloud platforms into controlled backup locations such as Windows folders, SharePoint, OneDrive, or other supported systems. This helps teams support retention, audit, closeout, and business-continuity needs.

For backup-style workflows, teams can define schedules, copy rules, and destination locations, then review activity logs to confirm what has been transferred. File Sync can also export supported Autodesk Forma and Procore project records into standard file formats when teams need file-based archives outside the source platform.

Why File Sync is different from ad hoc manual processes

Manual process File Sync approach
Download files from one platform and upload them into another Configure controlled source-to-destination syncs between supported systems.
Rely on people to remember which files changed Use incremental copy, scheduling, filters, and logs to manage ongoing updates.
Rebuild folder structures manually Preserve or recreate source folder structures where required.
Re-enter metadata manually Synchronize supported metadata fields and use Excel-based metadata workflows for selected scenarios.
Lose visibility into what transferred Review file-level logs, warnings, skipped items, and errors.
Restart large syncs after issues Retry failed files from previous sync logs without rerunning the full workflow.

 

A practical Procore and Forma / ACC sync workflow

A typical engagement starts by understanding the platforms, projects, data types, and business outcome. The workflow usually follows five steps:

  1. Assess the workflow. Identify whether the goal is migration, collaboration, backup, closeout, or a combination.
  2. Confirm platforms and permissions. Verify Procore, ACC/Forma, SharePoint, Bluebeam, Windows, or other systems and confirm admin requirements.
  3. Map project data. Define projects, folders, data categories, metadata, version history, filters, and destination structure.
  4. Configure and run syncs. Create connections, workspaces, and syncs; then run manually or schedule recurring syncs.
  5. Validate results. Use logs, destination checks, and file/folder review to confirm completeness before expanding the workflow.

Technical readiness checklist

Before setting up a Procore and Forma / ACC sync workflow, prepare the following information:

  • Which platforms are involved: Procore, Autodesk Forma/ACC, SharePoint, OneDrive, Bluebeam, Windows, Egnyte, Dalux, or others.
  • Whether the objective is ongoing sync, one-time migration, backup, collaboration, or closeout archive.
  • Which project data types must be included: documents, photos, sheets, RFIs, submittals, attachments, metadata, versions, or exports.
  • Number of projects, average data volume, folder structure, and expected sync frequency.
  • Whether all file versions must be included, or only the latest version.
  • Which metadata fields need to be preserved or populated.
  • Who has admin access to Procore, Autodesk Forma/ACC, Microsoft 365, and any other connected systems.
  • Where File Sync will run: desktop, dedicated server, or virtual machine, depending on the license and deployment model.
  • Whether Windows network shares are involved, and whether UNC paths and domain identities are ready.

Who benefits from Procore and Forma / ACC sync?

  • Project managers gain confidence that key project information is moving between systems without repeated manual reconciliation.
  • BIM/VDC teams can support coordinated data environments where drawings, documents, and project records stay aligned across stakeholders.
  • IT leaders get controlled, auditable sync and backup workflows with secure authentication and platform permissions.
  • Document controllers spend less time downloading, uploading, checking, and rechecking documents across systems.
  • Owners and operators gain better continuity and a stronger project record for handover, audit, and long-term asset management.

Why choose Graitec File Sync?

Procore and Autodesk Forma / ACC both play important roles in the construction technology ecosystem. Many firms use both because different stakeholders need different workflows.

Graitec File Sync is built for construction teams that need to move, synchronize, and protect project-critical data across the systems they already use. It combines platform connectivity, file synchronization, metadata support, versioning, scheduling, filtering, logs, and backup workflows in one AEC-focused solution.

Rather than forcing a single-platform decision, File Sync helps teams make their existing technology stack work together more effectively.

  • AEC-focused sync workflows for construction data, not generic file movement only.
  • Support for Procore, Autodesk Forma/ACC, SharePoint, OneDrive, Bluebeam, Windows, Egnyte, Dalux, and more.
  • 1-to-1 data synchronization between Autodesk Forma and Procore for supported project data types.
  • Metadata and version-history support where available in the connected platforms.
  • Scheduled and incremental syncs to reduce repetitive manual work.
  • Activity logs, warnings, error handling, and retry tools for better visibility and validation.
  • Migration, collaboration, backup, and closeout use cases supported through one solution.

CUSTOMER PROJECT

How ACE Automated Construction Data Backups with Graitec File Sync

Discover how Associated Construction Engineering (ACE) transformed their manual backup process using Graitec File Sync. See how automation improved reliability, saved time, and ensured data security for Autodesk Forma projects.

Read the full story

Keep Procore and Autodesk Forma / ACC in Sync | Graitec - UK

Ready to connect Procore and Autodesk Forma / ACC?

Talk to Graitec about your Procore and Forma / ACC workflow. We will help you identify what needs to move, what should stay synchronized, what needs to be backed up, and how File Sync can support your project data strategy.

Book a File Sync workflow assessment

Download your File Sync free trial

FAQs

  • Yes. Graitec File Sync supports synchronization between Procore and Autodesk Construction Cloud / ACC for supported project data types, including documents, sheets, RFIs, submittals, photos, metadata, attachments, and versions where supported by the connected platforms.

  • No. File Sync is not positioned as a replacement for either platform. It acts as a connective layer that helps teams move, synchronize, and back up project data across approved systems.

  • Yes, File Sync can support migration workflows between Procore and ACC/Forma for supported project data. The exact scope should be reviewed based on project data types, metadata, version history, and platform configuration.

  • File Sync supports metadata synchronization across supported systems. For Procore, metadata fields must already exist before File Sync can populate or update them.

  • File Sync can sync the latest version by default and can also sync all available historical file versions for supported platforms in one-time migration workflows. Version support depends on the source and destination systems.

  • Yes. File Sync can copy supported project data to other supported destinations, including Windows folders and Microsoft 365 environments, to support backup, archive, and closeout workflows.

  • Yes. Syncs can be configured to run on daily, weekly, or custom schedules, depending on the workflow.

  • Permissions depend on the connected platforms. Procore requires the File Sync app from the Procore Marketplace. Autodesk Forma paid deployments require a customer-owned Autodesk Platform Services app or service account setup. Microsoft 365 environments may require Azure admin approval.