Autodesk Revit 2026 came out recently and Autodesk partners like Micrographics first to test new capabilities (and experience any bugs that might be present to report them to the developers). As such, we are the first to see the advantages and value the new software version’s capability.

As an introduction, and in context of working on the cloud, ACC Revit cloud models (workshared and non-workshared) are ACC project version specific and are not backwards compatible, but they can be upgraded en masse at the press of a button. This is what makes Revit cloud models preferable for us to manage the condition of models in a portfolio.

I like multitasking and putting together systems and so I wanted to upgrade my Autodesk Construction Cloud Project from 2025 to 2026. However, this is not a prudent action to take since, if there is any failure in any of the new software platforms, it could cause me a significant setback. So, I decided to bridge an ACC 2026 project team into an ACC 2025 project. The idea is that I constantly have a set of models that I keep one year ahead so I can test the AEC platforms as and when their new versions become available. I can then also test their interaction with an earlier version on the cloud.

Non-cloud Revit models do not have to conform to the version of the ACC project. They may be or earlier, similar or later versions. These models (regardless of their version) get incorporated into the federal project model in ACC Collaborate or ACC Collaborate Pro and are also available for clash detection in ACC Coordinate. When a cloud workshared model is shared in a package, it is no longer a cloud model. If you tried to open it in Revit on your hard drive, it is recognized as the “published version of the cloud model”. It is also in the version of the cloud model from which it was originally shared (in other words, it is a static model if nobody alters it).

When and ACC Project is upgraded:

• Cloud models are upgraded
• Package shared models are not upgraded.
• Package consumed models are not upgraded.
• Outgoing bridged shared models are not upgraded.
• Outgoing bridged shared consumed models are not upgraded.
• Files that are bridged into the project are not upgraded.

When a cloud model is shared in a package the copy that is shared is no longer a cloud model. Similarly, the copy of the shared model that is kept within each team’s consumed folder is also not a cloud model. This makes sense when considering BIM Level 2 Compliance and the preservation of the truth. Upgrading a model exposes the model to the risk of some data loss, so it should not be undertaken unless agreed by all stakeholders, and without archiving (please do archive shared models before upgrading the project to the new version).

The version of the shared model is in the same version in which it was created. Therefore, it would not be possible to link the shared Revit 2026 model into the Revit 2025 models directly once they have been consumed. However, if you were to share in IFC format, you could link the files to the earlier Revit. A Navisworks NWD is not the preferred option, and it is best to use the same versions as the Revit file into which it is to be linked.  

Importantly, the federated project model does interpret the later Revit model. So, a clash detection and a constructability review are on the cards.

In conclusion, allowing operators to run their own ACC 2026 projects to bridge into ACC 2025 projects is a definite option to consider. For so long as the risks are understood (Revit 2026 is not backwards compatible).

For those that manage portfolios of Revit Cloud models, keep in mind that only the cloud models are upgraded when you upgrade the project. If you want the rest of the system to operate without having to upgrade Revit models that are linked (non-cloud), then you need at least share packages for every team and consume for every team. Perhaps upgrading files that are either not Revit or specifically Revit cloud is best left for when the project is activated again. However, in my experience, once too much time has passed, this might have been left too late. Limiting the project to Revit is a good solution when looking at a typical residential or commercial office, but as soon as industrial designs are considered, then this is not an option, and if the digital twin design models need to be upgraded from year to year, then time and money must be invested to make it so.

If you need help adopting the AEC Collection or the Autodesk Construction Cloud in your practice or if you are looking to invest in hardware, please contact Micrographics so that we may be of assistance.