You connect two Oracle Aconex projects or instances with a same-platform CDE integration that keeps chosen documents, revisions and register metadata aligned between them, or with a migration that moves content from one to the other. CDE Sync™ handles ongoing Aconex to Aconex sync and CDE Migrate™ handles one-off moves, both preserving version history and register fields.
Why two Aconex registers need to share
Aconex is widely used by owners and principals, so it is common for related work to sit in more than one Aconex project. A programme may be split into separate projects for each package or stage. An owner and a principal contractor may each run their own Aconex project for the same works. Some organisations operate in different Aconex instances for different regions, and information has to move between them.
Each register is usually configured differently, with its own numbering rules, mandatory fields and status codes. Without a connection, document controllers download from one register, rename files, complete the other register's fields and upload. Version history does not carry across, and the two registers slowly disagree.
What carries across between Aconex registers
CDE Sync™ connects two instances of the same platform as easily as two different ones. It moves documents with their version history between nominated document types and maps register fields where the two configurations differ, including numbering, status and discipline values. You choose one-way or two-way rules, and every transfer is logged for audit.
The Oracle Aconex integration page describes the connector.
How to connect two Aconex registers, step by step
Decide whether you need an ongoing sync or a one-off migration.
Agree which document types move between the two registers, and in which direction.
Collect both register configurations, including mandatory fields, picklists and numbering rules.
Request an Aconex integration user for each project or instance from its administrator.
Connect both in the CDE Sync™ wizard and map register fields and status codes.
Run a test on a handful of documents and compare both registers side by side.
Switch on the schedule, or complete the migration and confirm results with a validation report.
Programmes, stages and handover between registers
Large programmes often move between stages, such as planning, delivery and operations, with a different Aconex project or a different organisation responsible at each stage. Information created in one register is needed in the next. A sync keeps shared reference documents aligned while both stages are active, and a migration moves the full record when one stage closes.
Owner and contractor registers follow a similar pattern. A principal contractor may keep its own Aconex project for internal control while submitting to the owner's. Mapping one register to the other means submissions arrive with the owner's fields complete, and responses can flow back. Our article on automating submissions and transmittals covers this pattern in more depth.
Migrations between registers need enough notice before the target date to plan, test and validate properly. CDE Migrate™ carries versions, register fields and audit trails, so the receiving organisation inherits a record it can rely on.
Running the connection is mostly about exceptions. A document that fails a mandatory field rule in the receiving register 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 picklists or status codes is made once and applies to every later transfer. That single point of control keeps the two registers in agreement through the life of the programme.
Security and data residency
Moving data between Aconex instances in different regions raises residency questions. CDE Sync™ streams files 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 to Aconex and the Utopiaverse™
An Aconex to Aconex 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 the record between registers when a stage closes, 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 Oracle Aconex and Asite? and How Do I Connect Two Autodesk Forma Hubs or Regions?
See two Aconex registers connected in the monthly live demo, or talk to the team about your programme.
