Is there a one-click import from Asana?

No. Asana is not connected directly. You export the project as CSV and read it in through Zuuna's spreadsheet import. Title, description, column, due date, responsible person and tags come across.

Do comments and attachments come across?

No. Neither is in Asana's CSV. Copy the important decisions out of comments by hand; leave the old project archived so the history stays readable.

Do subtasks and dependencies survive?

The nesting does not. Asana refers to the parent by name in the CSV, while Zuuna links by a stable key: subtasks arrive as their own cards. Dependencies have no counterpart in the import.

Which plan includes the import?

Every plan, including the free one. The import itself costs nothing extra.

Migrate from Asana to Zuuna: the CSV route

People leaving Asana have usually already decided. The question is the mechanics: how you get your projects out, what lands in Zuuna, and what stays behind in Asana. This walkthrough goes the whole way.

First, so there is no wrong expectation: there is no one-click import and no Asana connector. The route runs through your project's CSV export and Zuuna's spreadsheet import. It takes a little hand-work at the column mapping, and in return you see exactly what arrives before you commit.

Export your Asana project as CSV

Open the project in Asana in the browser, click the arrow next to the project name, then Export/Print and CSV. Asana builds the file and downloads it. The export holds one row per task.

The columns in the file

Before you import, open the CSV once in a spreadsheet. The columns that matter for the move are Name (the task title), Notes (the description), Assignee (the responsible person), Due Date, Section/Column (the board column) and Tags. That way you know which column goes where when you map them.

Create the board in Zuuna

Create a new board in Zuuna and open the spreadsheet import. Asana has no ready-made field mapping the way Jira and Trello do: you upload the CSV and map the columns yourself. Your file's header row becomes the list to pick from.

Map the columns and import

Map Name to the title, Notes to the description, Section/Column to the column, Assignee to the member, Due Date to the due date and Tags to the labels. Zuuna anchors due dates at 12:00 UTC so the calendar day does not slip by one across time zones. Anything left over that matters to you can go onto a custom field.

Zuuna matches assignees against the members already on the board. Anything it cannot match to a person is listed for you rather than dropped silently. Check the preview and commit.

What does not come across

An Asana CSV is a table, and some things simply are not in it. Comments are not exported to the CSV, so they stay behind. Attachments the same: files are not part of the table. Subtasks do appear as their own rows, but they point at their parent by name, while Zuuna nests cards by a stable key: the hierarchy cannot be rebuilt cleanly from that, and subtasks arrive as their own cards. Dependencies (Asana's "Blocked by" and "Blocking") have no counterpart in the import. And Asana's own field types, such as formula, multi-select or people fields, do not exist in that form: their contents arrive as a plain text field, the logic behind them does not.

This is stated plainly because the worst thing about a migration is the gap you only notice weeks later. Zuuna shows you a report after the import of what was left out.

What to do about the comments

Re-entering comments by hand is only worth it for the few threads that hold a real decision. For those, copy the outcome into the card description or as a first comment. The rest is easiest solved by not deleting the old Asana project right away but leaving it archived: the history stays readable without you retyping it.

After the move

If you are still weighing whether the move is worth it, the detail is in the Zuuna versus Asana comparison and in the overview of Asana alternatives.