Introduction

Building Information Modeling (BIM) has transformed the architecture, engineering, and construction (AEC) industry, and Autodesk Revit stands as one of the most widely adopted authoring tools. However, few projects rely solely on a single software platform. Architects, structural engineers, MEP consultants, and contractors often use specialized tools for analysis, coordination, or fabrication. Seamless data exchange between Revit and other BIM software is therefore critical to maintaining data integrity, reducing rework, and ensuring that all stakeholders work from a single source of truth. Poorly managed exchanges can lead to geometry errors, lost parameters, or mismatched metadata, ultimately causing delays and cost overruns.

This article provides a comprehensive set of best practices for exchanging Revit data with other BIM platforms. From understanding file formats to optimizing export and import workflows, we cover actionable strategies that help teams collaborate effectively while preserving the richness of the BIM model. Whether you are exchanging data with ArchiCAD, Tekla Structures, Trimble SysQue, or a cloud-based Common Data Environment (CDE), these guidelines will help you achieve reliable interoperability.

Understanding Compatible Data Formats

The foundation of any successful data exchange is choosing the right format. Revit natively saves in the RVT format, but this is not universally readable. To share data with other tools, Revit can export to multiple formats, each with its own strengths and limitations. Understanding these options helps you select the best approach for each collaboration scenario.

Industry Foundation Classes (IFC)

IFC is the open, neutral standard for BIM data exchange, developed by buildingSMART International. It is supported by nearly all major BIM platforms and is the preferred format for exchanging full BIM models. IFC captures geometry, spatial structure, element relationships, and property sets. When properly configured, IFC can preserve a high level of semantic information. However, the quality of IFC export depends heavily on the mapping settings used in Revit. For example, Revit categories must be correctly mapped to IFC entities, and user-defined parameter sets need to be included in the export scope. Always test your IFC export with a subset of the model before full deployment.

DWG and DXF (AutoCAD)

While primarily used for 2D documentation, DWG and DXF formats can carry 3D geometry. They are useful for sharing floor plans, sections, or partial 3D views with teams that use AutoCAD or other CAD software. However, these formats lose BIM intelligence (parameters, classification, material properties). Use them only for geometric or drawing exchanges, not for data-rich BIM workflows.

COBie (Construction Operations Building Information Exchange)

COBie is a spreadsheet-based format (often in .xlsx or .ifcXML) focused on asset information rather than geometry. It is ideal for facilities management and handover requirements. Revit can export COBie data through built-in tools or third-party plugins. Ensure that your model contains the required properties (e.g., space types, equipment names) before exporting. COBie is also used to validate that the BIM model meets employer’s information requirements (EIR).

For energy analysis, gbXML is the standard format for exporting thermal zones and building geometry to analysis tools like IES VE or EnergyPlus. Revit can also expose its database via ODBC, allowing external applications to query element data. Some BIM software, such as Navisworks and Revit Live, can natively link to RVT files—no export required. Always prefer direct linking when the target tool supports it, as this retains the most current data without intermediate files.

Best Practices for Data Export from Revit

Exporting data from Revit is not a simple “save as” operation. Small misconfigurations can break data integrity. The following practices will help you produce clean, reliable export files.

1. Use IFC with Proper Mapping and Setup

IFC is the most common export format for interoperability. Before exporting, go to the IFC Export Settings dialog (File > Export > IFC) and review these key options:

  • Phase: Select the correct project phase (New Construction, Existing, etc.) to avoid exporting elements from all phases.
  • Export base quantities: Enable this to include standard IFC quantities (area, volume, width) for building elements.
  • Property Sets: Choose “Export Revit property sets” to map Revit parameters to IFC property sets. You can also define custom property set mappings using the IFC Parameter Mapping tool.
  • Class mapping: Ensure that Revit categories are mapped to appropriate IFC classes (e.g., IfcWall, IfcDoor, IfcColumn). Mismapped classes can break model structure in receiving applications.

Use the IFC Exporter for Revit (a free plugin from Autodesk on the Autodesk App Store) for more advanced control, including support for IFC2x3 and IFC4, and enhanced mapping capabilities.

2. Filter Exported Elements

Exporting the entire model may create large, unwieldy files that slow down the receiving application. Use worksets, design options, or view filters to export only the relevant parts. For example, if you are sharing only structural elements, create a filtered view that hides architectural and MEP elements, then export that view to IFC or DWG. In Revit’s export settings, you can also specify which elements to include by selecting “Export only elements in view” and choosing the appropriate view.

3. Preserve Geometry and Coordinate Systems

Coordinate confusion is a common source of errors. Always verify that the base point, survey point, and project north are set correctly in Revit. For IFC export, choose “Shared coordinates” under the “Coordinate system” option to maintain real-world positioning. If importing to software that does not support shared coordinates, consider exporting in the project internal coordinate system and document the offset separately.

For geometry, use the “Triangulation tolerance” setting to balance file size and accuracy. A smaller tolerance produces more tessellated faces but larger files. A value between 0.5 and 1 mm is usually sufficient for architectural collaboration. For structural steel connections or complex geometry, you may need a higher precision—test with your target software.

4. Document Your Export Configuration

Team consistency is key. Create a standard IFC export template (.ifcTxT) that stores all your preferred settings. Share this file across the project team and store it in the project’s Common Data Environment (CDE). When exporting, each team member uses the same template, ensuring uniformity. Also, document any manual parameter mappings or custom property sets in a shared spreadsheet or wiki.

Importing Revit Data into Other BIM Software

Importing data from Revit into other tools requires careful validation. The following practices will help you detect and resolve issues early.

1. Check Compatibility and Version

Before importing, verify that the receiving software supports the exact IFC version (e.g., IFC2x3 or IFC4) and schema used during export. Some BIM applications (like older versions of Tekla or ArchiCAD) have limited support for IFC4. In such cases, export using IFC2x3 CV 2.0 (Coordination View) as a fallback. If using DWG, ensure the AutoCAD version matches (e.g., AutoCAD 2018 format for compatibility with most 3D software).

2. Validate Imported Geometry and Data

After importing, perform a thorough check:

  • Geometry: Look for missing surfaces, inverted normals, or orphaned elements. Rotate the model and inspect intersections.
  • Property Sets: Confirm that custom parameters (e.g., fire rating, manufacturer) are present as property sets. If they are missing, the IFC export mapping might need adjustment.
  • Element Relationships: In some tools, spatial containment (e.g., walls in a room) may be lost. This is especially important for quantity takeoffs.

Use the import log (if available) to identify elements that failed conversion. For IFC, many BIM software provide an “IFC checker” tool (e.g., Solibri Model Checker, BIMcollab, or the free IFC File Analyzer).

3. Resolve Conflicts and Re-synchronize

If you detect conflicts—such as overlapping geometry or inconsistent classification—communicate with the Revit author. Do not attempt to fix the import by modifying the model manually in the receiving software, as those changes will be lost when the next export is imported. Instead, adjust the export settings or clean up the source Revit model and re-export. Changes should always flow from the source model to maintain a single point of truth.

4. Use Import Templates and Presets

Just as you standardize export settings, create import presets in the receiving software. For example, in Navisworks, you can create an “RVT” file reader configuration that pre-defines view settings, conversion parameters, and model coordination settings. This ensures every import is consistent and reduces manual setup time.

Collaborative Workflow Strategies

Data exchange is not a one-time event; it is a continuous process throughout the project lifecycle. The following strategies improve long-term collaboration.

1. Develop a BIM Execution Plan (BEP) for Interoperability

A BEP should define how data will be exchanged between parties. Specify the file formats, frequency of exchange, responsibility for export/import, and a process for resolving errors. Include a matrix of which software tools are used by each discipline and the mapping of elements. For example, “Structural Revit model exports to IFC every Monday for use in Tekla; Tekla exports back to IFC on Thursdays for clash detection in Navisworks.” This clarity prevents misunderstandings.

2. Use a Common Data Environment (CDE)

Store all exchange files in a shared repository accessible to all project participants. Cloud-based platforms like Autodesk BIM 360, Trimble Connect, or SharePoint allow role-based access and version control. Ensure that each file is clearly named with a standard convention (e.g., “Project_Revit_Structural_v03.ifc”). Avoid sending files via email—use links from the CDE to maintain a single version.

3. Implement Version Control and Model Comparison

When exchanging models frequently, it is easy to lose track of changes. Use version control tools (like Git for IFC, or built-in versioning in CDEs) to track revisions. Before importing, compare the latest export against the previous import to see what has changed. Tools like BIMcollab or Solibri can highlight differences in geometry and parameters. This helps teams identify unintended changes.

4. Regularly Update Software and Plugins

Both Revit and the receiving software constantly improve their interoperability features. For instance, Autodesk frequently updates the IFC exporter plugin, and other vendors improve their IFC importers. Subscribe to release notes and update your project’s software versions at logical milestones (e.g., after a phase completion). Test the new version in a sandbox project before rolling it out to active projects.

Advanced Techniques: Automation and Customization

For large projects or frequent exchanges, manual export/import can be error-prone. Automation can save time and ensure consistency.

Using Dynamo for Custom Export Workflows

Dynamo, the visual programming environment for Revit, can automate repetitive export tasks. For example, you can write a script that exports each workset as a separate IFC file, or that exports to COBie with custom property mappings. Dynamo packages such as “Rhynamo” or “Uniclass Utilities” extend these capabilities. A Dynamo graph can also validate that the export settings are correct before running the export, reducing human error.

API Integration with Other Tools

Some organizations develop custom integrations using the Revit API and the target software’s API (e.g., Tekla API). These integrations can directly read Revit elements and create equivalent objects in the target software without intermediate files. While this approach requires development effort, it offers near-perfect data fidelity. For example, Speckle is an open-source data platform that enables real-time streaming of BIM data between Revit, Rhino, Grasshopper, and other tools, bypassing file-based exchange entirely.

Special Considerations for Different Disciplines

The best practices above apply broadly, but specific disciplines have unique needs.

Structural Engineering: Tekla and Revit

When exchanging between Revit and Tekla Structures, IFC is often used but can lose steel connection details and bolt groups. Many teams prefer direct links like the Tekla Model Sharing or the Tekla Structures – Revit connection plugin. If using IFC, ensure that Revit export is set to include “Structural connections” as separate IFC elements (using IfcBuildingElementProxy).

MEP Engineering: Revit and Hevacomp or IES

For MEP analysis, gbXML is preferred. Before export, define energy zones and spaces correctly in Revit (using “Room” elements and “Space” elements). Run the built-in energy simulation check to identify missing zone boundaries. Also, export to gbXML with the “Export complexity” set to “Simple” for analysis or “Full” for detailed calculations.

Facilities Management: Revit to Asset Management Systems

For handover, COBie is often required. Use the free COBie Extension for Revit from buildingSMART. Populate all COBie-required parameters (like SerialNumber, WarrantyStartDate) before export. Validate the COBie spreadsheet using the COBie Tool (part of the National BIM Standard-United States). Ensure that each space and equipment has a unique identifier that matches the asset management database.

Conclusion

Effective data exchange between Revit and other BIM software is achievable when teams adopt a structured approach. By understanding the strengths and limitations of formats like IFC, DWG, and COBie, by rigorously controlling export and import settings, and by establishing collaborative workflows supported by a clear BIM Execution Plan and a robust Common Data Environment, you can minimize data loss and maximize collaboration. Automation through Dynamo or API integration further reduces manual effort and improves consistency. As the AEC industry moves toward open standards and connected data workflows, mastering these best practices will become even more critical.

Remember that interoperability is not solely a technical issue—it is a process that requires communication, standards, and continuous learning. Invest time in training your team on export settings, run periodic model checks, and document your workflows. With these best practices in place, your project will benefit from smooth data exchange, fewer coordination clashes, and a more integrated delivery process.