Import an Asana project
into Noots.
Connect with an Asana personal access token, pick a project, and Noots reads it through the Asana API and builds the project here. Archived projects are left out of the picker.
How a Asana import runs.
Nothing is written back, nothing keeps syncing, and your credentials are not kept.
Connect
Paste the credential the import wizard asks for. It is used for that request and discarded.
Pick
An Asana project, across every workspace your token can see. Noots lists the first hundred, with the workspace name beside each.
Import
One column per section, in Asana's own order. Tasks with no section in that project land in a column called No section.
Mapped, field by field.
- The task name becomes the task title.
- The notes field becomes the description, as plain text. Asana's rich-text version of the same field is not requested, so no formatting is lost in translation because none is fetched.
Completion follows the column, not a flag. A card arrives in a column named after the one it was in, and it counts as complete only when that name is one this product already treats as done.
Left behind, on purpose and in full.
- Assignee and followers
- Due dates and start dates
- Tags
- Every custom field, including a custom field called Priority
- Subtasks and dependencies
- Attachments, comments and stories
- The milestone flag and the link back to Asana
- Priority: Asana tasks arrive at the default priority, because nothing in Asana's core model maps to one
If one of these is the thing you cannot lose, export a CSV and use the paste importer instead. It is on every plan and it maps an assignee and a due date, which the live importer does not.
The ceilings a big workspace will meet.
Measured from the importer itself rather than estimated. A migration that quietly stops at a limit is worse than one that tells you the limit first.
- Up to two thousand five hundred tasks per project. A larger project is cut off at that point without a warning on screen.
- The project picker shows a hundred projects in one page and does not paginate.
- Only the first page of sections becomes columns; a section that appears on a task but not in that page is added at the end.
- Completed tasks are imported like any other.
- An import is a one-off copy, not a running sync. Nothing is written back to the source, and running the same import twice creates a second project with the same tasks in it.
- Your credentials are never stored. They travel with the request, make the calls and are discarded; there is no token table behind this.
- There is no undo. If an import is wrong, delete the project it made and run it again.
- Every import writes an audit row: which source, how many columns, how many tasks, who ran it and whether it finished cleanly.
- The person who runs the import becomes a manager on the new project, and the project takes your organisation's default visibility.
Moving from Asana.
Do subtasks come across?
What about our custom fields?
Does it keep syncing with Asana?
Start on the free tier.
Import into a free workspace first and look at the result before anybody pays for anything.
No card for the free tier. 10 people and 10 projects.