Short answer: yes, but not as a live Revit model. BricsCAD BIM V26.2 on Windows supports direct import of Revit 2026 RVT and RFA files. The content is translated into BricsCAD geometry and BIM data rather than remaining a native Revit model. IFC is also an important exchange route, particularly where the model will be used repeatedly for multidisciplinary coordination.
When people ask to open RVT in BricsCAD, they usually want one of three things:
BricsCAD can also support the first case in a translated sense. Imported Revit elements can become BricsCAD 3D solids or block references that can be manipulated in BricsCAD. It does not provide live Revit parametrics, native Revit family behaviour, or a full native Revit round trip.
Direct Revit 2026 import requires BricsCAD BIM V26.2 on Windows. BricsCAD BIM V26.1 supports Revit files only through Revit 2025, while V26.2 supports Revit 2015 through 2026.
In BricsCAD BIM V26.2, RVT import converts Revit content into BricsCAD 3D solids and block references while also importing substantial BIM information, including classification, spatial information, compositions and materials. It is still a translation and is not the same as native Revit authoring.
For UK projects applying information management according to the ISO 19650 series, IFC is a well supported open exchange format for multidisciplinary BIM interoperability. The required exchange format should be defined by the project’s information requirements, methods and delivery arrangements rather than assumed to be the same for every project.
Use:
For recurring coordination, IFC has a documented advantage because BricsCAD can attach an IFC model as an underlay and update it when a new IFC file is issued. Direct RVT import remains a valid route when the BricsCAD team needs translated geometry and BIM information inside the drawing.
If COBie is required, confirm the output view/config and test early with a model checker.
Use it for:
Use RVT import when you need Revit model geometry translated into BricsCAD solids and blocks together with supported BIM information. Use RFA import when you need Revit family geometry brought into BricsCAD as separate 3D solids. These routes can be used for context, selected model content and downstream work inside BricsCAD.
Use it for:
Use it for:
You can often bring across:
You should not expect native Revit parametric behaviour, native Revit family constraints or a live Revit worksharing environment after translation. Revit worksets can, however, be used to filter an RVT import, and imported Revit 3D views become BricsCAD Named Views. Project specific annotations, linked content and specialist analytical information should be tested before they are relied upon.
In short, BricsCAD gets useful model data, but not full Revit behavior. That is the core of BricsCAD vs Revit interoperability.
Use Shared Coordinates in Revit IFC export when the project needs it.
Appropriate IFC class mapping helps ensure elements are assigned to suitable IFC classes and can reduce unnecessary use of generic proxy classes. It does not guarantee that no proxy entities will appear.
Check shared params and property sets before you send the file.
Too much detail makes files slow. Use the right level of detail.
This is a suitable mixed team workflow where IFC has been agreed as the project exchange format. Where editable translated Revit geometry is required instead, BricsCAD BIM V26.2 also supports direct Revit 2026 RVT import.
Revit provides native parametric modelling, family based content, model documentation, views, sheets, parameters and discipline specific modelling tools.
BricsCAD BIM supports direct editing of BIM solids, RVT and RFA import, and IFC based information exchange. Its IFC4 Architectural Reference Exchange export has also received buildingSMART certification.
So BricsCAD is a good fit for some jobs, but it is not a full Revit clone.
Goal | Recommended path
Bring a Revit 2026 model into BricsCAD as translated editable geometry | Direct RVT import in BricsCAD BIM V26.2 on Windows
Use a repeatedly updated consultant model for coordination | IFC underlay
Edit 2D outputs in DWG | Export the required Revit sheet or view to DWG and use it in BricsCAD
Preserve native Revit family and parametric behaviour | Continue authoring that content in Revit
Validate direct RVT import | Pilot using the exact application versions and representative project content
Can BricsCAD import Revit 2026 files? Yes. BricsCAD BIM V26.2 on Windows supports direct Revit 2026 RVT import. Direct RVT import is appropriate when translated BricsCAD geometry and BIM information are required. IFC is particularly useful for open model exchange and recurring coordination, including an updateable IFC underlay workflow. Neither route provides a live native Revit round trip.
Can BricsCAD directly open and edit a Revit 2026 RVT model?
BricsCAD BIM V26.2 on Windows can open or import a Revit 2026 RVT file, but it does not edit the file as a live native Revit model. Revit content is translated into BricsCAD geometry and BIM information, and supported solids can then be manipulated in BricsCAD.
What is the most reliable way to move Revit 2026 content into BricsCAD?
Export IFC from Revit 2026 and import that file into BricsCAD BIM. Use Shared Coordinates and good class mapping.
When should I use RVT or RFA import, IFC, or DWG?
Use RVT when you need Revit project content translated into editable BricsCAD geometry with supported BIM information. Use RFA when you need Revit family geometry imported into BricsCAD. Use IFC for open BIM model exchange and coordination, and use DWG where the required exchange is primarily CAD geometry or 2D documentation.
What data often fails to transfer well?
Do not assume that native Revit parametric and constraint behaviour will survive the translation. Octave documents some Revit system families becoming 3D solids and constrained or loadable families becoming block references. Worksets can be used as import filters, and Revit 3D views are imported as BricsCAD Named Views. Other project specific information should be tested before it is relied upon.
How do I avoid bad alignment or data loss?
To reduce alignment and information transfer risk, agree and test the project coordinate basis, configure the required IFC classifications and property sets where IFC is being used, and validate a representative exchange before relying on it in production.
