If you open Revit 2022 and your ACC project is missing, it’s not a sync issue. It’s a version lock.
This catches teams regularly: a project is started in Revit 2026 or 2025, then later the team needs to work in Revit 2022 or 2024 due to client requirements, consultant constraints, or existing deliverables. At that point, the project becomes partially unusable depending on the version.
This is not a bug. It’s how Autodesk Construction Cloud (ACC) is designed.
How ACC Handles Revit Versions (What’s Actually Happening)
ACC uses Revit Cloud Worksharing, which is backed by a version-specific cloud database schema.
When the first model is published using Collaborate in Cloud, the system:
- Creates a cloud model container
- Tags it permanently with that Revit version
- Structures the underlying database to match that version
That database cannot be interpreted by older versions of Revit.
There is no backward compatibility layer.
The “Locked Project” Reality
Once the first Cloud Workshared model is created:
- The ACC project is locked to that Revit version
- The project is only visible in that version’s Autodesk Projects interface
Example:
- Project started in Revit 2026
- Open Revit 2024 or 2022 → project does not appear
- No warning, no message — it’s simply not listed
This is where most teams lose time trying to troubleshoot something that is not fixable.
Why There Is No Downgrade
Revit is not backward compatible. That’s known.
What matters here is the cloud side:
- The cloud model database evolves every year
- New schema = new data structures, relationships, parameters
- Older versions cannot safely interpret newer data
That’s why:
- There is a Cloud Model Upgrade tool
- There is no downgrade tool
- Deleting models does not reliably reset the project version (see note below)
Once the project is initialized, the version tag remains.
The Core Problem Scenario
Typical situation:
- Team starts in Revit 2026 or 2025
- Later needs to align with:
- Client using Revit 2022
- Consultant locked to older version
- Existing model delivered in earlier version
At that point:
- You cannot initiate Cloud Worksharing in older versions inside that project
- You cannot “convert” the project
- You cannot make multiple Revit versions coexist as cloud models
The Solution: Navigating the Version Barrier
The “Clean Break” (Recommended)
If the project is still early:
Step 1: Create a new project in ACC Account Admin Step 2: Open the required version (e.g., Revit 2022 or 2024) Step 3: Initiate models using Collaborate in Cloud
Result:
- New project locked to the correct version
- Full compatibility across the team
- Stable collaboration environment
Archive the incorrect project to avoid confusion.
This is the only reliable solution.
The Hybrid Approach (Non-Workshared)
If you must keep everything in one ACC project:
- Upload models from other versions via:
- Autodesk Docs (web)
- Desktop Connector (v15.x or v16.x depending on environment)
These files will be:
- Stored as standard files
- Not cloud workshared
- Not multi-user editable in real time
Limitations:
- No worksharing
- No central model behavior
- No concurrent editing
This is storage, not collaboration.
Technical note:
- Desktop Connector v16.x (Revit 2025/2026 standard) uses a different file system structure than v15.x
- Mixing older Revit versions (e.g., 2022) with outdated Desktop Connector versions can introduce:
- Path length errors
- Sync failures
- Permission inconsistencies
This can make the hybrid workflow unstable if not aligned.
Interoperability Workarounds
If the newer model (e.g., 2026) is already the main model:
IFC Export
- Export older version → IFC
- Link IFC into newer Revit version
Pros:
- Geometry preserved Cons:
- No parametric intelligence
Rhino.Inside.Revit
- Use Rhino / Grasshopper to transfer geometry
Pros:
- Flexible Cons:
- Complex workflow
- Not suitable for most teams
CAD Link (Last Resort)
- Export to DWG
- Link into another version
Pros:
- Fast Cons:
- No BIM data
- Geometry only
Mid-Project Recovery (What You Can and Can’t Fix)
If the project is already active:
- You cannot change the version of the ACC project
- You cannot merge versions in cloud worksharing
You can only:
- Split into a new project
- Use interoperability workflows
- Freeze one version as reference
At this stage, it becomes damage control.
Multi-Company Coordination Impact
This issue becomes critical when:
- Architect works in Revit 2026
- Structural or MEP teams are in 2024 or 2022
- Contractor requires a fixed version
Consequences:
- Broken coordination workflows
- Clash detection inconsistencies
- Model duplication
- Increased reliance on IFC
From a BIM execution plan, this must be defined before project start.
ISO 19650 and Version Control
From an ISO 19650 perspective:
- Version alignment is part of the Common Data Environment (CDE) strategy
- ACC version locking directly affects:
- Information consistency
- Model federation
- Data exchange workflows
Failing to align versions early introduces risk across the entire delivery process.
What NOT to Do
- Do not try to delete models to reset version
- Do not expect ACC to restore compatibility
- Do not attempt to downgrade Revit files
- Do not mix cloud workshared models across versions
These approaches do not work in production.
Decision Guide (Quick Fix Path)
- Early project → Create new ACC project in correct version
- Mid project → Split + IFC / reference workflows
- Late project → Lock version and stop mixing workflows
Best Practice for BIM Managers
Before initiating any ACC project:
- Confirm contractual Revit version
- Align all stakeholders
- Validate consultant capabilities
- Document version in the BEP (BIM Execution Plan)
Once the first Collaborate in Cloud command is executed, the version is set.
If a mistake happens:
- Stop immediately
- Restart correctly
Do not try to force compatibility later.
FAQ: Revit Versions and ACC
Why can’t I see my Revit 2022 project in Revit 2026?
Starting from Revit 2023.1 and later (2024, 2025, 2026), you can enable:
- File → Options → Cloud Model → Show projects in all Revit software versions
The project will appear:
- Grayed out
- Not accessible
This is visibility only, not compatibility.
Can I have both 2022 and 2026 models in the same ACC project?
Only as non-workshared files in Docs.
You cannot have:
- Multiple versions as Cloud Workshared models
ACC supports one Revit version per project for cloud worksharing.
What happens if I delete all models from the project?
In standard conditions:
- The project remains tagged to the original version
- The version lock stays in place
Exception (not reliable):
- In rare cases, if all cloud models are deleted and the Trash/Deleted Items is fully purged, the project may release its version lock
- This often requires backend cleanup or Autodesk support
This method is not reliable for production workflows.
Does the Revit Cloud Model Upgrade tool work in reverse?
No.
- It upgrades models forward (e.g., 2023 → 2026)
- There is no downgrade capability
Is there a way to link a 2022 model into a 2026 project?
Not directly.
Options:
- Open in newer Revit → upgrade → link
- Export to IFC → link IFC
There is no live cross-version linking.
Can Desktop Connector solve this issue?
No.
It allows file access, not version compatibility.
Also note:
- Version mismatch between Revit and Desktop Connector (v15 vs v16) can introduce additional issues
- It does not enable cloud worksharing across versions
Is this different between BIM 360 and ACC?
No.
- Same cloud worksharing logic
- Same version locking behavior
ACC is the continuation of BIM 360.
Can Autodesk change this behavior?
Unlikely.
It would require:
- Backward-compatible cloud schemas
- Cross-version data translation
That would introduce instability in production environments.
Final Takeaway
ACC version conflicts are not technical glitches. They are structural constraints.
The first Cloud Workshared model defines the project version permanently.
Everything else follows from that.