As IFC interoperability continues to improve, BIM strategies are focusing on more powerful and consistent model exchange workflows. To ensure a smooth collaboration process, it’s essential to establish key file setup parameters from early on in the project.
In practice, ArchiCAD users often collaborate with teams working in Autodesk Revit, and the results can vary widely depending on how models are prepared and exported.
Some of the most common pain points are outlined below:
Different CAD platforms each manage and interpret storey levels in their own way. In ArchiCAD, it’s generally best practice to keep storey definitions straightforward, aligning them only with the primary building floors.
Revit, on the other hand, often incorporates additional reference levels, such as façade datums or ceiling benchmarks, which serve design and coordination purposes beyond actual storey definitions. When exchanged via IFC, these extra reference levels can be interpreted by ArchiCAD as true building storeys, sometimes causing elements to resize or reposition unexpectedly.
When importing IFC files into ArchiCAD, a commonly recommended approach is to reposition the model using survey points tied to world coordinates. This method works well and is included in our IFC Interoperability Guide here.
However, while effective for a single import, it introduces complications when ongoing coordination and repeated model updates are required. ArchiCAD’s “Update with IFC Model…” command is a powerful tool for both updating a referenced IFC and identifying revisions—information that IFC files typically do not communicate clearly.
The challenge is that this command does not account for survey-point-based repositioning. As a result, ArchiCAD may misplace the updated model, preventing accurate comparison with previous versions.
The way CAD platforms interpret and translate data from IFC files is often not the most transparent process. When a model is exchanged, the receiving application may display the data in unexpected ways, leading to various frustrations. Without access to additional software (often tied to a significant investment) it can be challenging to understand the full scope of how the model is being processed. In some cases, elements may be missing entirely, while others may appear with geometry that is generated inefficiently or inaccurately.
Below is an example of an IFC produced from ArchiCAD which had strange boundary boxes for services objects and openings. This was related to a specific setting in the IFC translator and not something that is obvious during a standard workflow.
Although it is possible to address the above issues with precise control over the IFC Translator settings, the required solution may differ between various parties.
This guide outlines a straightforward, shared workflow designed to simplify the often complex and confusing process of accurately positioning IFC models for coordination.
The overall strategy is to establish common base points, orientation and storey levels for both ArchiCAD and Revit. This will allow IFC file outputs to be exchanged between programs whilst avoiding more complex methods such as using survey points or georeferencing.
The success of this method will be dependent on the agreement of parties to structure their project files consistently.
For the workflow described in this guide, several key model settings need to be agreed upon prior to start of works, and these should be clearly communicated to all project participants.
Project Model Position
Storey Level Coordination
Coordination with Revit

Name | Setting | Description |
Settings | ||
IFC Schema | IFC2x3 | IFC2x3 is recommended for better compatibility. |
Model View Definition | Coordination View Version 2.0 | N/A |
Model Filter | SMART Model Filter | |
by Structural Function | All Elements | Change to Load Bearing Elements only if exporting Structural models. |
By IFC Domain | Custom | Filters have been set to omit irrelevant geometry data. |
Select 2D Elements to Export | ||
Grid System and Elements | On | This is needed to coordinate site boundaries. |
Lines, Texts, Labels, Fills | Off | Generally not needed. |
Door / Window 2D Views | Off | Generally not needed. |
Type Mapping | ARCHICAD Classification – v 2.0 IFC2x3 | |
Geometry Conversion | SMART Geometry Conversion | |
Conversion of Archicad elements | ||
Export Only Geometries which “Participate in Collision” | On | This is usually needed to filter out building materials such as air spaces or wall cavities. Otherwise they will read as solid in clash detection. |
Export geometry of IFC Type Products | Off | N/A |
Export gross geometry of elements | On | Simplifies model for better performance. |
Export all model elements’ geometry as: | Parametric with exceptions | Keeps slabs/walls/beams readable while allowing fallback where complex |
Elements in Solid Element Operations | Extruded/revolved | Retains SEO calculated geometries. Good balance between accuracy and performance. |
Elements with junctions | Extruded/revolved without junctions | This avoids messy Boolean junction geometry. |
Define IFC model position by | Project Origin Only | Crucial for coordinating position with Revit’s Internal Origin. |
Hierarchical Archicad elements | ||
Curtain Wall | Keep hierarchy | Prevents complex BREP blobs. |
Stair | Keep hierarchy | Prevents complex BREP blobs. |
Railing | Keep hierarchy | Prevents complex BREP blobs. |
IFC Schema related to export options | Explode when necessary | Often Revit does not understand ArchiCAD composite structures. Settings will allow for some explosions to maintain correct wall junctions. |
Composite Structures and Complex Profiles | ||
Split complex Building Elements into parts. | Off | Turning this on can often separate geometry into separate IFC elements. Keep off to maintain unified solid geometry. |
Property Mapping | Standard IFC2x3 Properties | |
Data Conversion | Smart Data Conversion | |
Select Archicad Data to Export | ||
Classifications | On | Allows for Revit filtering via category/classifications. |
Element Properties | On | Includes custom Archicad element level properties. Translated as IFC Psets in Revit. |
Building Material Properties and Classifications | Off | Exports ArchiCAD Building materials as IFC Psets. Generally not needed for Revit and will affect file performance and size. |
Element parameters | Off | Exports Geometry parameters as attributes instead. Not needed for Revit. Keep off to avoid clutter. |
Component parameters | Off | Enables component-level parameters. (Skin-by-skin) etc. Revit cannot meaningfully use this data. |
Door-Window parameters | On | Exports essential opening parameters. |
Zone Categories | Off | Keep off unless Revit user specifically need ArchiCAD zones converted as Revit “Rooms” |
Export IFC Properties | All IFC Properties. | Exports all IFC property sets associated with the elements. |
Select Derived Data to Export | All Off | Only turn on if Revit requires QTO or schedule comparison |
IFC Base Quantities | Off | ‘’ |
IFC Space Containment | Off | ‘’ |
IFC Space Boundaries | Off | ‘’ |
Unit Conversion | Smart Metric | |
Length unit | Millimeter | Default |
Angle Unit | Degree | Default |
Area Unit | Square Meter | Default |
Volume Unit | Cubic Meter | Default |
Currency Unit | AUD | Default |
Time Unit | Year | Default |

Project Model Position
Storey Level Coordination
Coordinate with ArchiCAD
NAME | SETTING | NOTES |
General | ||
IFC Version | IFC 2×3 Coordination View 2.0 | IFC2x3 is an older IFC language. It offers greater compatibility with various CAD programs and versions over IFC4. |
Exchange Requirement | Architectural Reference Exchange | Includes relevant host geometry. |
Category Mapping | Default | This maps Revit Categories to universal IFC Classes. Generally, this does not need to be amended. |
Phase to Export | Varies | Set according to the project phase. |
Space Boundaries | None | N/A |
Split Walls, Columns, Ducts by level | Off | This often creates mess in the IFC translation process. Best left unchecked. |
File Header Information… | Default | N/A |
Project Address… | Default | N/A |
Additional Content | ||
Linked Files | Do Not Export | Ensures linked references are not included in the export. Only host geometry. |
Export only elements visible in view. | On | Ensures only elements visible in the Visibility/Graphic Overrides are included. |
Export rooms, areas and spaces in 3D view. | Off | N/A |
Export 2D Plan View Elements | Off | ArchiCAD generally does not register these correctly. Best toggled off. |
Export Ceiling Grids | Off | N/A |
Property Sets | ||
Export Revit property sets | Off | Not needed for ArchiCAD. Turn on only if requested by other Revit/Autodesk users. |
Export IFC common property sets | On | Ensures exported elements include key IFC properties. |
Export base quantities | On | Ensures geometry-derived quantities (volume, area) survive import |
Export material property sets | Off | N/A |
Export schedules as property sets | Off | N/A |
Export only schedules containing IFC, Pest or Common in the title | Off | N/A |
Export user defined property sets | Off | N/A |
Export parameter mapping table | Off | N/A |
Level of Detail | ||
Level of detail for some element geometry | Medium | Generally this should be set to medium unless exporting complex geometry where 3D fidelity is important. Setting this to low often causes issues with blocking fittings and curved objects. |
Advanced | ||
Export parts as building elements | Off | Generally not needed unless using ‘parts’ extensively. |
Allow use of mixed “Solid Model” representation | On | Ensures cleaner, lighter IFCs |
Use active view when creating geometry | Off | Causes unpredictable exports. |
Use family and type name for reference | On | Generally does not affect ArchiCAD |
Use 2D room boundaries for room volume | Off | N/A |
Include IFCSite elevation in the site local placement origin | On | Highly critical for aligning model Z level position |
Store the IFC GUID in an elements parameter after export | Off | Adds IFC GUIDs to Revit elements for round-tripping. Generally not needed unless models are being sent back and forth. |
Export bounding box | Off | Used for GSA or clash detection. Not needed for ArchiCAD. |
Keep Tessellated Geometry as Triangulation | Off | Only applicable for IFC4 |
Use Type name only for IFCType Name | On | Simplifies classification by removing family names. |
Use visible Revit name as the IFCEntity name | On | Exports actual Revit Element name. Best toggled on for team coordination. |
Always export faceted floors and roofs as a single IFC entity | On | Consolidates triangulated geometry. Greatly improved IFC File performance and prevented fragmented elements. |
Set “Last Modified” user to the Author in Project Information | On | Generally does not affect ArchiCAD |
Export bars in uniform rebar sets as separate IFC entities | Off | Generally does not affect ArchiCAD. |
Geographic Reference | ||
Project Site | Default site | N/A |
Coordinate Base | Internal Origin | Crucial for aligning Internal Origin to ArchiCAD’s project origin. |
macinteract Pty. Ltd. | ABN 44 155 154 653 | terms and legal. | © 2025
We use cookies to keep things running smoothly and help us improve—no secrets here!
Please select which cookies we can use. You can change your mind whenever you like!
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
These cookies are used for managing login functionality on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com