The files you already have, straight into one twin you own.
Bring your IFC model straight in — geometry and data intact. STEP files come in the same way.
How IFC import worksDrop an .rvt in directly, or export it to IFC.
Turn DXF and CAD floor plans into a 3D twin.
Drop in PDF drawings and trace them to 3D.
Photos of plan sheets work — detected and rebuilt in 3D.
Export IFC from SketchUp and upload that — the .skp itself does not come in. Send it to us first: SketchUp IFCs often arrive as one object for the whole building.
One format leaves: IFC. It is the one every BIM tool already reads, so the work you did in the twin stays readable outside it.
Send the twin back out as IFC — your geometry edits and finish data travel with it. Revit reads it through its own IFC import: a one-way handoff, not a live link.
Most people do not need an export. Invite them and they open the twin itself — access is by invitation, with roles and seats.
A drawing is one way in. The system that already holds your units and occupants is the other. Three connectors: each one tests the connection, syncs entities, and takes an inbound webhook.
Point it at your own Yardi account and the credentials are tested before anything is stored — a connection that fails never becomes a saved integration. From there it reads units and occupants across, and reports what it processed, created, updated and failed.
The same three parts: a credential test that has to pass, an entity sync over units and occupants, and a webhook address Buildium can call when something changes at its end. Every run is stamped with the time it finished and whether it succeeded or only partly did.
Connection tested first, then units and occupants sync on demand. The inbound receiver takes one address per connection: set a secret and every event has to carry a valid signature or it is refused, and each one is written to the log either way.
Said plainly: none of these is a partnership or a certified integration, and no field-level mapping is promised in advance — which of your records a unit or an occupant becomes is agreed with you before the first sync runs. A run is recorded as full or incremental with its finish time; today either kind reads the whole list. Connections are set up with us rather than switched on from a settings page. Tell us which system you run and we will test yours against it.
Exactly what this page claims, in a table. IFC is the only format that leaves, so most of the Goes back out column is a dash — and where a cell shows a dash we are making no claim either way. Send us the file and we will tell you.
| Format | Typical file types | Comes in | Goes back out | What we do with it |
|---|---|---|---|---|
| IFC | .ifc | Yes | Yes | Straight in, geometry and data intact. |
| Revit | .rvt | Yes, via conversion | As IFC | Drop it in and we convert it through Autodesk, or export to IFC yourself. This path is new enough that we would rather look at your file first. What comes back is an IFC that Revit imports. |
| DXF / CAD | .dxf | Yes | — | Floor plans become 3D. |
| PDF plans | Yes | — | Flat drawing sets are traced to 3D. | |
| Images | .jpg, .png | Yes | — | Photos of plan sheets are detected and rebuilt in 3D. |
| STEP | .step, .stp | Yes | — | Uploaded the same way as an IFC. |
| SketchUp | .skp | Via IFC | — | The .skp itself does not come in. Export IFC from SketchUp and upload that — and tell us, because SketchUp IFCs often arrive as one object for the whole building. |
Version, schema and file-size limits are not published here yet. If your export has to satisfy a specific schema or a size ceiling, ask us before you upload.
Upload it yourself, or tell us what you are working with and we will tell you what comes back.