Not on its own. A sync is built to keep two places the same, so changes and mistakes in one can reach the other. A backup is a separate copy that keeps earlier versions and deleted records.
A SharePoint sync is a mirror. A backup keeps what the mirror loses.
Connectors such as ProjectReady, HingePoint ProConnector, SyncEzy and odrive copy Procore or Autodesk Forma content into Microsoft SharePoint, Teams or Box, and several describe this as backup. It is a good way to work on project files from Microsoft 365 every day. But a sync is built to keep two places the same, so the copy changes whenever the source does. SIINC keeps a separate, scheduled copy of the project record in Amazon S3 or Azure Blob Storage you own.
- Compared
- SharePoint and Box sync and SIINC
- Side by side
- 9 capabilities
- Sources cited
- 6, linked at the table
- Facts checked
- 27 Oct 2026
SharePoint and Box sync or SIINC: the short answer
Syncing Procore or Autodesk Forma to SharePoint, Teams or Box gives you a working mirror of project files, while SIINC gives you a backup. A mirror is built to carry changes across, which HingePoint describes as mirroring the exact actions taken with documents in one system to the other. SIINC writes scheduled copies into Amazon S3 or Azure Blob Storage you own, keeps deleted records for the term of your plan, covers RFIs, daily logs, mail and financial records as well as documents, and restores records back into the platform when you run a restore.
Last reviewed
Sync to SharePoint, Teams or Box and SIINC, side by side
What each one does with your project record. Coral marks where the record is at risk.
| Capability | Sync to SharePoint, Teams or Box | SIINC |
|---|---|---|
| Built for | Working on Procore or Autodesk Forma files from Microsoft 365 or Box, kept in step with the source | Keeping an independent, scheduled copy of the project record |
| Direction | Often two-way. HingePoint and odrive sync documents in both directions | Backups are one way. They only read from the platform and write to your storage. SIINC writes back into the platform only when you run a restore |
| When something is deleted | Changes are mirrored to the other side. The vendor pages we checked do not say how deletions are handled | Kept for the term of your plan. Sync runs only mirror deletions if you turn that on, and a deleted record can be restored into the platform |
| What is copied | Mostly documents and folders. HingePoint syncs document folders, files and metadata. SyncEzy also sends RFIs and submittals one way to Box | Selectable modules, from Procore daily logs, change orders and invoices to Autodesk issues and Aconex mail and workflows |
| Platforms | Procore, Autodesk Forma or both, depending on the connector | Procore, Autodesk Forma and BIM 360, and Oracle Aconex |
| Where the copy lives | Your Microsoft 365 tenant or Box account, next to everyday files | Your S3 or Azure Blob storage, under your own retention and immutability policies |
| Setup | Varies. HingePoint installs and configures the integration for you. odrive runs as a desktop app | A hosted service. Authorise the platform, add storage credentials and pick projects, in under 30 minutes |
| Finding a record later | In SharePoint, Teams or Box, with your other files | The Procore Workbench, Autodesk Portal and Aconex Portal, by project, module and record |
| Proof of what was captured | Not described on the vendor pages we checked | Execution history for every run, a checksum for every file, emailed summaries and an exportable client audit log |
When is Sync to SharePoint, Teams or Box enough?
- Your team works in Microsoft 365 or Box and wants current Procore or Autodesk Forma documents there every day.
- You need two-way sync, so files added in SharePoint reach Procore. HingePoint sells exactly that.
- Your records team already governs everything in SharePoint, and documents and drawings are what you need.
- You want the vendor to install and configure the connection for you.
When do you need SIINC instead of Sync to SharePoint, Teams or Box?
- You need to get back a file or record from before someone deleted or overwrote it.
- The copy must be separate from the system people work in every day, so a mistake there does not reach it.
- You need RFIs, submittals, daily logs, mail and financial records, not just the documents folder.
- IT wants the copy in AWS or Azure storage, under the retention and immutability rules it already runs, including S3 Object Lock or Azure immutable storage.
- You run more than one platform and want one backup across Procore, Autodesk Forma and BIM 360, and Oracle Aconex.
Using Sync to SharePoint, Teams or Box and SIINC together
Sync and backup answer different questions, so many teams will run both. Keep the SharePoint or Box sync for everyday access to current documents, and let SIINC keep scheduled copies of the full record in your own storage. If a sync carries a mistake into SharePoint, the version from before it is still in your bucket.
SharePoint, Teams and Box sync vs SIINC questions
SharePoint, Teams and Box sync vs SIINC questions
93 days. Microsoft keeps deleted SharePoint items in the recycle bin for 93 days from the time they are deleted, then deletes them permanently.
Yes, several connectors do. ProjectReady, HingePoint and odrive all copy Procore content into SharePoint. SIINC takes a different route and writes backups to Amazon S3 or Azure Blob Storage in your own account.
No. They do different jobs. The connector keeps current files where your team works, and SIINC keeps an independent copy of the whole record, including what was deleted, backed up hourly as standard.
More construction backup comparisons
- vs Procore Project ArchiveA closeout export someone runs by hand, or a backup that keeps running.
- vs Autodesk Replication Tool and BridgeAutodesk's own tools copy files. SIINC backs up the project and moves it whole.
- vs Oracle Aconex ArchivesAn archive you order from Oracle, or a backup in storage you own.
Start a trial workspace or book a demo and we will run the first backup with you.