Tutorial

Migrate from Asana to Zuuna: the CSV route

Export your Asana project as CSV and import it into Zuuna, which proposes the column mapping. What comes across, what gets linked and what stays behind.

Last updated:

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. Zuuna recognises the Asana export and pre-fills the column mapping right away, so 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 Email (the responsible person), Due Date, Section/Column (the board column), Tags, Parent task (the parent task) and Blocked By (Dependencies) / Blocking (Dependencies). 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. Upload the CSV and, once at least three of the four columns Task ID, Name, Section/Column and Assignee are present, Zuuna recognises the Asana format and pre-fills the whole mapping, the same way it does for Jira and Trello. Your file's header row stays visible in case you want to map something differently.

Map the columns and import

Zuuna maps Name to the title, Notes to the description, Section/Column to the column, Assignee Email to the member, Due Date to the due date, Tags to the labels, Parent task to a link to the parent card, and Blocked By (Dependencies) / Blocking (Dependencies) to card links. You can still change any of it before you import. 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 the assignee email 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. The Parent task column carries the parent task's Task ID, and Zuuna links child and parent through that same ID: the subtask arrives as its own card with a subtask link to the parent card. When the ID does not resolve, because the parent task is not in the same export, the import report says so rather than staying quiet about it. Dependencies come across too: Blocked By (Dependencies) and Blocking (Dependencies) carry the same kind of Task ID and become card links showing which card blocks which; an ID that does not resolve lands in the report, not nowhere. 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.

FAQ

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, but the link does: Asana's "Parent task" column carries the parent task's Task ID, Zuuna resolves it and adds a subtask link to the parent card. "Blocked By (Dependencies)" and "Blocking (Dependencies)" become card links the same way. Anything that does not resolve shows up in the import report.

Which plan includes the import?

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

Rebuild this step in your own workspace.

The guide takes a few minutes: it sticks when it is your own board underneath. 14 days of full access, no credit card.