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.

Start from the template

Download the Orgonaut CSV template, replace the sample rows with your people, and upload it. The template uses the canonical column names, so the importer recognises it as the Orgonaut format automatically.

You can also download the template from the Import from CSV card on the onboarding page, from the import dialog, and from the empty Live dashboard.

Required columns (minimum)

Your CSV must include these columns:

email, or both source_hris and source_hris_id
first_name and last_name (or a single name column)
department_name
job_title
manager_email

Notes:

Email can be blank when a complete source identity is provided. BambooHR PersonID supplies a BambooHR source identity. A nonblank invalid email is rejected even when source identity is present.
manager_email can be blank for top-level leaders. Use manager_employee_id/BambooHR SupervisorID when linking managers by employee ID.
department_name is the department name (string). department is also accepted.
job_title is the human-readable title (“Senior Engineer”, “VP Sales”, etc).

Recommended columns

These columns unlock better rollups and fewer manual fixes later:

team_name (or team)
location
fte (e.g. 1.0, 0.5)
allocation_pct (e.g. 100, 50)

See the CSV field reference for every supported column and alias.

Example CSV

Csv

email,first_name,last_name,job_title,department_name,team_name,manager_email,location,fte,allocation_pct
ada@example.com,Ada,Lovelace,Chief Executive Officer,Executive,Leadership,,Dublin,1.0,100
grace@example.com,Grace,Hopper,Chief Technology Officer,Engineering,Leadership,ada@example.com,Dublin,1.0,100
linus@example.com,Linus,Torvalds,Staff Engineer,Engineering,Platform,grace@example.com,Remote,1.0,100
margaret@example.com,Margaret,Hamilton,Senior Engineer,Engineering,Platform,grace@example.com,Remote,1.0,100
patricia@example.com,Patricia,Smith,Product Manager,Product,Discovery,ada@example.com,Dublin,0.8,100

Quality checks before upload

Ensure each supplied email and each source_hris + source_hris_id pair is unique in the file.
Check manager emails or manager employee IDs refer to the intended people in the file.
Normalize department and team names.
Validate FTE and allocation values are realistic for each actor.

What happens after upload

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

Search Results