“I sent it as an IFC, but the properties were empty when opened” is one of the most common problems in IFC exchange. And the cause usually isn’t IFC itself — it’s the export settings. This article rounds up tips for exporting IFC without losing data.
- Most lost properties / missing elements come down to export settings
- First, match the IFC version with the recipient (2x3 / 4 / 4.3)
- Be deliberate about which properties, scope and coordinate system you export
- The best defence: open and verify the file yourself after exporting
Why properties get lost
Every BIM tool “translates” its own internal data into the shared IFC format on export. During that translation, settings decide which information, in which IFC version, mapped how. Get them wrong and properties that were visible internally never make it into the IFC — so they show up empty on the recipient’s screen.
In other words, IFC didn’t “throw the data away” — the export settings didn’t include it.
Settings to get right
🏷️ Version
Export as IFC2x3 / 4 / 4.3? Match the recipient; when unsure, 2x3 is safe.
📋 Properties
Choose which property sets (Psets) to export; confirm the ones you need are included.
🧱 Scope
Which elements / views / storeys to include. Make sure you're not exporting only part.
📍 Coordinates
Base point and coordinates. Far from the origin = the dreaded "I see nothing."
🗂️ Classification
Include classification codes (e.g. Uniclass) when schedules/links depend on them.
📐 Geometry
BREP vs extrusion, etc. — balancing file size and compatibility.
A workflow that doesn’t fail
Ask the recipient's requirements
Confirm IFC version, required properties and coordinate base up front. "Just IFC" invites accidents.
Match the export settings
Set version, Psets and scope to the requirements, then export.
Open and verify yourself
Open the exported IFC in a viewer and check properties, elements and position with your own eyes.
Hand it over
Share with a note on the version and what's included; prompt the recipient to verify too.
Know the limits of round-tripping
Export to IFC, import into another tool, write it back — that round-trip is never perfect. Vendor-specific features and parametric editability are lost once you go through IFC. Not expecting “IFC round-trips back to the original” is itself a way to avoid trouble.
Summary
- Most lost properties / missing elements are about export settings, not IFC.
- Match the version first, then be deliberate about properties, scope and coordinates.
- The strongest defence is to open and verify the file yourself after exporting.
- Share the expectation that round-tripping has limits.
IFC isn’t “export and done” — it’s “export, verify, hand over.” That one extra step transforms the reliability of your exchanges.