Asana Importer
Import your Asana projects, tasks, comments, and attachments into awork using a Personal Access Token with Custom Fields mapping.
With the Asana Importer, you can transfer projects, tasks and, optionally, subtasks, comments and attachments from Asana to awork. Imports usually take between 2 and 15 minutes, depending on the number and size of the projects.
Key benefits and use cases
If you're switching from Asana to awork, the importer saves you a lot of clicking:
-
Move projects quickly by importing projects and tasks from Asana
-
Keep more context by optionally importing subtasks, comments and attachments
-
Control what gets imported by mapping Asana fields to Custom Fields in awork
How to use the Asana Importer
Requirements
-
You need admin permissions or access to the Workspace Settings to use the importer.
-
You must be able to create a Personal Access Token in Asana (access to the Asana developer console)
-
Set these up beforehand: If you want to use Custom Fields, Project Templates or Project Types, they must already exist in awork
Important: User assignments only work reliably if people have the same email address in Asana and awork.
1. Open the Importer Hub in awork
-
In awork, open Settings (the gear icon in the bottom-left corner of the main menu) and go to the Importer Hub
-
Select Asana and click Start Import
2. Create a Personal Access Token in Asana
awork needs an Asana Personal Access Token (access token) to import your data:
- Open your Asana workspace
- In Asana, click your Profile and select Settings (a pop-up will open)
- Scroll to the bottom of the pop-up and click Show Developer Console
- A new tab will open. Click Create New Token
- Enter a name (for example, awork Token), accept Asana's API terms of use and click Create Token
- Your token will appear in the next pop-up. Copy it and save it somewhere secure so you can paste it into awork in a moment
3. Enter the token in awork
- Switch back to awork
- Paste the token into the relevant field and click Next
4. Select a project type and project template (optional)
You can optionally select a Project Type and a Project Template. Both must already exist in awork.
5. Map custom fields
In the next step, you can map Custom Fields from Asana to Custom Fields in awork. If you don't want to map a column, select Do Not Map.
- Custom Fields must already be set up in awork before you can select them during the import.
- A Status must first be added to a Project Template before you can use it in the mapping. Otherwise, the status won't be imported correctly.
6. Select import options (subtasks, comments, attachments)
You can choose separately whether to import Subtasks, Comments and Attachments.
Note: awork supports only one level of subtasks.
7. Review the summary and start the import
Before starting, you'll see a summary of your selections (for example, projects, tasks, subtasks, files and comments). This may take a few seconds to calculate.
Then click Start Import.
8. Track progress and review the result
During the import, you'll see the progress and an estimate of the time remaining.
If your import is successful, you'll receive a confirmation. You'll also see a notification if the import fails. You can restart the import process by clicking Back to Home.
Once the import is complete, you'll find your imported project in your awork workspace.
Map columns to custom fields
You can map columns and fields from Asana to the following awork fields (selection/overview):
| Asana | awork |
|---|---|
| Task Name | Task |
| Approval Status | Task |
| Mark Task as Complete | Status |
| Subtask | Subtask as well as Timeline (start/due date) and Date (Custom Field) |
| Assignee | Assigned to and Person (Custom Field) |
| Description | Description as well as Text (Custom Field) |
| Comments | Comment |
| Attach Files | Attachment |
| Single Select | Text (Custom Field), Selection (Custom Field) or Status |
| Multi Select | Text (Custom Field) |
| Date | Timeline (start/due date) and Date (Custom Field) |
| People | Assigned to and Person (Custom Field) |
| Text | Description and Text (Custom Field) |
| Number | Text (Custom Field) and Number (Custom Field). The number in Asana is linked to Text and Number in awork. |
| Formula | Text (Custom Field) |
| ID | Text (Custom Field) |
| Time Tracking | Logged Time |
| Calculation | Text (Custom Field) |
| Projects | Text (Custom Field) |
| Tags | Tags as well as Text (Custom Field) or Selection (Custom Field) |
| Completed On | Text (Custom Field) and Date (Custom Field) |
| Last Modified On | Text (Custom Field) and Date (Custom Field) |
| Created On | Text (Custom Field) and Date (Custom Field) |
| Created By | Assigned to and Person (Custom Field) |
| Collaborators | Assigned to and Person (Custom Field) |
Tips, limitations and security
Known limitations
- Subtasks: awork supports only one level of subtasks. Deeper nested structures from Asana are simplified accordingly
Tips for a clean import
-
Make sure email addresses match in Asana and awork before importing
-
Set up Custom Fields in awork beforehand
-
Prepare a Project Template (including statuses) and, if needed, set up a Project Type in awork
Handling your token
-
Protect your token: Treat your Asana Personal Access Token like a password and don't share it publicly
-
Revoke your token: If you think your token has been compromised, revoke it in Asana and create a new one
FAQ
How long does an import from Asana take?
Imports usually take between 2 and 15 minutes. The duration depends on the number of projects and the number of tasks, subtasks, comments and attachments.
Why aren't tasks assigned to the right person?
Assignments only work if the person has the same email address in Asana and awork. Also check whether the person has access to the workspace in awork.
Why aren't statuses imported correctly?
A status must first be added to a Project Template in awork before you can use it in the mapping. If there isn't a matching status, it can't be mapped correctly during the import.
Can I map custom fields from Asana to awork?
Yes. However, the target fields must be set up as Custom Fields in awork before the import. You can also choose to leave fields unmapped by selecting Do Not Map.
Are nested subtasks from Asana fully transferred?
awork supports only one level of subtasks. If you use multiple levels of nesting in Asana, they'll be simplified during the import.





