Finding and exporting your Asana data

What it holds

Asana organizes tasks into projects with descriptions, ownership, dates and discussion history. Teams, portfolios, goals and messages supply broader work-planning context.

Where Asana shows the size

1. Choose a token that can access every relevant project; an Enterprise service account or super admin is preferable for broad coverage.
2. List workspace or organization projects through the API.
3. Call GET /projects/{project_gid}/task_counts with opt_fields=num_tasks for each project and add num_tasks. Treat the sum as an upper bound because multi-project tasks repeat.

Plan and admin role. Task counts respect the token’s project access and have an additional rate limit. Admin console and super-admin features require Enterprise or Enterprise+. Complete organization JSON is listed for Enterprise+, or Enterprise with the Compliance add-on, and its API requires an Enterprise service account.

Exporting the full history

1. Confirm organization-export entitlement before starting a complete backup.
2. Using the service account, call POST /organization_exports with the organization gid and poll until the export state is finished.
3. Download the gzipped JSON immediately; the URL lasts about one hour. Large exports may take minutes to hours.
4. Without organization-export access, export projects individually to CSV and consolidate them, checking sample fields and duplicate tasks.

Personal, Starter and Advanced offer CSV/PDF rather than a native complete organization JSON backup.

Enterprise and Enterprise+ graph exports can start from a project, team, portfolio or goal. Resource exports can collect tasks, teams and messages in bulk.

Graph and resource deliveries use gzipped JSON Lines and one-hour download links. Check project CSV coverage before treating it as a full-history archive.

You don't need to run an export to talk to us, and there's no need to clean it first — removing personal data is part of our work.