Asana CSV Export/Import Issues

A good measure of whether the CSV export/import process works is whether the exported CSV file can be reimported “as is”. This is not currently the case with Asana. Below are some findings. [Note: Because I was in a test mode, I intentionally removed assignee fields, so I’m not sure if that functionality works.]

The export to CSV has the following issues:

  • Sections are exported as “Projects”, not as “Section”, as it should be.
  • Since all dependencies are finish-start only, the “Blocked By” field is redundant on import and is merely an internal convenience. This field does not need to be exported.

The import doesn’t recognize the following fields in the exported files:

  • Completed At
  • Tags
  • Notes
  • Under common or anticipated conditions, Dependencies (which are the “Blocking” field) are not recognized because they often exported out of the necessary sequence. Current import protocol requires that Dependencies may only look “up” in the table, an obvious flaw of design. (Proper design would load a task table from the core fields, then initiate the dependency import from a full task table.)

Other issues on import:

  • “Project” field must be changed to “Section”
  • “Due Date” must be assigned then “Start Date” can be assigned, though both will be recognized.

What works?

  • “Name” is correctly identified
  • “Due Date” is correctly identified
  • “Parent Task” is correctly identified as “Subtask Of”

In summation, this export/import process is useless if the user wishes to reorganize their project “en masse” retaining key information and assignments.

I am new to Asana and cant seem to find where you can export a list to excel or csv. Is this an additional app as it comes free with most apps these days?

You can export from the pull-down menu next to the name of the schedule at the top of the screen. The little “v” next to the information icon.