CSV Integration Schema: Inventory
Last updated: October 5, 2026
This is the format for Inventory coming into Housing.Cloud during a managed migration. Each row is a single bed; all parent levels (building, floor, room) are built implicitly if they don't exist yet.
| Column | Type | Required | Notes |
|---|---|---|---|
building |
string | Yes | Must be unique |
buildingId |
string | No | The SIS building code; must be unique |
floor |
string | No | Unique per building |
suite |
string | No | Unique per building/floor |
room |
string | Yes | Unique per building/suite |
bed |
string | Yes | Unique per room |
roomType |
string | Yes | e.g. Single, Double, Green_Hall_Triple |
roomTypeCapacity |
number | Yes | |
bedType |
string | Yes | |
bedCostCode |
reference | Yes | Must match a preexisting Charge Code name |
| building address & description fields | string | No |
buildingStreetAddress/City/Zip/State (2-char USPS); *Description fields |
A building address saves only if all required parts are present (everything except buildingStreetAddress2). Building/room/bed combinations must be unique — occupancies reference them exactly.
Delivery
Ingress (managed migration) · Ethos equivalent: buildings + rooms (used for indexing).