You sync metadata between common data environments (CDEs) and keep ISO 19650 fields correct by mapping each platform's fields and values once, then letting a CDE integration apply that mapping to every file it moves. CDE Sync™ translates naming, status, revision and classification fields between platform schemas automatically, so a document carries the right ISO 19650 metadata wherever it lands.
Why metadata breaks between CDEs
ISO 19650 gives projects a common language for information management, including naming conventions, status codes and revision rules. Each CDE implements those ideas differently. Autodesk Forma uses custom attributes, Bentley ProjectWise uses environment attributes, Oracle Aconex uses register fields, and SharePoint uses metadata columns. Even when two platforms both follow ISO 19650, their field names, picklists and formats rarely match.
When files move by hand, metadata is re-keyed at every step. A status code is typed slightly differently, a revision is incremented on one side but not the other, or a field is left blank because the receiving platform made it optional. Over a project those small errors accumulate until the register no longer matches the files. Our article on ISO 19650 metadata compliance across multiple CDEs explains what different tools support.
What correct metadata sync requires
Correct sync rests on three things. The first is a field mapping that pairs each source field with its target. The second is a value mapping, so a status of "S2" in one platform becomes the equivalent picklist value in another. The third is consistent version handling, so revisions stay in the same order on both sides. CDE Sync™ handles all three, including dynamic mapping across large numbers of fields where client requirements are extensive.
How to sync ISO 19650 metadata, step by step
Collect the information requirements for the project, including the client's naming convention, status codes and mandatory fields.
List the metadata fields each connected CDE uses, with their names, types and allowed values.
Build a mapping table that pairs fields and values across platforms, and agree it with each party's document controller.
Enter the mapping in the CDE Sync™ wizard when you connect the platforms.
Decide how to handle mismatches, such as a required field with no source value, and who is notified.
Run a test sync on a representative sample and check every field on the receiving side.
Review the audit log regularly and update the mapping when a party changes its requirements.
Common pitfalls to avoid
Most metadata problems come from assumptions. Teams assume two platforms use the same status codes because both say they follow ISO 19650, and only discover the difference when submissions are rejected. Others map fields but forget values, so a status arrives in the right field with the wrong code. Some leave mapping until late, when thousands of documents already need correcting. Agreeing the mapping table at project start, testing it on real documents and treating it as a controlled document that changes only with agreement avoids most of these issues.
It also helps to keep the mapping in one place. When each party maintains its own spreadsheet of field equivalents, they drift apart. A single configuration in CDE Sync™ becomes the reference everyone can point to.
When requirements change mid-project
Information requirements rarely stay fixed. A client adds a mandatory field, a new subcontractor joins with its own codes, or a revision scheme is clarified after the first submissions. With manual transfers, each change means retraining people and correcting documents already sent. With a mapped sync, the change is made once in the configuration and applies to every file from that point on. Where earlier documents need correcting, the audit log shows exactly which ones were affected, so the fix can be targeted. Keeping a dated record of each mapping change also helps when auditors ask why a field changed during the project.
Security and audit
Every metadata action is logged, so you can show what value was written, when and by which rule. CDE Sync™ streams files directly between platforms 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.
ISO 19650 metadata and the Utopiaverse™
Consistent metadata is what makes the Utopiaverse™ useful. The Utopiaverse™ maps metadata from every CDE into one schema aligned to ISO 19650 in your own Azure. CDE Sync™ keeps live platforms aligned, CDE Backup™ keeps an independent copy, CDE Migrate™ carries metadata across platform changes and CDE Archive™ captures completed projects. AI Insights then searches the whole record and filters by the fields you trust. See also How Do I Connect Oracle Aconex and Autodesk Forma? for a register mapping example.
See metadata mapping in the monthly live demo, or talk to the team about your information requirements.
