# How to move from Asana to Artavolo.com

> You export each Asana project as CSV and bring the files into Artavolo together. Each project becomes a table and each task a record; sections become a single select, tags a multiple select, and subtasks records that name their parent task. Asana’s CSV leaves out comments and attachments, and rules are rebuilt as automations. Nothing in Asana changes while you try it.

Source: https://artavolo.com/migrate/asana
Last reviewed: 16 November 2026

## In short

You export each Asana project as CSV and bring the files into Artavolo together. Each project becomes a table and each task a record; sections become a single select, tags a multiple select, and subtasks records that name their parent task. Asana’s CSV leaves out comments and attachments, and rules are rebuilt as automations. Nothing in Asana changes while you try it.

You import with: Import data, then Other apps.

## Before you start

- List the projects you bring, and the custom fields each one uses.
- Copy the comments you need, or ask us to bring them over Asana’s API: the CSV leaves them out.
- Download attachments you still need: they are not in the CSV either.
- Write down each project’s rules, to rebuild as automations.
- Make a free Artavolo account and a workspace: the free plan has no limit on people or records.
- Keep Asana running. Nothing in it changes, and the team switches once the new base is checked.

## Moving from Asana in 5 steps

### Step 1: Export from Asana

You get: CSV, one file per project.

1. Open the project, then the arrow next to its name.
2. Choose Export / Print, then CSV.
3. Repeat for each project you bring. Comments are not in Asana’s CSV; copy the ones you need first, or ask us.

### Step 2: Bring the files into Artavolo

The files are read in your browser.

1. In Artavolo, choose **Import data** on Home, then **Other apps** ([this link opens it for you](https://artavolo.com/login?then=%2F%3Fimport%3Dapps#sign-up)).
2. Pick or drop the files, all at once: each becomes a table, linked where one names the other’s records. Say they come from Asana, so the report names it.
3. The tables and their fields are shown with their types, and what was found (links, lookups, groups). Untick a table to leave it out, then choose **Make the base**.

### Step 3: Read the import report

It lists the tables and records made, the formulas and lookups checked against Asana’s own results record by record, and what is different, so nothing is dropped without a word.

### Step 4: Check the new base

1. Compare the number of records in each table with Asana.
2. Open a few records and check their links, dates and selects.
3. Make a kanban view by the Section field and compare it with the project’s board in Asana.
4. Go through the report’s list of what is different, and decide what to rebuild.

### Step 5: Rebuild and switch over

1. Rebuild what the export leaves out: the table below lists it, and so does the import report.
2. Invite the team, and set who sees which tables and records.
3. Set Asana to read-only, or stop using it, and keep it for a month rather than deleting it.

## Asana's words in Artavolo.com

| Asana | Artavolo.com |
| --- | --- |
| Workspace or organisation | Workspace |
| Project | Table |
| Task | Record |
| Subtask | Record, with its parent task named |
| Section | Section field (single select) |
| Tag | Multiple select field |
| Custom field | Field |
| Board view | Kanban view by the Section field |
| Rule | Automation |
| Portfolio or goal | Interface page over the tables |

## What comes over

- Every task of every project you bring, a table per project
- Sections as a single select, tags as a multiple select
- Assignees, start and due dates, completion dates, notes
- Subtasks, with their parent task named

## What you rebuild

- Rules (as automations)
- Comments and attachments, which Asana’s CSV does not include
- Portfolios and goals (an interface over the tables)

## Help with the move

We move a base or a whole workspace from Asana for a fixed price, agreed before we start and quoted by e-mail: https://artavolo.com/contacts

## Questions and answers

### Do comments come over?

Not from the CSV: Asana leaves them out of its project export. Its organisation export has them, on Enterprise+. If comments matter, tell us and we bring them over its API as part of a fixed-price move.

### Do sections and tags stay?

Yes. Section/Column becomes a single select (a kanban view by it gives you the board back), and the tags in one cell become a multiple select.

### Do subtasks come over?

Yes, as records of the same table, each with its parent task named.

### Do rules come over?

No: they are not in the CSV. Write them down first and rebuild them as automations, which run on the server on every plan.

### Does anything change in Asana?

No. You only export from Asana, and the files are read in your browser. Keep using it until the team has switched.

### Can you do the move for us?

Yes. We move a base or a whole workspace for a fixed price, agreed by e-mail before we start: we run the import, rebuild what the export leaves out and check the result against the report with you.

How Asana compares: https://artavolo.com/compare/asana.md
