Customizing the Revit IFC mapping table is the single most effective way to control how your Revit categories, families, and types are translated into IFC entity classes when you export an openBIM file. Out of the box, Revit ships with a default mapping table (exported as a .txt file) that assigns Revit categories to generic IFC classes such as IfcBuildingElementProxy, which is why so many exported models arrive at the coordination stage full of meaningless 'proxy' objects. By editing the mapping table, you tell Revit exactly which IFC class each category or type should become — IfcWall, IfcDoor, IfcFurniture, IfcSanitaryTerminal, and so on.
What the IFC Mapping Table Actually Is
Also worth reading: How does PDF underlay layer mapping work in Revit 2026 for automated architectural drawing conversion? · How can architects and engineers implement an automated BIM property mapping workflow to ensure data consistency across complex design projects? · What are the definitive best practices for mapping BIM compliance rules to architectural drawings?
The mapping table is a plain-text configuration file that Revit reads during IFC export. You access it through File > Export > IFC, then click the 'Export setup' / 'Modify setup' button, which opens the IFC Export Setup dialog. Inside that dialog there is an 'Additional Content' section with a button to export the current mapping table to a text file. Once exported, you can open this file in any text editor such as Notepad or VS Code and edit the assignments directly. The default file is typically named something like 'IFC mapping table.txt' and contains lines pairing Revit category names (and optionally family names and type names) with target IFC entity names.
The structure follows a hierarchy: category-level mappings apply broadly, family-level mappings override the category level, and type-level mappings override everything else. This three-tier hierarchy means you can map the entire 'Plumbing Fixtures' category to IfcSanitaryTerminal while overriding one specific family, say a commercial grease trap, to map to IfcTank instead. Each line in the file uses a specific syntax: the Revit element identifier on the left, an equals sign, and the IFC entity name on the right, with optional pre-defined property set (PSet) assignments appended. Getting the syntax wrong causes Revit to silently ignore the line, which is one of the most common reasons customizations appear not to work.
Why the Default Mapping Fails Most Projects
Autodesk's out-of-the-box mapping prioritizes broad compatibility over semantic precision. Categories without a clear IFC equivalent — casework, specialty equipment, signage, entourage, parking — all collapse into IfcBuildingElementProxy. In a typical mid-size commercial project, 15 to 30 percent of modeled elements can end up as proxies depending on how much site furniture, equipment, and specialty content the model contains. Downstream consumers using tools like Solibri, BIMcollab, or Navisworks clash detection then see hundreds of objects classified identically, making rule-based checking and quantity takeoff unreliable.
There is also a versioning problem. The IFC schema has evolved from IFC2x3 (still the most widely required deliverable format in contracts) through IFC4 to IFC4x3, and entity availability differs between them. For example, IfcSanitaryTerminal exists in both IFC2x3 and IFC4, but several more granular entities introduced in IFC4 have no IFC2x3 counterpart. A mapping table tuned for IFC4 will produce warnings or fallbacks when the same file is exported to IFC2x3 Coordination View 2.0. You therefore need separate mapping tables per target schema and per client requirement, and you should store them alongside your project templates rather than leaving them on individual workstations.
Step-by-Step: Creating and Applying a Custom Mapping Table
Start by exporting the current table so you have a valid template with correct formatting. Open the IFC Export Setup dialog, choose the setup you use most often, and export the mapping table to a working folder. Open the file and locate the category you want to change. Suppose your furniture is exporting as proxies: find the line for OST_Furniture (Revit's internal category name appears in comments or in the left-hand column) and change the target from IfcBuildingElementProxy to IfcFurniture. Save the file with a descriptive name such as 'Company_IFC4_Mapping_v2.txt'.
Return to Revit, reopen the IFC Export Setup dialog, and load the modified file back into the setup using the import/load mapping table option. Give the setup a clear name like 'IFC4 CV2.0 – Client XYZ' and save it. Critically, IFC export setups are stored per project unless you transfer them via a template. To make your customization durable, open your office template (.rte), configure the export setups there, and save. Every new project started from that template inherits the correct mappings automatically. For existing projects, use Insert > Import CAD... no — instead use the Manage > Transfer Project Standards tool, which transfers IFC export setups along with other standards between projects.
After re-exporting, validate the result. Open the IFC file in a free viewer such as BIMvision or the IFC-based viewer of your choice and check entity classifications, or run a quick check by opening the file's text and searching for 'IfcBuildingElementProxy' to count remaining proxies. A well-tuned table should reduce proxy counts dramatically; anything above roughly 5 percent of total elements usually indicates unmapped categories worth addressing.
Mapping Table vs. Direct Parameter Overrides vs. Third-Party Tools
| Feature | Custom mapping table | Per-element parameter override | Third-party exporters/plugins |
|---|---|---|---|
| Scope | Whole categories, families, types | Individual selected elements | Varies by tool |
| Effort to set up | Moderate (text editing, testing) | Low per element, high across large models | Low to moderate |
| Repeatability | High, stored in templates | None, manual per project | Depends on tool configuration |
| Cost | Free, built into Revit since ~2011 releases | Free | Subscription licenses, often $300–$1,500/year per seat |
| Schema flexibility | Manual per-schema files | Limited | Often automated multi-schema output |
| Best for | Standardized office-wide BIM delivery | One-off corrections | Complex MEP/infrastructure handoffs |
Common Mistakes That Break Custom Mappings
The first mistake is editing the wrong tier of the hierarchy. If a family-level entry already maps a specific family to IfcBuildingElementProxy, your category-level fix will never apply because family entries take precedence. Search the file for the family name before assuming a category edit failed. The second mistake is typos in IFC entity names: 'IfcWallStandardCase' versus 'IfcWall' matters, and IFC4 deprecates IfcWallStandardCase entirely. Revit does not always warn loudly about invalid targets; it may simply fall back to defaults.
Third, teams frequently forget that export setup changes do not propagate to existing projects. A firm standardizes its template in January, yet by March half the active projects still carry old setups because nobody transferred project standards. Fourth, users conflate the mapping table with property set mapping. The mapping table controls entity class assignment; PSets (like Pset_WallCommon) are controlled separately in the same dialog under Property Sets. Editing one does nothing for the other. Finally, some users try to map Revit subcategories, which the table handles only partially — subcategory support depends on Revit version, and relying on it produces inconsistent results between releases. Test after every major Revit update, because Autodesk occasionally adjusts default mappings and dialog behavior.
When to Invest Time in Mapping Customization
Act before the first IFC deliverable of a project, not after. Retrofitting classifications into an issued model creates version confusion for consultants who already linked the earlier file. The right moment is project kickoff or template maintenance cycles — many firms schedule mapping reviews twice a year, aligned with Autodesk's major release cadence (typically spring). If your contract requires IFC2x3 Coordination View 2.0 certification or a client-specific BIM Execution Plan with classification requirements (Uniclass, OmniClass, or COBie), mapping work is mandatory, not optional. COBie deliverables in particular depend on correct entity typing; spaces must export as IfcSpace and assets as proper component classes or the COBie spreadsheet generation fails or produces empty worksheets.
Conversely, if you only ever exchange files internally within a Revit-to-Revit workflow, heavy mapping investment yields little return — native RVT links preserve far more data than any IFC round-trip. Reserve deep customization for external handoffs, regulatory submissions, and asset-management handover packages.
How Automated Conversion Platforms Change the Equation
Platforms that convert architectural drawings and models into code-compliant outputs sit downstream of this whole problem, and they inherit whatever classification quality your IFC export delivers. When a conversion platform ingests an IFC file, it relies on entity types to distinguish walls from columns from doors; a model where 25 percent of geometry is IfcBuildingElementProxy forces the platform's inference engines to guess, which slows processing and increases error rates. This is a practical argument for cleaning up your mapping table even if you never manually touch the IFC file yourself: better-classified source data measurably improves automated downstream analysis, whether that analysis is code checking, quantity extraction, or clash detection. Some platforms accept native RVT uploads and handle translation internally, sidestepping the issue, but openBIM deliverables via IFC remain the contractual norm in most public and large private projects as of 2026.
A reasonable workflow pairs the two approaches: tune your Revit mapping table once per template, export clean IFC, then feed that IFC to automated review tooling. The upfront effort — typically two to six hours for a first pass plus validation — pays back quickly when automated checks stop flagging phantom proxy elements and quantity schedules reconcile correctly on the first attempt.
Maintenance and Version Control Recommendations
Treat mapping tables as controlled documents. Store them in a shared location with version numbers and change logs, exactly as you would a content library. When Autodesk releases a new Revit version, re-export the default table, diff it against yours, and merge deliberately rather than blindly reusing last year's file. Keep at least two canonical versions per office: one targeting IFC2x3 for legacy contractual requirements and one targeting IFC4 or IFC4x3 for modern handoffs. Document in your BIM Execution Plan which table applies to which deliverable so consultants can reproduce your results. Finally, audit real exports quarterly — open a sample IFC file, count proxies, spot-check ten random elements against their intended classes, and log deviations. Fifteen minutes per quarter prevents the slow drift that turns a well-tuned pipeline back into a proxy swamp.