Asana · Moving in
Move from Asana to a Parody
Export your records from Asana, import them into a Asana Parody with CSV files, check them, then switch over. You can move back the same way: Move back to Asana.
Before you start#
Asana exports each project as CSV or JSON. The CSV holds tasks and subtasks with their fields, which is what your Parody imports. The JSON adds comments and history; keep it as an archive.
Who can do this
Anyone who can see a project can export it. Exporting every project at once is an organization export, available to super admins on Enterprise+ as one large JSON file; it isn't needed for this guide.
What comes over
| In Asana | In your Parody |
|---|---|
| Projects | Projects |
| Sections (board columns) | Sections |
| Tasks and subtasks | Tasks |
What doesn't
- Comments and attachments. They're in the JSON export, not the CSV.
- Tags and most custom fields. Fields without a Parody field are left out.
- Rules, forms, portfolios, and goals. Recreate them on their screens in the Parody.
- Dependencies. Add them on the Dependencies screen after importing.
- Anything the Asana Parody has no field for. Check the column tables below; columns without a match are left out.
1. Set up your Parody#
- Create a Asana Parody with at least these features, so every record type has a home: Projects, Sections, Tasks. See what's in the Asana Parody.
- New Parodies come with sample records. Open Import & export in your Parody, and under Start empty, delete them.
2. Export from Asana#
- Open a project you're moving.
- Open the menu next to the project name and choose Export/Print → CSV.
- Repeat for each project. Download the JSON too if you want comments on record.
Very large projects
People have reported CSV exports of very large projects coming out incomplete. Compare the row count with the task count in Asana, and use JSON or the API if they differ.
What to export:
- Projects: Asana exports one project at a time, not a list of projects. Make a Projects sheet with a row for each project you're moving.
- Sections (board columns): there's no separate export. Copy the distinct
Section/Columnvalues from each project's task export into a Sections sheet, with the project's name beside each. - Tasks and subtasks: in each project, open the menu next to the project name and choose Export/Print → CSV. Subtasks are rows too, with the
Parent taskcolumn filled in.
3. Prepare the files#
You need one CSV per record type. Open each export in a spreadsheet app, make the changes below, and save it as CSV (UTF-8). Keep the header row.
You can put all projects' tasks in one file: the Projects column says where each belongs. Keep Task ID, so subtasks and later re-imports line up.
Keep the ID column
Map Asana's own ID to ID. Your Parody remembers it, so later files can link to the record by that ID, and importing a fresh export later updates records instead of duplicating them.
Projects
| Asana column | Parody field |
|---|---|
Name | Name |
Owner | Owner |
Status | Status |
Description | Description |
Sections
| Asana column | Parody field |
|---|---|
Section/Column | Name |
Project | Project |
Several projects can each have a section called “To do”. That's fine: tasks are matched to the section in their own project.
Tasks
| Asana column | Parody field |
|---|---|
Task ID | ID (match and link rows) |
Name | Title |
Notes | Description |
Assignee | Assignee |
Start Date | Start date |
Due Date | Due date |
Section/Column | Section |
Projects | Project |
Parent task | Parent task |
Completed | Completed |
Asana writes when a task was completed, not whether it is. Add a Completed column that says yes when Completed At has a date, for example =IF(B2<>"","yes","no") with the completion date in column B.
A task in several projects lists them all in Projects, separated by commas. Keep the one it should live in; a Parody task belongs to one project. Dates can stay as Asana writes them; the importer reads both 2026-11-21 and month-first 11/21/2026.
4. Import, in this order#
Import parents before the records that link to them, so links resolve:
- Projects
- Sections
- Tasks
For each file:
- In your Parody, open Import & export.
- Under Import, choose the record type and the CSV file.
- Check the column list. Columns named like the tables above are matched for you; pick a field for any that aren't, or leave them out.
- Select Import. If any row has a problem, nothing is written and you get a list of the problems by line number. Fix the file and import again, or tick Skip rows with problems.
Files can hold up to 5,000 rows and 4 MB. Split bigger exports and import the parts one after another. The full rules are in Import & export.
5. Check the result#
- Compare the counts on your Parody's overview with the row counts of your files.
- Open a few records of each type and check their links (the project on a task, the account on a contact).
- Open the boards and reports and check that records sit in the right columns.
6. Switch over#
- Pick a cutover time and ask your team to stop editing in Asana.
- Export again and import the new files. Rows with an ID you've imported before update those records; new rows are added.
- Share the Parody's address with your team, and keep Asana read-only until you're sure nothing is missing.
Troubleshooting#
| Message | What to do |
|---|---|
| No … named or with id "…" | The record it links to isn't in the Parody yet. Import that record type first, or check the name is spelled exactly the same. |
| "…" matches 2 … records | Several records share that name. Also map the column that links to their parent (the project or board), or use the ID instead of the name. |
| … is not a date we can read | Use YYYY-MM-DD. Day-first dates like 21/11/2026 aren't read, because 03/04/2026 would be ambiguous. |
| … is not a number | Remove words and units other than currency symbols, commas, and %. |
| The file has more than … rows | Split it into files of up to 5,000 rows. |
Sources
Checked against these pages on 2026-11-21. Vendors change their export and import tools often; if a step doesn't match what you see, their page wins.