Upgrading cloud-shared Revit models via Autodesk Construction Cloud’s Cloud Model Upgrade tool can initially feel daunting. It often surfaces a flurry of errors and warnings, but the key insight is that most issues indicate pre-existing model “technical debt”, not bugs in Autodesk’s tool.
Understanding Technical Debt
Technical debt is a concept originally coined by software developer Ward Cunningham in 1992. It refers to the future cost incurred when development prioritizes speed or expediency over long-term quality. In the context of BIM, technical debt can manifest as poor modelling practices or model management, outdated process, shortcuts and workarounds, or suboptimal design decisions. These issues, if left unresolved, can complicate future work and maintenance, leading to increased effort and potential errors.
In other words, the upgrade process is exposing model elements that need cleanup or correction. With the right approach, project teams and BIM managers, even those less experienced with Revit, can systematically tackle these errors and successfully upgrade their projects.
The idea behind these posts is to replace the “Autodesk is broken” panic with a predictable process, so you see these errors not as random failures, but as an actionable to do list for model cleanup.
How Revit Cloud Model Upgrades Work
The ACC Cloud Model Upgrade function allows a Project Admin to upgrade all cloud-hosted Revit models in a project to a newer Revit version in one batch operation. Essentially, it automates what you’d do manually (opening each model in the new Revit release) but at the project level.
There’s also a “Test Upgrade” mode, which runs through the motions without saving the changes to the files, and produces a detailed Upgrade Report of any errors or warnings encountered. This report is gold. It tells you which models had problems and why, so you can address issues before doing the real upgrade. If no issues are found, you get a simple “All clear” message.
All or Nothing
An important and often misunderstood point is that the cloud upgrade treats the entire project as one job. If any model fails to upgrade, the process stops and no models are upgraded, meaning all files remain in the old version. One problematic model can block hundreds of others. Autodesk confirms that if a model “fails to upgrade, all models in the project remain in the prior release”. This is by design, to ensure data consistency, but it can be frustrating on large projects. A single misbehaving file might hold up an entire suite of models. This “one fails, all fail” behavior is likely why some teams tend to feel that the tool is broken. The actuality is that the tool is just stringent, after all, could you imagine if the tool upgraded most but not all of the models? It would be more disastrous than a report that tells you no. The implication of this is that you must resolve upgrade-stopping errors in failed models before the upgrade can complete.
Typical Workflow
Only a project admin can initiate the cloud upgrade. They go to Project Admin > Revit > Revit Cloud Model Upgrade, select the target version, and run either Test Upgrade (for a report) or the actual upgrade.
You should always run a test first. The upgrade can take a long time and should be done off-hours. During the run, users should avoid accessing the models. Autodesk’s notes point out that if a project is huge (2,500+ models), the tool won’t even enable. At that kind of scale, manual or scripted approaches are needed.
A common misconception is “the updater will magically fix my model”. In reality, the tool can auto-resolve only minor issues, for example, Revit will sometimes fix or ignore certain errors when upgrading, marking them as warnings, but anything substantial must be fixed by users.
Another misunderstanding is the error messages themselves, with people often finding them to be cryptic. In reality, these messages often point to specific issues within the model that need to be addressed. While the error messages can be challenging to interpret, they are designed to guide you toward the necessary fixes, directing you to which models and families are causing trouble.
Ultimately, ACC’s Project Updater is a powerful convenience. It provides the ability to upgrade dozens (or even hundreds) of Revit files at once, but it demands that every model be in good shape. It will halt for any serious issue, essentially saying: “Please fix this model’s issues (technical debt) before I proceed.”
Sometimes, dealing with these errors can feel a bit like you’re the Old Man Yelling at Cloud. Don’t let the frustration get the better of you!
The good news is the errors are usually predictable types. Next week, we’ll start looking at turning your upgrade failure messages into actionable next steps.
References
Project will not upgrade in Revit
Help | Upgrade Cloud Models | Autodesk
“An error occurred in family and was automatically resolved” when upgrading a file in Revit
No Comments