Public Demo
You are welcome to explore this solution. Prior to official go-live, you may use it freely — however, your data may be lost in future updates. No guarantees or liability are given. Use at your own discretion.
Intermediate

Import your existing data

Load your facility lists, people, and reference data from CSV files — in the order that makes each import validate cleanly.

Published

Outcome

Your existing operational data — sites, criteria, spaces, people-adjacent reference lists, and templates — loaded from files instead of typed in, in an order where every import validates against data that already exists.

Before you begin

  • The Editor or Admin role (sites need Admin).
  • Your data in spreadsheets or exportable systems.
  • The mechanics reference: Import and export. Two rules from it shape everything below: imports validate before applying, and they upsert — “Existing items with matching IDs will be updated.”

Step 0 — Learn each format by exporting first

For every page you plan to import into, run an Export first — even from a near-empty workspace. The export format is the import format: exact columns, exact value shapes. Build your files against those samples and skip the guessing.

Step 1 — Import in dependency order

Data references data, so load the referenced things first:

  1. Sites (Administration → Sites open, then Import — CSV/JSON). Everything below lives in a site.
  2. Criteria (Settings → Criteria — CSV/JSON). The vocabulary spaces and requests will reference.
  3. Spaces (Spaces page — CSV): “the list of spaces with their properties and capabilities” — capability references resolve against the criteria you just loaded.
  4. Request Templates (Settings → Templates — CSV/JSON), if you maintain standard patterns.
  5. Users (Administration → Users — CSV/JSON) for bulk onboarding, or invite individually.
  6. Requests (Requests page — CSV) last — they reference everything above.

At each step: pick the Format, Browse to the file, Import, and read the validation result before moving on.

Step 2 — Spot-check, don’t proof-read

After each import, open the target page and check a handful of rows deeply — a space’s capabilities, a criterion’s enum values — rather than skimming everything. Validation catches structural problems; spot-checks catch semantic ones (the wrong capacity is valid data).

Step 3 — Iterate by re-import

Bulk corrections use the upsert property: export, fix the file in your spreadsheet tool, re-import. Matching IDs update in place — this is the intended bulk-edit loop, not a workaround.

What doesn’t come in by file

Floorplan images and drawn geometry are visual work — Model your facility covers them. Person skills and absences are managed on the People page. And whole-configuration transfer between workspaces (criteria + groups + templates as one validated file) is Presets, which beats per-page files when the source is another Orkyo workspace.