How to convert IFC files to Revit or DWG without losing data
Updated · IFCfiles team
To convert an IFC file to Revit, link or import it through Revit's IFC importer with the right mapping settings; to convert IFC to DWG, export the geometry from Revit, FreeCAD or BlenderBIM. Neither direction is lossless — and knowing what gets lost is the difference between a usable model and an expensive surprise. This guide covers both routes, the free tools involved, and the checks that catch data loss before it costs you.
Why convert IFC files to Revit or DWG?
The scenario is always some flavor of the same story. A consultant delivers their model as IFC — maybe they work in ArchiCAD or Tekla, maybe the contract mandates openBIM — and your team lives in Revit. Or a client wants "the CAD files" and means DWG, because their facility team runs AutoCAD and always has.
Sometimes conversion is genuinely the right call. Often it isn't: if you only need to view the model, check quantities or pull properties, you can do all of that directly on the IFC — a browser-based IFC viewer opens it in seconds without Revit, and an IFC to Excel export gets the data into spreadsheets without touching the geometry. Convert when you need to author against the model: hosting elements on its walls, dimensioning its grids, producing 2D deliverables from it.
What are IFC files, briefly
IFC (Industry Foundation Classes, ISO 16739) is the open exchange format for BIM: a text-based database holding geometry, classifications, property sets and relationships, readable by any compliant tool. Crucially, its geometry is frozen — it records shapes, not the parametric recipes that produced them. That single fact explains most conversion pain, because Revit is parametric to its bones and DWG barely stores metadata at all. The full picture is in our pillar guide, what is an IFC file?
The core challenge: avoiding data loss during IFC conversion
Every conversion is a translation between data models that don't align one-to-one. What survives, what degrades and what disappears:
| Model content | IFC → Revit | IFC → DWG |
|---|---|---|
| Geometry | Survives as direct shapes | Survives (3D solids/meshes or 2D) |
| Categories / classes | Survives if mapping is set up | Degrades to layer names |
| Property sets (Psets) | Survives as parameters (mapping-dependent) | Lost |
| Parametric behavior | Lost — shapes don't flex like families | Lost |
| Relationships (hosting, systems) | Partially lost | Lost |
The defense is a before/after audit. Before converting, open the IFC in a property explorer and confirm the data you care about is actually in the file — a surprising share of "the conversion lost my data" cases are really "the export never included it". Then export the properties to Excel as a snapshot. After converting, compare Revit schedules (or the DWG layer table) against that snapshot. Twenty minutes, and disputes about who lost what become grep problems.
How to convert IFC files to Revit (RVT) effectively
Revit gives you two doors, and picking the right one matters more than any other setting:
Link IFC (coordination)
Insert → Link IFC keeps the model as a live reference: it updates when the IFC is re-delivered, you can snap to it, tag it, run interference checks against it. You cannot edit it. For coordination workflows this is almost always the right answer — fast, reversible, and it never pretends the elements are yours.
Open/Import IFC (adoption)
File → Open → IFC converts every element into Revit objects. Before running it on a real model:
- Set the category mapping. Open → IFC Options loads a mapping table (IfcDoor → Doors, IfcFlowSegment → Pipes…). The default table is decent for architecture and weak for MEP and infrastructure classes — review it once, save it as your office template.
- Import the Psets. Enable property-set import so IFC properties arrive as Revit parameters you can schedule. Without it you get mute geometry.
- Check units and shared coordinates first. A model landing 2 km from the origin usually means the IFC was exported with world coordinates — fix the survey point rather than moving geometry.
- Expect direct shapes. Imported walls are walls (category-wise) but not system families; they schedule and tag correctly yet won't flex parametrically. Plan to remodel the handful of elements you genuinely need to edit, and keep the rest as-is.
About those "IFC to RVT online converter" services that rank for this search: they run the same import server-side with settings you don't control, and you hand your model to a third party to get a worse result. If confidentiality matters at all, tune the import locally instead.
How to convert IFC files to DWG
DWG holds geometry, layers and blocks — no Psets, no relationships. Accept that upfront and the conversion is straightforward:
- Via Revit (any Autodesk seat): link the IFC, set up a view (3D or the floor plans you need), Export → DWG. Categories become layers; you control the layer standard. The cleanest output if you already pay for Revit.
- Free, via FreeCAD or BlenderBIM: both import IFC natively (IfcOpenShell under the hood) and export DXF/DWG. FreeCAD's TechDraw handles 2D extraction; BlenderBIM is stronger on big models. Fiddlier than Revit, entirely free.
- ODA IFC tools: the Open Design Alliance ships free IFC viewing/conversion utilities that write native DWG — worth knowing when you need batch geometry conversion.
If the goal is lightweight 3D rather than CAD — a model for a website, Blender, Unity or a presentation — skip DWG entirely and convert the IFC to glTF: a fraction of the size, made for real-time rendering, and our converter runs in your browser without uploading the file.
Verify the result, whichever route you took
Re-export a test IFC from the converted Revit model (or open the DWG) and put it side by side with the original in the free IFC viewer — the viewer loads multiple models, so drift in placement or missing elements shows up visually in minutes. Element counts come straight from the Excel snapshot you made earlier. If something did get lost upstream, fixing the Revit export settings at the source beats patching downstream every time.