Import work into an existing space in Jira using CSV

Learn how to import work items into an existing space in Jira using CSV files.

Important limitations

A few things you should know:

  • Only CSV imports are supported for this feature.

  • You can’t add new statuses, work types, custom fields, or custom field options during import. All imported data must match the existing space configuration.

Import work items into an existing Jira space

Site and organization admins can import content into both company-managed and team-managed spaces. Other users can import content only into team-managed spaces.

To import work items into a Jira space using a CSV:

  1. Select Settings (), then System. Then, select External system import.

    1. Or, if you’re not an admin, hover over Spaces in the sidebar and select Create space (), then select Import data.

  2. Select System then External System Import.

  3. Select CSV as the import source.

  4. Select the existing Space you want to import work items into.

  5. Upload your CSV file.

  6. Map the fields in your CSV file to the fields in your existing Jira Space. All fields, statuses, work types, and custom fields must already exist in the space.

    1. Map the fields in your CSV file to the fields in your existing Jira Space.

      1. In case of CMP projects, you can create new work types, custom fields, and custom field options, if required.

        More about mapping CSV data to Jira fields

        1. Make sure to select the appropriate hierarchy level from the dropdowns. More about mapping column data to work types

        2. You can only map to existing statuses and priorities. New ones can’t be created. You can a create new status/priority manually in Jira after the import.

        3. If no statuses are mapped, a default status will be automatically picked.

      2. In case of TMP projects, all fields, statuses, work types, and custom fields must already exist in the space.

  7. Review the migration summary. If your CSV contains new statuses or priorities that aren’t present in your existing space, the import will fail. Resolve these conflicts before proceeding.

  8. Start the import process.

  9. After the import completes, review the migration report.

No new configuration elements can be added during import.

Still need help?

The Atlassian Community is here for you.