Asana Task Exporter – two versions in two days

Pinterest

Not unexpectedly, the people who want to export stuff from Asana are the people who use it a lot.  Which means that they have more stuff to export than Asana’s API can readily handle.  One of the people who asked me about adding subtask and comment export tried my new version last night and ran into Asana’s rate limitation, which essentially broke the tool (thanks for the heads-up, Jon).  So here is another new version, and this time, it will let you select which projects you want to export.

You can choose to export subtasks and comments or not  If you do choose to export subtasks and comments, your export will take longer than if you choose not to export them.  If you get an error message that includes the phrase ‘The remote server returned an error: (429) Internal Server Error‘, then you’re trying to export too much stuff at once.  Try again, selecting fewer projects.  And yes, I know that’s annoying, but it’s a limitation imposed by Asana’s API.

Finally, my usual information about special characters and choosing your delimiter applies to this version as well:

Just a reminder that the exporter produces its output in tab-delimited form, not comma-delimited. This is to prevent problems if you have commas in the name or notes field of your tasks, but it does mean that your stuff will look funny unless you specify the correct delimiter. In Excel, you can do that a couple of ways – by importing the CSV file  or using Text to Columns. (These options may not be applicable to whatever spreadsheet program you’re using.)

If your project names or notes include any special characters (such as á, í, û and so on), please make sure that when you open the CSV file, you set the encoding to UTF8 so that these characters can be displayed properly.

You can download the tool here:  Asana Exporter GUI 20130330

If you have any questions or comments about the exporter, or if you’d like to get in touch with me for some other reason, you can do that here.

One final thing.  I’ve been told that people might like to donate for the exporter.  So I’m making that option available, and if you would like to donate, feel free to do that.  Don’t think I won’t be appreciative, because I will be.

Asana Exporter donations

Thanks for thinking about donating for the Asana Exporter. Please donate whatever amount you'd like.
  • $0.00

 

 

14 Responses to “Asana Task Exporter – two versions in two days”

Read below or add a comment...

  1. Martin Kelleher says:

    Does this work on a Mac? I downloaded and it said it was a Windows only tool?

    Thanks,
    Martin.

  2. Bruno says:

    Hi!

    I was looking for a Asana task exporter too and found this tool quite useful.

    However, as some others, I would find big value in being able to export Tags.

    Are there any plans to update the tool to do this?

    Thanks :)

  3. Jason says:

    Thanks for creating and sharing this!

    -Jason

  4. JFranchetti says:

    I got around the colon {:} issue that I posted about by renaming my 175 projects and using a dash instead. Still a bug that could result in the export leaving out important data, so would be a good fix, but not critical to me now.

    Would be nice if the exporter made it easier to select projects to export. I have to individually click on all 175.

    Would be nice if it could bring “Team” information over. We have our Workspace broken into 7 teams, which group our projects together. That would help in reporting later. You could also provide that as an option when doing an export (choose a team and it shows all projects for that team).

    Would be nice if there was a better way to handle sections. They come across in the export as a task, when they really are metadata for other tasks. It throws off reporting numbers.

    Would be nice to have create and lastmodified date for tasks. That way I could report on how stagnant tasks are.

  5. JFranchetti says:

    Thanks for creating this. One significant issue that I have. The majority of our project names have a colon “:” in the name. For example, I have 20 projects that all start off with “Telecom: Upgrade PBX” and “Telecom: Develop New Address Book”. The exporter strips out everything after the colon and now all I have have is Telecom as the project name for multiple projects.

    Fixing the above is donation worthy :)

    Other feedback: Would be cool if it could handle sections: better. They show up as tasks in the exporter data, but there is no easy way to relate them to the tasks that they include (or to strip them all out for reporting purposes). Some people may like them in the exporter data. One thought was to append the section data in front of the tasks that they relate to, though that might be annoying to some people.

  6. Varun says:

    Hi Ed
    Great tool – just checking if you have any plans on including tags in the export as well – those can be immensely useful.

    Thanks regardless
    Varun

    • ed says:

      I honestly don’t have any plans for the exporter at all, but I can certainly look at adding the ability to export tags.

  7. Nitin says:

    Hi Ed,
    Where does the exported file get stored? Its not in the folder that the application was extracted to… Everything seemed to have gone smoothly, with “Export Completed” showing at the end. I just can’t seem to find the file though!

    • ed says:

      Hi,

      Sorry for the late reply – I’ve been away. The export will be stored on your desktop.

      Cheers,

      Ed

  8. gareth says:

    Hi Ed,

    I’m getting an error when running the exporter .exe file in Win XP (vm) – is it made for Win 7 or smth, or am I missing something?

    Thanks!
    gareth

    • ed says:

      Hi Gareth,

      I built it in Win 7, but I can’t see why it wouldn’t work in XP. Can you email me (use the contact form) with more info about the error, and I’ll see whether I can help you.

      Cheers,

      Ed

      • Gareth says:

        Hi Ed,

        Just reading your other page on this:
        what is the syntax of the command line command?
        could be I’m getting that wrong and that might solve it!

        lemme try that, if not, will revert with more.

        gareth

  9. Alfred says:

    Make sure you extract the zip file before running the executable, otherwise the program will throw an error.

Leave A Comment...

*