Skip to content

Project management

Find and export
your Asana data.

Asana tasks can belong to several projects. A company inventory needs to describe that overlap as well as the project and organization export options available.

Report in
Records
Category
Project management
Last checked

Find your Asana data size

  1. Use an account or service account with access to the projects in scope.
  2. Ask a developer to list those projects through the Asana API.
  3. Retrieve each project's task count with opt_fields=num_tasks, which requests the otherwise omitted count field.
  4. Count unique task identifiers for a combined total, or label a sum of project counts as potentially duplicated.
The same task can appear in several projects. Project totals should not be presented as a deduplicated organization count.

What to include in your data inventory

Report in records, identifying tasks, projects and any duplicate-count limitation. Describe comments, custom fields and attachments available.

Give the earliest retained task date, teams and users represented, including imported work.

Add the dates covered and the people who use this software. Label estimates and describe how you calculated them.

Export your Asana history

  1. Check the organization's current export entitlement with the administrator.
  2. Where licensed, request an organization JSON export using the authorized service-account route.
  3. Download the completed archive while its link is valid and preserve identifiers and relationships.
  4. For project-level collection, export each project through its available controls and check the fields and files included.

Organization, graph and resource exports depend on the product entitlement and permissions. Confirm the scope before choosing one.

Project CSV files need separate checks for conversation and attachment completeness.

Why Asana data has value for AI training

Task history can connect an assignment with discussion and a completed result.

Project relationships can show how a team coordinates dependencies across a larger piece of work.

What stays private

Select the teams, projects and tasks in scope, reviewing private project and personnel content.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.

Common questions about Asana data

Can we add every project count together?

That can count tasks more than once. Use unique task IDs or identify the overlap.

Why is the task-count API response empty?

Asana requires the count fields to be requested explicitly through opt_fields.

Can every plan export the whole organization?

Check the current organization-export entitlement and administrator permissions.

Does a project CSV include the entire task history?

Inspect its fields and collect required comments or attachments through an appropriate additional route.

Your data inventory

Add your numbers to the picture.

Enter the quantities and years covered in your data inventory, then share it with your Telegraph Lab contact. We’ll review the material and discuss the next step with you.

Discuss your data