Export each project through Export/Print > JSON or CSV. If you need organization-wide coverage, use Domain export on Enterprise+ or Legacy Enterprise. The export steps are in Asana's privacy and security help article; open it alongside these steps.
Who runs it and how long it takes
- Each project: Asana's help says you can export your own data, per project. Compare the labels below with what you see on your screen.
- The whole organization: an admin or Super admin, on Enterprise+ or Legacy Enterprise.
- Time: Asana's API documentation says an organization export can take from several minutes to a few hours for large organizations.
Before you start, read How to export your Confluence spaces or site and How to export your GitHub repositories, issues and pull requests.
Export each project
- Open the project and select the drop-down arrow in its header.
- Select Export/Print.
- Choose JSON. Asana opens a link to the JSON file in a new tab. Save the file from there.
- If you choose CSV instead, it downloads in your browser. For a large project, Asana displays a generating-file message and emails you when it is finished. Keep each file on your computer.
Export the whole organization (Enterprise+)
- Select your profile photo, then Admin console.
- Open the Settings tab and select Domain export.
- Submit the request. Asana sends the admin a link to download the data.
- Download the file from the link and keep it unchanged.
The organization export is a JSON file only. It holds tasks, custom fields, sections, attachments, comments, subtasks, project statuses, messages, task templates and project templates, plus deleted projects and teams and tasks deleted in the previous 30 days.
If the file or link does not arrive
The CSV email goes to the user who requested it, and the organization link goes to the admin who submitted the request. If yours has not arrived, check that person's mailbox, then run the export again.
The JSON link is a permalink, and only people who can view the content in Asana can load it, and only while they are logged in to Asana. If the link will not open, log in with an account that can view the project and open it again.
In the Asana help article we read on 7 Oct 2026, we found no instructions for a CSV email or an organization export link that never arrives. Asana's API documentation says an export download URL may be valid for only 1 hour from the time of retrieval, so retrieve the API download URL when you are ready to download.
Check the export on your computer
Keep the Asana JSON or CSV files on your computer while you check each project, and the organization export if you have one, for completeness.
- Open each file you downloaded. A JSON file opens in a text editor or a browser, and a CSV file opens as a spreadsheet.
- Compare the number of tasks in each project with the number of tasks in the file. Count top-level tasks and subtasks separately on both sides, and note any filter you had on in Asana.
- Write down the project names, the format you chose and the date you ran each export. Keep the notes with the files.
- List what the export leaves out. Tasks deleted more than 30 days before an organization export request are not in it. In the Asana help article we read on 7 Oct 2026, we found no list of what a project export contains, so open one task with comments and subtasks and check that they are in the file.
- Keep an unchanged copy of each downloaded file alongside your inventory.
Decide between project and organization scope
| Route | Access and format | Coverage to reconcile |
|---|---|---|
| Project export | Project header > Export/Print; JSON or CSV | Compare tasks in the selected project; check a task with subtasks, a comment, a custom field and an attachment separately. |
| Organization export in Admin console | Admin or Super admin; Enterprise+ or Legacy Enterprise; JSON | Includes comments, subtasks and attachments; reconcile projects and tasks, including the documented deletion window. |
| Organization export API | Service Accounts of an Enterprise+ organization; JSON in a gzip (.gz) container | Request the export every few minutes until its state is finished, then download the file at the download URL. |
Make a local inventory with export route, organization or project, request time, format, expected task count, downloaded task count, and checks for comments, subtasks, fields and attachments. Preserve the original IDs, and record exclusions alongside counts.
Export access lets you retrieve the file. Before sharing client work, confirm the agreements and permissions for the records you want reviewed.
Review the inventory before sharing records
Use your project inventory to request an eligibility review. Keep the raw Asana files on your computer, and confirm the scope, permissions and sample-review steps before sharing records.
Task history rarely stands alone. The Confluence export guide covers the wiki pages those tasks link to, and the GitLab export guide covers engineering projects.