ORGONAUT
Login Signup
Docs
Imports and setup
Import your org (CSV)

Import your org (CSV)

Use this guide to prepare a CSV that imports cleanly and predictably in Orgonaut.

If you’re viewing this page on a workspace subdomain (for example acme.orgonaut.co), the “Try it now” buttons will open the import tool directly in that workspace.

Astro can explain current import status and related operational context, but it cannot run, rerun, approve, or remediate import workflows for you. Those remain human-owned operational actions in the import UI.

Try it now

  • Open the imports list: /imports
  • Start a new run from the Import action in that page
  • Track progress and review from the selected run's progress/review screens

Imports are available only to roles that include import management. By default that means owner, admin, and manager.

What the importer expects

Orgonaut imports actors, reporting lines, departments, teams, and role metadata from CSV. The importer is strict by design so outcomes are deterministic and safe.

Rules that matter most:

  • Email is the primary unique identifier for humans.
  • Names are used as a fallback signal only (not a reliable identifier).
  • Department names should be consistent (avoid “Sales”, “Sales Dept”, “sales”).
  • Manager references must resolve to an existing row in the same import run.

Required columns (minimum)

Your CSV must include these columns:

  • email
  • full_name
  • department
  • job_title
  • manager_email

Notes:

  • manager_email can be blank for top-level leaders.
  • department is the department name (string).
  • job_title is the human-readable title (“Senior Engineer”, “VP Sales”, etc).

These columns unlock better rollups and fewer manual fixes later:

  • team
  • location
  • employment_type (e.g. employee, contractor)
  • fte (e.g. 1.0, 0.5)
  • allocation_pct (e.g. 100, 50)

Example CSV

Csv
email,full_name,department,job_title,manager_email,team,location,employment_type,fte,allocation_pct
ceo@acme.com,Ada Lovelace,Executive,CEO,,Leadership,Dublin,employee,1.0,100
cto@acme.com,Grace Hopper,Engineering,CTO,ceo@acme.com,Leadership,Dublin,employee,1.0,100
eng1@acme.com,Linus Torvalds,Engineering,Staff Engineer,cto@acme.com,Platform,Remote,employee,1.0,100
eng2@acme.com,Margaret Hamilton,Engineering,Senior Engineer,cto@acme.com,Platform,Remote,employee,1.0,100
pm1@acme.com,Patricia Smith,Product,Product Manager,ceo@acme.com,Product,Dublin,employee,1.0,100

Quality checks before upload

  • Ensure one row per email.
  • Check manager_email values refer to emails in the same file.
  • Normalize department and team names.
  • Validate FTE and allocation values are realistic for each actor.

What happens after upload

  1. Upload the file.
  2. Confirm format mapping.
  3. Choose target context (Live or a new scenario).
  4. Start import and track stage progress.
  5. Resolve quarantined rows in run review if needed.