SIINC keeps up to the 20 most recent revisions of each Procore document, plus the revisions Procore makes available for drawings and specifications. Sync runs add new revisions as they appear.
Keep every Procore project after closeout, in storage your company owns.
SIINC backs up Procore projects hourly as standard, or every 4 hours or daily if you prefer, into Amazon S3 or Azure Blob Storage in your own cloud account. It captures 35 Procore components, from drawings and RFIs to daily logs, change orders and invoices. The Procore Workbench lets your team search and download records without a Procore login, and SIINC can restore records back into Procore, including into a different Procore account.
- Backs up
- 35 components from Procore
- Find records in
- Procore Workbench, no Procore login
- Stored in
- Amazon S3 or Azure Blob Storage, in your account
- Access
- Read-only backups, through the official API
- Last reviewed
- 28 Oct 2026
Last reviewed
What happens to Procore project data when access ends?
Procore's own tool for keeping project data is Procore Project Archive, and it is an export, not a backup. Project Archive (formerly Data Extracts 2.0) builds a ZIP file of the tools and items a user chooses, when that user asks for it. Procore's help says the download is available for 30 days.
Procore Project Archive is private to the user who created it. The only other people who can see and download it are users with Admin permission on the project-level Directory tool. Most items arrive as PDFs, while documents and photos keep their original file type.
Project Archive works on active and inactive projects, but the person running it needs at least Read Only permission on every tool they include, and can only download an archive marked Partially Completed or Completed. In practice, one person with the right permissions has to build the archive for each project, download it and file it somewhere safe within 30 days.
| Procore Project Archive | What Procore's help says |
|---|---|
| How it runs | On request. A user chooses the tools and items, then Procore builds the ZIP |
| Tools covered | Up to 26 project tools, including RFIs, submittals, daily logs, drawings, change orders and invoices |
| What you get | A ZIP file. Most items as PDFs, documents and photos in their original format |
| How long the download lasts | 30 days |
| Who can download it | The user who created it, plus users with Admin permission on the project Directory |
Why back up Procore on a schedule instead of exporting at closeout?
A scheduled backup starts copying in the first week of the job and keeps going, so the record does not depend on someone remembering a closeout export. Procore Project Archive holds what existed on the day it was built. A backup taken run after run also holds what changed, and what was deleted, along the way.
Closeout is when the people who know a project are moving to the next one. The person with permission on every tool may have left, the 30-day link may lapse before anyone files the ZIP, and records argued over later, such as daily logs, change orders and correspondence, are needed for years after handover.
- The first SIINC run is a Full backup of every record and file version in the components you choose, and for a mid-sized project it completes the same day
- After that, Sync runs copy only what changed since the last run, hourly as standard
- Records deleted in Procore are kept for the term of your plan, so a deleted RFI is still in your copy
- Every run is recorded with its scope, size, warnings and errors, and summaries are emailed to your team
What SIINC backs up from Procore
- Core and administration
- Project inventory, Directory and permissions, WBS and reference data, Locations, Custom fields and workflows
- Documents and design
- Documents, Drawings, Specifications, Photos, Models and coordination
- Project management
- RFIs, Submittals, Correspondence, Emails, Meetings, Schedule tasks, Action plans, Forms, Inspections
- Field, safety and workforce
- Observations, Punch list, Incidents, Daily logs, Time and productivity, Equipment and materials
- Financial and commercial
- Bidding and preconstruction, Budget, Prime contracts, Commitments, Change events and RFQs, Change orders, Invoices and payment applications, Payments and direct costs, Resource management
- Audit and change history
- Audit and change history
Find Procore records again in the Procore Workbench
The Procore Workbench is a view over your backed-up Procore data, with a category for every component, a record inspector with fields, responses and attachments, version history and ZIP export. It reads from your own storage, so your team can search a closed project the way they remember it and download the files without a Procore login. When a record needs to go back into Procore, SIINC restores it into the same Procore account or a different one.
What you need to connect Procore
A verified company connection through the SIINC Procore integration, approved by an admin of the Procore account that owns the projects, and an Amazon S3 bucket or Azure Blob container in your own cloud account. SIINC captures what the connected Procore account can see, and nothing more. There is nothing to install, and setup takes under 30 minutes.
How SIINC compares to Procore Project Archive
Procore Project Archive is a one-off closeout export, and SIINC is a backup that keeps running. Many teams use both: Project Archive when an owner asks for a PDF package at handover, and SIINC to keep the working record in their own storage from the start of the job.
Project Archive is enough when you need one closeout or billing package for a single project and someone will download and file it within 30 days. SIINC is built for records that have to outlast the project, the Procore subscription and the people who ran the job. The full side-by-side table is on the SIINC vs Procore Project Archive page.
Who can back up a Procore project with SIINC?
Any company whose Procore account is a member of the project, subject to that account's permissions. SIINC backs up the projects your account is a member of and captures what the connected account is allowed to see, into storage your company owns.
That matters for subcontractors, trades and design consultants who work inside a head contractor's Procore. Your side of the record, such as RFIs, submittals and correspondence you were part of, can sit in your own Amazon S3 or Azure Blob Storage account, so the copy stays with you after your access to the project ends.
Sources
Procore backup questions
Procore backup questions
Not as part of closeout. Marking a Procore project inactive does not remove its data, and Procore Project Archive can still export from inactive projects. The risk is losing access, not deletion at handover. The Procore help pages cited here do not say how long project data is kept after a company's subscription ends, so treat a copy in your own storage as the record.
Yes. SIINC writes Procore backups into an Amazon S3 bucket in your own AWS account, in the region you choose. It can write to an Azure Blob Storage container instead. SIINC runs a write test before saving the storage credentials, and AWS bills you for storage at your own rates.
Yes. You pick the projects, then the components that matter for each one. Every component is a checkbox, so you can back up the records your contracts depend on and leave out heavy or rarely needed data.
Yes, for the term of your plan. Sync runs only mirror deletions if you turn that on, so an RFI, drawing or daily log deleted in Procore stays in your copy. File versions are captured too, so you can go back to the version before a change.
Not when it backs up. Backups only read from Procore through the official API and write to your own storage. SIINC writes into Procore only when you run a restore, which can put records back into the same Procore account or a different one. A Procore admin approves the SIINC connection for the company.
More on keeping Procore records
- Use caseProject closeoutKeep the full project record after closeout, when platform access ends within about 30 days.
- Use caseClaims and disputesThe daily logs, RFIs, mail and change orders behind variations, EOTs and defect claims, kept after access ends.
- Use caseRecords retentionKeep project records for as long as liability runs, without paying for old platform licences.
- Use caseDeletion and recoveryGet back a deleted or overwritten file or record, after the recycle bin and after access ends.
- Comparisonvs Procore Project ArchiveA closeout export someone runs by hand, or a backup that keeps running.
- GuideKeeping construction project records after completionWhich project records to keep after completion, why limitation periods make that a long time, and what to ask your lawyer.
- GuideProject closeout records checklist for Procore, Autodesk Forma, BIM 360 and AconexWhat to export or back up from Procore, Autodesk Forma, BIM 360 and Aconex before project access ends.
Start a trial workspace or book a demo and we will run the first backup with you.
