Back to the BIM & IFC blog
Tool Guides · 2026-06-03 · 8 min
IFC Properties Missing After Export From Revit? The Fix Checklist
You exported the model, opened the IFC, and half your parameters are gone — or worse, they exported fine for you but vanished when a colleague ran the same export. Here's the checklist that explains why IFC properties go missing from Revit and how to get every one of them across.
IFC Properties Missing After Export From Revit? The Fix Checklist — IFC Viewer Online article cover
Missing properties is one of the most reported IFC export problems, and it's rarely a single bug — it's four or five distinct causes that all look identical from the outside: you open the exported IFC and the data you expected just isn't there. The frustrating part is that the geometry is perfect, so nothing looks broken until someone downstream goes looking for a parameter that should be on every element.
Before you change a single export setting, confirm the properties are actually missing rather than just hiding under a different property set name. Open the IFC and click any element — the full property set list shows you exactly which Psets and values survived the export.
Inspect property sets on a real model
Open the buildingSMART duplex, click any wall, and browse its complete property sets. Then open your own export and check whether your parameters made it across — and under which Pset.
IFC2x3 · 2.4 MB
Open the interactive IFC viewer
Cause 1: The Parameter Has No Value
The single most common reason. If a Revit parameter is empty for an element, the IFC exporter drops it for that element rather than writing an empty property. In the export mapping UI those parameters often appear greyed out. The fix is upstream: populate the parameter in Revit. An empty parameter is not exported, full stop.
Cause 2: Unit Mismatch With the IFC Schema
When a Revit parameter shares its name with a standard IFC property but uses a different unit type (a length parameter mapping to a property the schema expects as a count, for example), the exporter can refuse to write it. The value exists, but it silently fails to map.
Cause 3: Custom Pset Mapping File Problems
Custom property sets are driven by a text mapping file (the IFC export user-defined Pset configuration). If a property name in that file doesn't exactly match a Revit parameter — wrong spelling, wrong case, wrong data type token, or a parameter that doesn't exist in the model — that line produces nothing. No error, just a missing property.
- Confirm the mapping file is actually selected in the export setup (it resets between sessions and machines).
- Match parameter names exactly, including case and spacing.
- Make sure the declared data type (Text, Real, Integer, Boolean) matches the Revit parameter's type.
- Verify the parameter exists on the categories you're exporting — a wall Pset line won't populate doors.
Cause 4: It Works for One Person but Not Another
A genuinely confusing case reported repeatedly: the same model exports all parameters when one team member runs it, but loses shared parameters when a colleague exports it. The usual culprit is that shared parameters and the custom Pset mapping file are stored locally per machine. If the shared parameter file or the mapping file isn't identical on both workstations, the export silently differs.
Cause 5: Standard Psets Were Never Enabled
Common Property Sets (Pset_WallCommon, Pset_DoorCommon, and so on) are the schema-standardised data that any receiving tool knows how to read — the passport data of your model. They are not always exported by default. In the IFC export setup, enable "Export IFC Common Property Sets" so the standard Psets are written alongside any custom ones.
The Pre-Delivery Property Checklist
- Populate empty parameters in Revit — empty values are never exported.
- Enable 'Export IFC Common Property Sets' so standard Psets are included.
- Select your custom Pset mapping file in the export setup (check it didn't reset).
- Confirm the shared parameter file and mapping file are identical across the team.
- Resolve unit mismatches by remapping to a correctly-typed parameter.
- Export to a local folder, open the IFC, and verify the properties survived — before the file reaches the CDE.
For the export settings that prevent GUID, coordinate, and proxy problems at the same time, see How to Export Clean IFC Files from Revit. To confirm nothing else is wrong before delivery, run a full validation and target a Health Score of 80 or above.
IFC Properties Missing After Export From Revit? The Fix Checklist