Jira CSV import checker
Preflight checks your file for import blockers, silent relationship loss, accidental create/update mistakes, mapping traps, inconsistent dates, and other Jira-specific risks — before you hand it to Jira's own importer. The diagnosis is complete and free: findings and affected rows are not hidden behind a paywall.
Currently open to a small beta group while we gather feedback. If you don't have access yet, get in touch for an invite.
Example report — migration.csv
Result: 1 error · 2 warnings · 1 info
Choose what kind of import you're performing — create, update, or migrate.
Upload one CSV.
Review errors, warnings, and destination-dependent checks.
Correct the file and run it again.
Preflight is a Jira CSV validator built around the specific ways a Jira CSV import goes wrong — not a generic CSV linter. Every check below reflects a real, Jira-specific failure mode.
Malformed structure, broken quoting, blank required fields — the Jira CSV import errors that stop the file cold, found before you waste an import run on them.
Parent references that silently fail to resolve, rows in the wrong order, mixed identifier styles — the usual ways a Jira Parent import or Jira CSV hierarchy quietly breaks.
Work-item-key-shaped values sitting under the wrong header, or a key column that mixes populated and blank rows — the pattern behind most accidental duplicates in a Jira bulk update CSV.
Columns that won't map to Summary the way you expect, and historical vs. current Jira terminology that can cause confusion during mapping.
Mixed date formats, genuinely ambiguous day/month values, and display-name assignees Jira has no reliable way to match to a real user.
Local or private URLs Jira Cloud can never reach, and case/whitespace near-duplicate values that quietly split one option into two.
During this beta, please don't upload highly confidential production files.
Jira's own importer explains very little when something goes wrong — it tends to succeed silently rather than warn you. A Jira CSV validator that runs before the real import catches the version of these problems that costs the most to fix afterward:
No. It only reads the file to produce a report. The CSV itself is never changed, and nothing is written back to it.
No. Your file is processed in memory for the single check you run and is not intentionally retained afterward — there is no upload history and no database of past files.
No tool can guarantee that. Some things — whether a user exists, whether you have permission, whether a workflow status is available in that project — can only be verified by your destination Jira site itself. Preflight is explicit about which checks are file-level facts and which are things you still need to confirm in Jira.
No. It only reads the CSV file you upload. There is no Jira API connection, no OAuth, and nothing is sent anywhere except back to your own browser.
Yes. Choose "Update existing Jira items" as the import intent, and the checks most relevant to a Jira bulk update CSV — work-item-key mapping, and mixed create/update rows — are given more weight in the report.
Yes. Jira CSV hierarchy checks cover missing Parent references, child rows listed before their parent, and mixed identifier styles — the most common ways a Jira Parent import silently loses relationships.
No. Jira is a trademark of Atlassian. Preflight is an independent tool and is not affiliated with or endorsed by Atlassian.
Free during the beta. No account required to view the report.
Open the checker →