How to Manage an IFC Model Exchange Between Archicad and Revit

For most Archicad↔Revit teams, the reliable path is Graphisoft’s free IFC Model Exchange with Archicad for Revit add-in. Where that isn’t available, export IFC4 in the Design Transfer view with disciplined origin alignment and explicit property-set mapping, then import or link into Revit and validate before anyone builds on it. IFC exists to move geometry and data between platforms at defined milestones. It is not a substitute for the native RVT or PLN file, and treating it as one is the single most common cause of coordination failures.

Before you export anything, confirm three things:

• The target model view and schema (IFC4 Design Transfer for editable handoffs, IFC2x3 if a downstream tool still requires it)
• That shared coordinates and project base points match on both ends
• That the resulting file passes a sanity check in an independent IFC viewer

Pro Tip: A round-trip re-import through IFC will not preserve native parametric behavior. Re-imported geometry is generally lossy compared with native RVT, so keep the native file as the single source of truth and treat IFC purely as the coordination and handover layer.

Key Takeaways

Reliable IFC model exchange between Archicad and Revit depends on disciplined schema selection, aligned coordinates, and a validation step run before, not after, the file gets built on.

Key Downloads, Vendor Docs, and Standards to Consult Next

• IFC Model Exchange with Archicad for Revit — the add-in itself, plus release notes and version history.
• Data and model exchange between Revit and Graphicad — Autodesk’s technical notes on coordination differences.
• IFC introduction / buildingSMART — the standard itself and model view definitions.
• IFC vs RVT: Key differences in interoperability — a clear breakdown of why IFC and RVT serve different purposes.

Table of Contents

• What the Graphisoft IFC Model Exchange Add-In Actually Does
• Sending a Model From Archicad to Revit: A Step-By-Step Checklist
• Preparing a Revit Model for Export to Archicad
• Choosing Between IFC2x3 and IFC4 Model Views
• Fixing the Most Common IFC Exchange Problems
• How Do You Validate an Imported or Linked IFC Model?
• How Aman Engineering Operationalizes IFC Handovers
• Sources

What the Graphisoft IFC Model Exchange Add-In Actually Does

The add-in isn’t a generic IFC translator bolted onto Revit. It performs three distinct functions that address specific pain points in Archicad↔Revit exchange.

• Improved IFC Import: reads incoming IFC geometry with better fidelity than Revit’s stock IFC importer, particularly for architectural elements authored in Archicad.
• Link IFC: brings an Archicad-originated model into Revit as a non-editable reference, ideal for coordination and clash review without risking accidental edits.
• Export to Archicad: packages Revit elements with mapping enhancements specifically tuned for reopening in Archicad, rather than a raw generic IFC dump.

The biggest gains show up in bi-directional workflows, structural engineers in Revit coordinating against an architect’s Archicad model, or vice versa, where round after round of plain IFC export/import would otherwise degrade geometry and property data. Graphisoft maintains yearly updates to the add-in that improve mapping accuracy, so check the release notes for your Revit version before assuming a compatibility issue is unfixable. An installer refresh is typically a small download and worth doing before starting a new project handover.

Sending a Model From Archicad to Revit: A Step-By-Step Checklist

Getting a clean Archicad export into Revit comes down to sequencing, not luck. Follow these steps in order:

1. Pick the model view first. Use Design Transfer view with IFC4 if every party on the exchange supports it. It carries richer geometry and property content than older coordination-only views, per buildingSMART’s model view documentation. Fall back to IFC2x3 only if a downstream tool genuinely can’t read IFC4.
2. Align origins before you export, not after. Confirm the Archicad project origin matches Revit’s shared coordinates system. A few centimeters of drift here compounds into meters across a tall building.
3. Export a test set first. One floor or one representative wing catches property-set and geometry mapping problems long before you commit to a full building export.
4. Check Archicad’s export settings: verify property sets are enabled, element classification is mapped, and mesh tessellation settings won’t bloat file size on curved or complex geometry.
5. Choose link or import in Revit deliberately. Linking keeps the model as a non-editable reference, safest for coordination. Importing brings elements in as editable Revit objects, useful for takeoff or heavy modification but riskier for maintaining data integrity.
6. Validate after import: check levels and grids landed correctly, confirm key property sets survived the trip, and do a visual walk-through of major assemblies.

Pro Tip: Export the small test block through the exact schema and settings you plan to use for the full model. A mismatch that shows up on one floor will show up on all forty, so find it early.

Preparing a Revit Model for Export to Archicad

Revit-to-Archicad exports fail most often because of sloppy pre-export housekeeping, not because the tools are incapable. Use the add-in’s Export to Archicad function rather than Revit’s generic IFC export whenever the destination is Archicad. It applies category-to-IFC mapping tuned to how Archicad interprets incoming elements, which cuts down on family mismatches that otherwise require manual rebuilding on the receiving end.

Before you run the export:

• Resolve phasing so only the intended phase is included; leftover demolition or future-phase elements confuse the receiving model.
• Turn off unnecessary view filters and worksets that aren’t relevant to the handover, since these can distort what actually gets translated.
• Review category-to-IFC parameter mapping and confirm the fields Archicad expects (material, fire rating, load-bearing flag) are actually populated, not left blank.
• Open the exported IFC in an independent viewer before sending it. Catching a stripped parameter yourself costs minutes; catching it after the architect has built on top of it costs days.

Revit’s IFC export mapping interface has matured meaningfully in recent releases, including improved link orientation controls, so always confirm you’re exporting from a current build rather than troubleshooting a bug that was already fixed.

Choosing Between IFC2x3 and IFC4 Model Views

IFC is formalized as ISO 16739-1, and a “model view” defines which subset of that schema a given exchange actually uses. Getting this choice wrong is where most Archicad↔Revit teams lose data they didn’t know they were losing.

• IFC4 Design Transfer View carries richer geometry and property definitions, and it’s the right choice when the receiving team needs to edit elements downstream rather than simply review them.
• Reference or Coordination views are leaner, built for clash detection and visual review rather than editable transfer, and often the better fit when the IFC is destined for a coordination platform rather than another authoring tool.
• IFC2x3 remains relevant only when a specific downstream tool or authority portal hasn’t caught up to IFC4 support. Confirm this rather than assuming it.

The trade-off is straightforward: richer schemas carry more fidelity but demand more disciplined export settings on both ends. A team that defaults to IFC4 Design Transfer without checking that both Archicad and Revit builds actually support it consistently will hit more translation errors, not fewer.

Fixing the Most Common IFC Exchange Problems

Most IFC compatibility issues trace back to a small, repeatable list of causes.

• Lost parameters after import usually mean the property-set mapping wasn’t explicit on export. Fix it by defining a minimum required property list (material, fire rating, structural flag) before every export, not after a client complains.
• Family mismatches happen when Revit categories don’t map cleanly to Archicad’s classification system. Standardizing category mapping once, at the template level, prevents re-solving it on every project.
• Misaligned origins are almost always a shared coordinates problem, not a software bug. Re-check base points before blaming the translator.
• Lossy round-trip behavior is expected, not a defect. Autodesk documents that Revit and IFC handle model coordination differently: clashes tied to native Revit-originated issues don’t always carry over identically when the source was IFC.

Pro Tip: Version your native file and its IFC export as a pair, same date stamp, same revision number. When a downstream team reports a discrepancy, you need to know instantly whether it’s a stale IFC or a genuine translation defect.

When a problem persists past the checklist, check the add-in’s release notes for a known issue before assuming it’s unfixable, and escalate to vendor support with the small test export rather than the full model.

How Do You Validate an Imported or Linked IFC Model?

Validation is what separates a usable exchange from a liability. Run these checks every time, not just when something looks wrong:

1. Open the file in an independent IFC viewer before it touches the working model, to catch obvious geometry or property failures early.
2. Confirm coordinate and grid alignment against the native model. Misalignment here is the fastest way to introduce clash-detection false positives.
3. Spot-check property sets on a sample of elements, not just the whole-model element count, to confirm the data survived translation.
4. Run automated clash detection through a coordination platform for repeatable checks, but pair it with a human visual review of major assemblies.
5. Cross-reference against buildingSMART-certified validators when the deliverable is going to a regulatory or handover milestone, since certified tools catch schema violations generic viewers miss.

Automated checks catch scale, but a five-minute human walkthrough of the model’s major assemblies catches the thing no script is looking for.

How Aman Engineering Operationalizes IFC Handovers

On a real project, someone has to own the export, and it can’t be an afterthought assigned the day before a submission is due. Aman Engineering assigns export and handover responsibility to the BIM coordinator on each discipline team, with sign-off checkpoints built into the project’s digital engineering workflow before any file reaches an authority reviewer or another consultant.

• Every handover issues the native file and its IFC pair together, with matching revision numbers.
• Naming conventions flag schema version and export date so a stale file is obvious at a glance.
• Model sign-off happens before submission, not after a rejection.

A handover that arrives without its native counterpart is treated as incomplete, regardless of how clean the IFC file looks on its own. That native + IFC pairing is what keeps statutory-ready models defensible when a regulator or downstream consultant asks a question the IFC alone can’t answer.

Why hybrid workflows beat picking one format

The pragmatic answer isn’t Archicad versus Revit, or IFC versus native. It’s both, with governance. Keep native files as the authoring source, use IFC strictly for exchange, and run a five-minute audit on every handover. That habit, more than any single setting, is what makes multidisciplinary coordination actually hold up under deadline pressure.

— Aman

Where Aman Engineering Fits Into Your IFC Workflow

If your team is losing hours reconciling Archicad and Revit models by hand, that’s exactly the friction a structured BIM process is built to remove. Aman Engineering prepares BIM models for statutory-ready handovers, performs IFC export mapping and validation, and structures deliverables so they hold up under authority review rather than bouncing back with rejected submissions.

Our team handles the model QA work most in-house teams don’t have time for: checking property-set completeness, confirming coordinate alignment, and catching translation losses before they become a coordination dispute between disciplines. Whether you need a one-time model audit, a pilot project to test a new exchange workflow, or a full handover package prepared for submission, reach out to Aman Engineering to scope what your project actually needs.

Sources

• Data and model exchange between Revit and Graphicad
• IFC introduction / buildingSMART

Recommended

• CORENET X Submission Guide: Electronic Building Plans – Aman Engineering Consultancy
• CORENET-X Transition Guide: Submitting Temporary ERSS via Singapore’s OpenBIM Engine
• Top BIM Tools for Singapore Projects: Architects & Engineers Guide
• Maximizing Efficiency with Revit: Tips for Architects and Designers