Asana · Moving out
Move from your Parody back to Asana
Your data is yours, and you can take all of it with you, even after your free month ends. This guide moves a Asana Parody's records into Asana.
Before you start#
Asana's CSV importer turns each row into a task, in a new project or one you already have. It only adds tasks; it can't update tasks that are already there, so import each project once.
Who can do this
Any Asana member can import into a project they can edit. Start dates and custom fields need a paid plan; on other plans, extra columns go into the task description.
What transfers
| In your Parody | In Asana |
|---|---|
| Projects | Projects (one CSV import per project) |
| Sections | The Section column on tasks |
| Tasks | Tasks |
What doesn't
- Whether a task is complete. Leave completed tasks out of the file, or mark them complete in Asana afterwards.
- Comments, members, rules, forms, goals, portfolios, and status updates. Recreate them in Asana.
- Dependencies on tasks that are already in the project; see Asana's advanced CSV import options for dependencies within a file.
- Record history. Exports hold each record as it is now.
1. Export from your Parody#
- Open your Parody and go to Import & export. If your Parody is paused after the free month, use Download everything on the paused screen.
- Select Download everything (JSON) and keep that file. It's the complete backup.
- Download the CSV for each record type below.
Each CSV has:
id: the record's ID in the Parody.- One column per field, named like
due_dateorproject_id. - A
(name)column after every link, such asproject_id (name), holding the linked record's name. Asana can't read Parody IDs, so these are the columns to use for links. source_id, if the records first came from Asana or another tool: their original IDs.
2. Prepare the files for Asana#
Split your tasks file into one file per project, using project_id (name). Rename the columns as below and remove the rest.
Projects
| Parody column | Asana column |
|---|---|
name | Project name (chosen when you import) |
Asana creates a project per CSV import, so you name it in the import screen rather than in a column.
Sections
| Parody column | Asana column |
|---|---|
name | Section |
Asana creates sections from the tasks file, so there's no separate sections import.
Tasks
| Parody column | Asana column |
|---|---|
title | Name |
description | Description |
section_id (name) | Section |
assignee | Assignee (email address) |
start_date | Start Date |
due_date | Due Date |
parent_task_id (name) | Parent Task |
Put the task name first, keep the header row, and sort so each parent task sits above its subtasks. Asana matches assignees by work email address, so replace names with emails. Write dates month first (MM/DD/YYYY).
3. Import into Asana#
- In Asana, create a project and choose Import → CSV, or open an existing project's menu and choose Import → CSV.
- Choose the file and confirm that the first row is a header.
- Map each column to its Asana field, and check the preview.
- Import, then repeat for the next project.
4. Check the result#
- Compare Asana's record counts with the row counts of your files.
- Open a few records and check their links, people, and dates.
5. Wind down the Parody#
- Keep the JSON backup somewhere safe.
- Cancel from the billing page. You keep access until the end of the period you've paid for.
- To clear the Parody yourself, use Delete all records on its Import & export page. To have your account and data deleted, reply to any email from us.
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.