Jira CSV Import and Export: Issues, Fields, and Migrations

Two Different “Excel → Jira” Jobs

Engineering teams confuse them constantly. CSV issue import creates/updates Jira issues with fields, issue types, and links. Excel to Jira table markup pastes a grid into a description/comment. This guide is the issue import/export path for US, UK, Australian, Canadian, and EU teams migrating backlogs or reporting out of Jira.

Export vs Import

Exports are easy; imports need admin rights and mapping.

Step-by-Step: Export Issues to CSV

Sprint review and audit path.

• Build a JQL filter for the project/status range you need.
• Export CSV (All fields or Current fields — know the difference).
• Archive raw as project-jira-YYYY-MM-DD.csv.
• Open in Online CSV Editor; keep Issue key as text.
• Convert to Excel for stakeholders if needed.
• For description tables inside tickets, convert a small sheet with Excel to Jira Table instead.

Issue key,Summary,Issue Type,Status,Assignee,Priority,Created,Custom field (Story Points)
PROJ-1042,Add UTF-8 BOM guide,Story,In Progress,alex@example.com,Medium,2026-05-03,3

Step-by-Step: CSV Issue Import

Migration / backlog seed path (admin).

• Confirm you have permission for External System Import / CSV import.
• Create the destination project and issue types first.
• Build CSV with Summary (required) plus mapped fields.
• Use user emails/usernames that exist in Jira for Assignee/Reporter.
• Prefer ISO dates for Created/Due.
• Map columns carefully in the import wizard — including custom fields.
• Pilot 5–10 issues; verify issue type, status, and components.
• Import the remainder; review the import log.

Mapping Gotchas: Status, Issue Type, Components

Importers cannot invent your workflow casually.

• Issue Type values must exist in the project.
• Status may map through a workflow — invalid statuses fail or land oddly.
• Components/Labels must often preexist or follow create rules.
• Parent/sub-task relationships need the columns your Jira version documents.
• Do not assume Cloud and Data Center CSV wizards are identical.

Custom Fields and Multi-Select Values

Where imports silently create mess.

• Custom field names in the CSV must match what the mapper expects.
• Select lists need valid options.
• Multi-value fields often use a documented delimiter — follow Atlassian’s sample.
• User picker fields need resolvable users.

Locale Notes for Distributed Teams

US/UK/EU backlogs collide on dates.

• Prefer ISO timestamps in import CSVs.
• German semicolon Excel files: convert before import if the wizard expects commas.
• UTF-8 for summaries with non-English text.
• See CSV UTF-8 BOM guide if Windows Excel corrupts characters or headers.

Jira CSV vs Excel-to-Jira Table

Pick the right tool.

Common Mistakes

Admin foot-guns.

• Trying to “import” by pasting CSV into a description.
• Assignee emails that are not licensed/known users.
• Re-importing weekly without Issue key/external id strategy → duplicates.
• Exporting Current fields then wondering why Story Points are missing.
• Ignoring the import validation/error file.

Best Practices

Treat imports like production schema changes.

• Sandbox/pilot project first when possible.
• Version CSVs with project + date.
• Document field dictionaries for migrations from Azure DevOps/GitHub/Linear.
• Separate analytics exports from import templates in folders.
• Cleanse in-browser when contractors prepare migration sheets.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Prep Jira import sheets in the Online CSV Editor, convert exports to Excel for PMs, and use Excel to Jira Table when you only need markup inside an issue. Works for distributed engineering teams across US, UK, AU, CA, and EU.

Conclusion

Jira CSV imports succeed when Summary, issue types, users, and custom fields map to the live project. Export for reporting, import with pilots, and use table markup tools only for in-issue grids — not for creating tickets.