You can add custom field information for users, such as skills, office locations, or start dates, within your Asana teams in bulk through a CSV import. This allows you to populate and maintain those valuable details with ease.
To ensure a smooth import, your CSV file needs to be formatted correctly:
To upload a CSV file:
Note
You can click Download template to learn how to structure your information.
The import process will respect all existing access controls for custom fields. You can only update fields and values via CSV which you would typically have permission to edit.
When you upload your file, the system will perform a basic check. If headers are not formatted correctly or the "Email Address" column is missing, the UI will show a warning.
The UI will immediately confirm that your file upload was successful if everything is formatted correctly.
The actual updating of user custom fields happens as an asynchronous background job. Once all the records in your uploaded file have been processed, Asana will email the user who uploaded the CSV, notifying them the records successfully processed and any errors.
No. You need to ensure that the custom fields (column headers in your CSV, e.g., "Office Location") are already set up in the team's "Members" tab before you attempt to import data for them.
Anyone who has permission to edit custom fields on users within the team's "Members" tab can use the CSV import feature. The import respects existing access controls.
The system will match users by their email address and update the custom field values in Asana based on the information in your CSV. If someone is not present in the team, it will add them to the team (and invite them to your domain) if needed.
Yes, the CSV import is designed to override existing data. If a cell in your CSV contains a value for a custom field, it will update and overwrite the existing value for that user in Asana. However, if a cell in your CSV is blank for a particular custom field, the existing value in Asana will not be changed.
No. Leaving a cell blank in the CSV will not clear Asana's existing value.
Not at this time.
For multi-select fields, separate values within a single cell using semicolons (e.g., "ValueA;ValueB;ValueC"). The handling of different custom field types will generally follow the same behavior as CSV imports for projects in Asana. The case sensitivity of custom field values will also align with how project CSV imports handle this.
The import process will create any necessary new option values for single-select or multi-select fields. So, if "London" isn't an existing option for your "Office Location" single-select field, the import will add "London" as an option and assign it to the relevant users.