CSV import
CSV import brings roadmaps, backlogs, and status sheets into Foundation without touching the Jira API first. Use it when your plan lives in Excel, Google Sheets, or another tracker you can export.
The importer handles three hierarchy patterns: a dedicated parent-key column, indentation (leading spaces), and flat lists.
Launch the wizard
Section titled “Launch the wizard”- Open the lens you want to import into.
- In the toolbar, click Import CSV.
- Follow the six-step wizard.
The six steps
Section titled “The six steps”- Upload — drop a
.csvfile onto the upload zone, or click to browse. The file is parsed in the browser; nothing leaves your session until you confirm. - Column mapping — Foundation auto-detects columns such as Summary, Issue Key, Status, and Assignee. Review each mapping and override any that look wrong. Columns you don’t want can be set to Ignore.
- Hierarchy detection — the wizard shows the hierarchy mode it detected (parent column, indentation, or flat). Accept it or switch modes manually.
- Preview — scan the first 20 rows to confirm the tree looks right.
- Import — rows are uploaded in chunks with a live progress bar. Large sheets run through as an async job.
- Results — a summary shows issues created, flex items added, any errors, and links to jump into the new rows.
Rows become issues or folders
Section titled “Rows become issues or folders”- Rows with a valid Issue Key are linked to the matching Jira issue. Foundation does not re-create issues that already exist.
- Rows without a key become Flex Items — organizational folders that live in Foundation. You can convert them to real Jira issues later with Copy to Jira.
Tips for a clean import
Section titled “Tips for a clean import”- Keep one summary per row; avoid merged cells.
- Put parent-child relationships in a single Parent Key column, or use consistent indentation (two or four spaces).
- Save as UTF-8 CSV to preserve accented characters and emoji-free special characters.
- Remove formulas — paste values only.