Asana Importer

With the Asana Importer, you can import projects, tasks, and optionally subtasks, comments, and attachments from Asana into awork.

The import typically takes between 2 and 15 minutes and depends on the number and size of the projects you're importing.

Prerequisites

• You have access to the Importer Hub in awork (typically Admin/Owner rights).
• You can create a Personal Access Token in Asana (access to the Asana Developer Console).
• If you want to use Custom Fields, Project Templates, or Project Types, these must be created in awork beforehand.
• Important: User assignments only work reliably if the people exist in both Asana and awork with identical email addresses.

---

How do I start the Asana import?

The import consists of two parts: (1) Create a token in Asana and (2) Start and configure the import in awork.

1) Open the Importer Hub in awork

1. Open Settings in awork (gear icon in the bottom left of the main menu) and navigate to Importer.
2. Select Asana and click Start Import.

2) Create a Personal Access Token in Asana

For the import, awork needs an Asana Personal Access Token. Here's how to create it in Asana:

1. Open your Asana workspace.
2. Click on your Profile in Asana and select Settings. A popup will open.

1. Scroll down to the bottom of the popup and click Show Developer Console.

1. A new tab will open. Click Create New Token.

1. Give it a name (for example, awork Token), confirm the Asana API terms of use, and click Create Token.

1. Your token will be displayed in the next popup. Copy it and save it securely so you can paste it into awork right away.

3) Insert the token in awork

1. Switch back to awork.
2. Paste the token into the corresponding field and click Next.

4) Select project type and project template (optional)

Optionally, you can select a Project Type and a Project Template. Both must exist in awork beforehand.

5) Map custom fields

In the next step, you can map Custom Fields from Asana to Custom Fields in awork. The custom fields must already be created in awork before you can select them in the import.

Important: A Status must first be created in a Project Template before you can use it in the mapping. Otherwise, the status will not be imported correctly.

Important: Person assignments only work if the person exists in both Asana and awork with identical email addresses.

If you don't want to map a column, select Do not assign.

6) Select import options (subtasks, comments, attachments)

You can separately choose whether to import Subtasks, Comments, and Attachments.

Note: In awork, there is only one level of subtasks.

7) Review summary and start the import

Before starting, you'll see a summary of your selections (for example, projects, tasks, subtasks, files, and comments). The calculation may take a few seconds.

Then click Start Import.

8) Track progress and review results

During the import, you'll see the progress and an estimated time remaining.

If your import is successful, you'll receive a confirmation. If the import fails, you'll also see a notification. You can click Back to Home to restart the import process.

After a successful import, you'll find your imported project in your awork workspace.

---

Tips & Limitations

Known Limitations

• Subtasks: awork supports only one level of subtasks. Deeper nested structures from Asana will be flattened accordingly.
• Status Mapping: A status must exist in a Project Template, otherwise it won't be imported correctly.
• Person Assignments: Assigned people are only imported correctly if the person exists in both Asana and awork with the same email address.
• Custom Fields: Fields you want to map to must be created beforehand in awork.

Tips for Clean Results

• Before importing, create a suitable Project Template (including statuses) and optionally a Project Type in awork.
• Align email addresses of your team members between Asana and awork before you import.
• Consistently use Do not assign in the mapping if you don't want to import certain fields.
• If you're unsure, start by importing a few projects first and expand later.

Mapping Columns to Custom Fields

You can map columns/fields from Asana to the following awork fields (excerpt/overview):

1. Task Name (Asana) > Task (awork)
2. Approval Status (Asana) > Task (awork)
3. Mark Task Complete (Asana) > Status (awork)
4. Subtask (Asana) > Subtask (awork) as well as Timeline (start/due date) (awork) and Date (awork) (Custom Field)
5. Assignee (Asana) > Assigned To (awork) and Person (awork) (Custom Field)
6. Description (Asana) > Description (awork) as well as Text (awork) (Custom Field)
7. Comments (Asana) > Comment (awork)
8. Attach Files (Asana) > Attachment (awork)
9. Single Select (Asana) > Text (Custom Field), Select (Custom Field), or Status (awork)
10. Multi Select (Asana) > Text (awork) (Custom Field)
11. Date (Asana) > Timeline (start/due date) (awork) and Date (awork) (Custom Field)
12. People (Asana) > Assigned To (awork) and Person (awork) (Custom Field)
13. Text (Asana) > Description (awork) and Text (awork) (Custom Field)
14. Number (Asana) > Text (awork) (Custom Field) and Number (awork) (Custom Field)

• The number in Asana is linked with Text and Number in awork.

15. Formula (Asana) > Text (awork) (Custom Field)
16. ID (Asana) > Text (awork) (Custom Field)
17. Time Tracking (Asana) > Logged Time (awork)
18. Rollup (Asana) > Text (awork) (Custom Field)
19. Projects (Asana) > Text (awork) (Custom Field)
20. Tags (Asana) > Tags (awork) as well as Text (Custom Field) or Select (Custom Field)
21. Completed At (Asana) > Text (Custom Field) and Date (Custom Field)
22. Modified At (Asana) > Text (Custom Field) and Date (Custom Field)
23. Created At (Asana) > Text (Custom Field) and Date (Custom Field)
24. Created By (Asana) > Assigned To (awork) and Person (awork) (Custom Field)
25. Followers (Asana) > Assigned To (awork) and Person (awork) (Custom Field)

Security: Handling the Token

• Treat your Asana Personal Access Token like a password and don't share it publicly.
• If you suspect your token has been compromised, revoke it in Asana and create a new one.

---

FAQ

How long does the import from Asana take?

The import usually takes between 2 and 15 minutes. The duration depends on the number of projects and the amount of tasks, subtasks, comments, and attachments.

Why aren't tasks assigned to the right person?

Assignments only work if the person exists in both Asana and awork with identical email addresses. Also check whether the person has access to the workspace in awork.

Why aren't statuses imported correctly?

A status must first be created in a Project Template in awork before you can use it in the mapping. If no matching status exists, it can't be assigned correctly during the import.

Can I map custom fields from Asana to awork?

Yes. However, the target fields must be created as Custom Fields in awork before the import. You can also intentionally skip fields in the mapping by selecting Do not assign.

Are nested subtasks from Asana fully imported?

awork supports only one level of subtasks. If you use multiple nesting levels in Asana, they will be flattened accordingly during the import.