You connect Oracle Aconex and Microsoft SharePoint with an integration that copies documents and register metadata between an Aconex project and SharePoint libraries on a schedule. CDE Sync™ handles the connection without code, maps Aconex register fields to SharePoint columns, keeps revisions in order and records every transfer.
Why Aconex content needs to reach SharePoint
Aconex is often the controlled platform for a project, holding documents, correspondence and submissions. SharePoint is where an organisation keeps its own records and where most staff do their daily work. Commercial, legal, operations and asset teams all need project documents, but few of them work in Aconex, and some organisations limit Aconex access to project staff.
Without an integration, people export from Aconex and upload into SharePoint by hand, or rely on emailed copies. Metadata is lost along the way, and SharePoint ends up with an incomplete or outdated picture of the project.
What the integration carries
CDE Sync™ moves documents with their revision history and maps Aconex register fields, such as document number, revision, status, discipline and type, into SharePoint metadata columns. You choose the SharePoint folder structure, for example by discipline or document type, so people can find content in a familiar layout.
Most organisations run this one way, publishing approved documents into SharePoint. Two-way connections are also possible, so documents drafted in SharePoint can be lodged in Aconex with the right register fields completed.
How to connect Aconex and SharePoint, step by step
Decide which Aconex documents should reach SharePoint and who will use them.
Set up the SharePoint site and libraries with columns for the Aconex register fields you want to keep.
Request an Aconex integration user from the project administrator and a SharePoint service account from IT.
Connect both platforms in the CDE Sync™ wizard.
Select the Aconex document types and target libraries, then map register fields to columns.
Run a test, check revisions and metadata in SharePoint, then set the schedule.
Bringing correspondence and documents together
Many organisations want their SharePoint copy to follow the way their own staff already work. That usually means grouping documents by project, then by discipline or document type, with columns for document number, revision, status and the date it was issued. Keeping column names close to the Aconex register field names helps people who move between the two systems. It is also worth deciding early whether superseded revisions should stay visible in SharePoint or be kept in version history only. CDE Sync™ supports either approach, because the structure and the version handling are set in the wizard. A short pilot with the people who will use the SharePoint copy confirms the layout before it is rolled out across every Aconex project, and it surfaces any missing columns or naming issues while they are still easy to fix.
Using SharePoint as a long-term record
Some organisations connect Aconex to SharePoint so they hold their own copy of project documents through delivery, not only at the end. That copy stays inside the organisation's Microsoft 365 environment under its own retention policies. For a full, independent copy of files, versions and metadata on a schedule you control, CDE Backup™ keeps the record in your own Azure tenancy. Our article What Is CDE Backup™? explains the difference.
Security and control
CDE Sync™ streams files directly from Aconex to SharePoint without storing them. Data is encrypted in transit and processed in the Azure region you choose. Each platform keeps its own permissions, and only the document types you configure are moved. Utopia Digital holds SOC 2 Type II and Cyber Essentials, with the detail on the Security Trust Portal.
Aconex, SharePoint and the Utopiaverse™
An Aconex to SharePoint connection is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Sync™ keeps systems aligned, CDE Backup™ keeps an independent copy in your own Azure, CDE Migrate™ handles platform changes and CDE Archive™ captures the record at completion. AI Insights then searches Aconex and SharePoint content together, with answers that cite the source documents. The Aconex and SharePoint integration pages have more, and How Do I Connect Aconex and ProjectWise? covers another common pairing.
See it running in the monthly live demo, or talk to the team about your platforms.
