Why attachments are the sticking point
The Atlassian thread exists because the obvious route (export Asana to CSV, import the CSV into Jira) drops every file. Asana’s CSV and PDF exports leave out comments, and Asana staff have said attachments aren’t in them either. So the CSV route needs a separate file step, and the importer is usually the easier path.
The routes
| Route | Attachments | Comments | Subtasks | Limits |
|---|---|---|---|---|
| Jira’s Asana importer | Optional, chosen in the importer | Asana stories become comments | Become sub-tasks | Collaborators become watchers; members are optional |
| Asana CSV + Jira CSV import | Only as URLs Jira can reach over HTTP/HTTPS | Separate Comment columns | Work item ID and Parent columns, parents first | Jira recommends about 1,500 work items per file |
| Asana resource export (JSON Lines) | Included by default | Stories included | Included | Enterprise+ or the Compliance Management add-on; you then transform it to CSV or the API |
Steps (importer)
- Invite the Asana users to Jira so assignees can map.
- Create the Jira space with the work types and statuses you want.
- Run the Asana importer, pick the projects, and turn on attachments.
- Check one project: file count per task in Asana compared with Jira.
- Rebuild Asana rules as Jira automation.
Steps (CSV fallback)
- Pull each task’s attachments from the Asana API.
- Host the files at temporary URLs your Jira site can reach.
- Add an Attachment column per file to the CSV and import it as a Jira admin.
- Remove the temporary hosting once you’ve checked the counts.
What the native tool does / where it stops
Atlassian documents the importer’s mappings but not file limits or failure handling. In practice, check large or externally linked files (Google Drive or Dropbox links in Asana) by hand. Those are links, not attachments, so they come across as URLs in the description, not as files.
Where FlitStack AI fits
FlitStack AI moves Asana tasks with attachments, comments, subtasks and dependencies into Jira, with users matched by email. See Asana to Jira or Jira migrations.