You connect Oracle Aconex and Asite with a CDE integration that moves documents, revisions and metadata between the two registers in the direction each party needs. CDE Sync™ links both platforms through dedicated accounts, maps Asite attributes to Aconex fields and back, and logs every transfer, so each organisation keeps working in its own platform while both registers stay aligned.
Why two registers meet on one project
Aconex and Asite are both built around controlled document registers, workflows and transmittals. That similarity is exactly why they collide. A contractor who has standardised on Asite wins work for an owner who mandates Aconex, or the reverse. Neither party will give up its own platform, because each has its own processes, reporting and contractual record built around it.
Without a connection, the contractor's document controllers export from one register, rename files to the other party's numbering scheme, complete a second set of mandatory fields and upload. When the receiving party issues comments or a new status, the result is carried back by hand. Two registers that should agree slowly drift apart, and disputes later turn on which one is right.
What carries across between Aconex and Asite
CDE Sync™ moves files with their version history and translates metadata between the two schemas. Document number, revision, status, discipline and document type are mapped so each register receives values it accepts. Picklist values that differ between the platforms, such as status codes, are translated rule by rule. Every action appears in the audit log, which gives both parties a shared account of what moved and when.
The Oracle Aconex and Asite integration pages describe each connector in more detail.
How to connect Aconex and Asite, step by step
Agree which party submits, which receives, and which document types flow in each direction.
Collect both register configurations, including mandatory fields, picklists and numbering rules.
Request an Aconex integration user and an Asite service account from each administrator.
Connect both platforms in the CDE Sync™ wizard and select the Asite folders and Aconex document types.
Map fields and status codes between the registers, and decide how superseded revisions appear.
Run a test exchange on a handful of documents and check both registers side by side.
Switch on the schedule and agree who monitors failed transfers.
Translating status codes and workflows
The hardest part of connecting two registers is usually status. Each platform has its own codes for documents that are work in progress, issued for review, approved or superseded, and each organisation configures them differently. A single mapping table, agreed by both document controllers, settles which status in one register triggers a transfer and what status the document should carry on arrival.
Workflows themselves stay in each platform. Review and approval steps in Asite remain Asite steps, and Aconex workflows remain Aconex workflows. CDE Sync™ moves the documents and their outcomes between them, which keeps each party's process intact while the records agree. Our article on automating submissions and transmittals covers this pattern further.
Running the connection day to day is mostly about exceptions. If a document fails a mandatory field rule in the receiving register, it is reported rather than silently dropped, and the document controller fixes the source record so the next run succeeds. Because both registers draw from the same mapping table, a change to the client's picklists is made once in CDE Sync™ and applies to every later transfer, which saves both teams from updating spreadsheets of rules by hand. Over a long project, that single point of control is what keeps the two registers in agreement.
Security and data residency
Projects that use two registers often span countries, so where data is processed matters. CDE Sync™ streams files directly between Aconex and Asite without storing them, encrypts data in transit and processes it in the Azure region you choose. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.
Aconex, Asite and the Utopiaverse™
An Aconex to Asite connection is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Sync™ keeps both registers aligned, CDE Backup™ keeps an independent copy in your own Azure, CDE Migrate™ moves projects onto or off either platform, and CDE Archive™ captures the record at completion. AI Insights searches both registers together, with answers that cite the source documents. See also How Do I Connect Asite and Autodesk Forma? and How Do I Connect Oracle Aconex and SharePoint?
See Aconex and Asite connected in the monthly live demo, or talk to the team about your registers.
