IFC data out to Excel — and back in.

Every property set and quantity to Excel, sortable and filterable, ready for the QS. Reports as HTML or BCF. COBie for handover. Then edit the spreadsheet and push the values back into the model, matched GlobalId by GlobalId. Free, browser-based, no authoring seat needed.

The model already knows the answer. The problem is that it's locked inside an IFC and the person asking uses Excel.

  • Out: XLSX · CSV · HTML · BCF 2.1 · COBie
  • Round-trip: Edit in Excel, write back by GlobalId
  • Scope: Psets, quantities, classifications
  • Batch: A folder at a time, as a pipeline

Start here — IFC to Excel

IFC to Excel, and Excel back to IFC. Export Psets writes every property set and quantity to a workbook — one sheet per IFC class, one row per element, GlobalId in the first column. That last detail is the whole feature: change values in the spreadsheet, upload it through Import Psets, and each edit lands on the element it came from. No duplicate entities, no re-modelling.

  • One sheet per IFC class, one row per element
  • GlobalId keyed, so the round-trip is exact
  • Import Psets writes the edits back into a new IFC

Open IFC to Excel

What this set does

Quantities without model-mining

Counts, lengths, areas, volumes — pulled straight from the model rather than clicked out of it one element at a time.

Reports people accept

Health, IDS and clash results bundled into an HTML report a client will actually open, or a BCF the coordinator's tool ingests directly.

Handover formats

COBie spreadsheets with the assets, spaces and equipment records an FM team expects at the end of a job.

Tools in this category

How it works

  1. Drop the IFC. Or pick one already sitting in your workspace.
  2. Pick the shape. Excel for the QS, BCF for the coordinator, COBie for FM, HTML for the client.
  3. Send or return. Hand off the file — or edit it and push the changes back into the model.

When you'd use it

The QS wants a takeoff

By Friday, in Excel, with the door schedule broken out — and re-mining the model by hand is two days you don't have.

Handover week

The FM consultant needs every asset, room and piece of equipment in COBie, formatted the way their system reads it.

Four thousand wrong values

A fire-rating parameter went in wrong across a whole discipline. Fixing it in a spreadsheet and pushing it back beats fixing it element by element.

Where it stops

  • Import Psets matches on GlobalId. An element whose GlobalId changed between export and import won't be found.
  • A takeoff is only as honest as the model. If quantities were never authored, Add Base Quantities has to compute them first.
  • COBie output follows the spreadsheet template, not a certification programme — check it against your client's schema before handover.

FAQ

What formats can I export to?

Excel (.xlsx) for property + quantity tables, BCF 2.1 (.bcf / .bcfzip) for issue / coordination data, HTML for shareable reports, and COBie spreadsheets for FM handover. Schedules and BOQs come out as XLSX with one sheet per IFC class by default.

Can I edit data in Excel and push it back?

Yes. The Export Psets / Import Psets pair is designed as a round-trip. Export, edit cell values in Excel, upload the spreadsheet, and BIMCamel updates the matching elements in the IFC by GlobalId — no model corruption, no duplicate entities.

Does the report include validation findings?

Generate Report bundles whatever you ran on the model — Health Check, IDS, clash — plus model statistics and screenshots. The HTML output is stakeholder-ready; the BCF output round-trips into desktop coordination tools.

Can I extract from a folder of files at once?

Yes. Save Export Psets (or any extractor) as a pipeline step in the Automate tab and drop a folder — you get one consolidated workbook, or one workbook per file, depending on how the pipeline is configured.

Related BIMCamel tool categories

  • Validate — when the data needs checking, not exporting.
  • Convert — when it's the geometry that has to leave.