Looking for a Jira alternative? Bring your issues with you

Export your issues from Jira

1. In Jira, open Filters → View all issues and narrow the search down to the project you want to move (for example project = ABC).
2. Click Export in the top right and choose Export CSV (all fields).
3. Jira Cloud puts at most 1,000 issues in one export. For a bigger project, split the search (for example by creation date) and export each part as a separate file; you can import the files one after another. Parent links are created between issues in the same file, so keep sub-tasks and epics in the same file as their issues where you can.

Then import the file into Subtask

1. Create your free account and a workspace, or open an existing workspace.
2. Click the ⋮ menu next to the workspace title and choose Import issues. You need to be a manager of the workspace.
3. Choose the source and upload the file. Columns are matched automatically; you can change any of them.
4. Map the statuses, see which people were matched, check the preview, then start the import. It runs in the background, and at the end you see what was created and what was skipped, and why.

What comes over

• Summary and description
• Status: matched to your workspace's statuses or added as new ones
• Assignee and reporter
• Labels, priority and issue type, as filterable labels
• Due date, story points and original estimate
• Comments, with their original date written at the top
• Sub-tasks and issues in an epic stay linked to their parent when both are in the same file

Upload again without creating duplicates

Every imported issue keeps its original key (Jira issue key, Trello card ID or ClickUp task ID). If you upload the same file again, or a newer export of the same project, issues already in the workspace are skipped instead of being copied a second time; they are not updated. If an import is interrupted, upload the same file again to finish it. A file without such an ID column (for example a hand-made spreadsheet) is recognised only row by row: a row that changed counts as a new issue.

Good to know

• Descriptions arrive as plain text; Jira's formatting markup is not converted.
• Jira Cloud exports comment authors as account IDs rather than names, so those comments arrive without the author's name.
• Attachments, sprints and work logs are not imported. You can append other columns, such as custom fields, to the description while mapping.
• People are matched to Subtask users by email or name. No invitations are sent to people who can't be matched: their issues stay unassigned, and you can invite them from the Users page and assign them later.
• One import can contain up to 10,000 issues in a file of up to 20 MB; split larger exports into several files.