CSV Import for Project Tasks

Hi Todd,

Great point and here’s a summary to the questions asked above:

We have some additional functionality rolling out over the next 7 days that addresses some of the questions asked here:

  • Dependents will be enabled as a mappable field
  • Collaborators will be enabled as a mappable field (and now supports multiple collaborators)
  • The import status message in the bottom left will update when the import has completed

Other answers

  • Importing to organizational custom fields can be done but requires the organizational custom field to be added to the project first. We’ll be adding clearer instructions in the guide for this. The reason behind this is that project-local custom fields are less confusing for newer users.
  • The invite functionality is no longer in the CSV importer due to some confusion it was causing (the importer isn’t clear on where the invited users were getting invited to, what they’ll have access to, what their experience will be). We recommend using our project invite screen which we’ll continue to improve. Invited users can then be utilized in the importer for assignee/collaborator.

Hi Tony,

Will Tags be enabled to be a mappable field?

Thank you.


Good morning Tony!

Can you elaborate on what you mean by:

While we will usually have organizational custom fields set to a project prior to importing, it was always nice to be able to search the library for any Custom Fields that columns needed to be mapped to. I’m not a big fan of new Custom Fields of the same name (but limited field options) being created for the project otherwise.

Also, since the new importer doesn’t support the invite functionality what happens when a new user is set as an assignee or collaborator? Does it throw an error or what?


Hi Jerod,

Thanks for your follow up questions. Organizational custom fields have the benefit of maintaining consistent types and field options (for dropdowns) across your projects and teams, but becomes problematic when a user intends to use a field of the same name with different possible values or a different type. The most common example we often see of this is “Status”, where different projects of different types may use different statuses. When importing, this often means the column ends up being incompatible with the existing organizational custom field. Changing any of the dropdown values will also impact across all projects using that field (which could be desired or undesired).
When consistency is desired between projects → templates can be helpful in ensuring projects are setup the same way with the same organizational custom fields. We’ll definitely take this feedback of being able to search for organizational custom fields within the custom fields as potential future add.

The import will make a best effort - when an email that does not belong to any user in Asana is used, the task will still be successfully created but won’t have the user applied.


Thanks for the clarification, @TonyC. That makes a lot of sense. When a user is intending to import to an existing organizational custom field it does require an extra step however (- having to add organizational custom field to the project prior to importing).

The ability to browse the library to a organizational field would be really helpful. Furthermore, have you thought about offering any indicators for the users to tell when a custom field is indeed leveraging a organizational custom field rather than creating a new? This may help them ensure everything is being mapped correctly before proceeding.

Good morning, @TonyC!

Are we on track with these updates?

Anything anything else to expect?

Hi @LEGGO, dependents, collaborators and the import completion message should now all be available!

1 Like

Thank you for the new import completion messaging and the ability to map collaborators.

I don’t remember quite what you said about mapping the tags field to the pre-existing one. Will that one be possible in the new import process? We use 2 tags across all projects for specific tasks. It was part of the import process to map them to the asana tab field. Now they are showing up as organizational fields – unfortunately that means, after the import, i need to manually add tags to those tasks and remove the auto-generated organizational fields for tags. This is because we have a body of projects already in Asana that have these tags on them and to move them all to an organizational field would be an effort and we would loose the asana functionality tied to the tags field (i.e. making the tag a favorite and being able to pull a cross-project list of all the tagged tasks)

1 Like

Hi @TonyC, just read through this whole thread and am unable to find a definitive answer to the question about importing tags. It doesn’t seem like it’s currently an option, unless I’m totally missing something somewhere here and while using the import function.

If it actually isn’t an option, are there plans to eventually bring this into play? (That is – mapping tags to the Asana tag fields as opposed to text in the description.) In my current situation, bulk importing tags would be one of the most time-saving uses of importing a CSV. Would love to know what the status is! Thanks.

Hi @Dana_Arends, unfortunately tags is not supported in the current version. Please vote and leave your feedback here CSV importer: import tags so we can consider this for future enhancements!

1 Like

Hi @TonyC can you help with this please?

Hi there,

I can’t manage to figure out wny my CSV imports will not work. All the column fields in my Sheet are mapped identically to what is required. Can someone help me? This is happening for the last few projects I have created.

Hey @Halley_Bass welcome to the Asana Community Forum :wave:

Can you please provide a bit more information such as what Asana version you are using, if any error message is showing, if something loads and then stops, etc

When you tried to import tasks and as you say it did not work, have you already tried finding one of the tasks you tried to import? As maybe they ended up somewhere else.

I also recommend double checking the filter set in the project, not that some tasks are just hidden.

And I recommend looking through all troubleshootings steps.

I have troubleshooted for many hours. The issue is that the column titles don’t line up - so when I download this spreadsheet as a CSV file, and then upload to Asana - the column the column clearly labled 'Assignee" which is also clearly an email address, does not allow me to label that as Assignee. When I try to edit - I am not given the option to change that field to the correct one.

I recommend also double checking the csv encoding you used, see CSV Encoding Standard - #2 by Andrea_Mayer

And see this article under point „ Change the encoding“

Wait, I “thought” it worked, but not sure I did this correctly.

Can you explain what he meant by “run the macro”

Hm best to ask him directly but I think he just means to overwrite the original format.

Just had a look at your screenshot again and I really believe it has to do with the format cause it has the " in the field

For me when I import it does not show it

You can try adding a new empty column besides the assignee field in your sheet, copying the whole existing column and then paste as values only.

Whenever I am having troubles with a CSV import I open a google spreadsheet, import the CSV, review everything there and then download as CSV from there.
This always works well for me.

Can you try that?

1 Like