Import Jira Issues from CSV
Prepare CSV mappings for the specific Jira import route and validate a small sample. Administrative migration tools and ordinary issue-import controls do not offer identical capabilities.
Step-by-step guide
Check access and scope
Confirm your import permissions, destination space and field configuration. Preserve the source file and do not assume that a missing field can be created automatically.
Prepare unambiguous data
Use a header row with Summary and map that column to Jira Summary. Quote multiline descriptions and prepare dates in the format selected by the importer.
Map destination identities
Map source statuses, issue types and user identities to valid values.
- Worked example: Start with a bug, a task and a multiline description. If you need parent-child hierarchy, select the external-system CSV import route and test its parent mapping separately.
Choose the import route
For flat work, open Filters > Search work items > More actions > Import work items from CSV. That bulk route cannot map parent-child hierarchy. For hierarchy, an administrator should use Settings > System > External system import > CSV and the documented parent mapping.
Run a representative sample
Upload a small sample, select the destination and date format, map Summary and other fields, then choose Validate before Begin import. Resolve warnings before proceeding.
Inspect and save mappings
Inspect records and save the mapping before processing the full set.
Verify the result
The sample preserves task meaning, ownership, dates and the intended hierarchy without duplicates.
Common mistakes
Check the handoff edge case
Importing a source row twice can create duplicate operational work. Keep a reviewed source-to-destination reconciliation.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.