Skip to content
Get a quote

How do I migrate attachments from Asana to Jira?

Short answer

Use Jira Cloud's built-in Asana importer and tick the attachments option. It maps subtasks to sub-tasks and Asana stories to comments. Asana's CSV export doesn't include attachments, so the CSV route needs each file downloaded through the Asana API, hosted where Jira can reach it over HTTP or HTTPS, and referenced in an attachment column.

By

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

RouteAttachmentsCommentsSubtasksLimits
Jira’s Asana importerOptional, chosen in the importerAsana stories become commentsBecome sub-tasksCollaborators become watchers; members are optional
Asana CSV + Jira CSV importOnly as URLs Jira can reach over HTTP/HTTPSSeparate Comment columnsWork item ID and Parent columns, parents firstJira recommends about 1,500 work items per file
Asana resource export (JSON Lines)Included by defaultStories includedIncludedEnterprise+ or the Compliance Management add-on; you then transform it to CSV or the API

Steps (importer)

  1. Invite the Asana users to Jira so assignees can map.
  2. Create the Jira space with the work types and statuses you want.
  3. Run the Asana importer, pick the projects, and turn on attachments.
  4. Check one project: file count per task in Asana compared with Jira.
  5. Rebuild Asana rules as Jira automation.

Steps (CSV fallback)

  1. Pull each task’s attachments from the Asana API.
  2. Host the files at temporary URLs your Jira site can reach.
  3. Add an Attachment column per file to the CSV and import it as a Jira admin.
  4. 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.

Questions, answered

A few useful answers.

Does Jira still have an Asana importer?

Yes. Atlassian's 'Import data into Jira' page lists Asana among its direct importers, alongside CSV, monday, ClickUp, Trello and others.

Can I export Asana attachments in bulk?

Not through CSV. Asana's resource export includes attachments and stories, but needs Enterprise+ or the Compliance Management add-on. Otherwise use the Asana API per task.

Do comments come across too?

Through the importer, yes: Asana stories become Jira comments. Through CSV, put each comment in its own Comment column.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote