Asana's CSV export is per-project only, there is no native Excel add-in, and the API returns only task names unless you add opt_fields to every request.
There are two practical ways to get Asana data into Excel: the built-in per-project CSV export and the Asana API via Power Query. Asana has no official Excel add-in, so there is no live-connected option from Atlassian or Asana themselves. The CSV export works for a single project snapshot. The pain starts when you need tasks from multiple projects, or when the same report has to be current every Monday without someone exporting each project individually. Here is every method, with the limits Asana's own docs skip.
Method 1: Project CSV export from the Project Actions menu
Open the project you want to export, click the drop-down arrow in the Project Actions menu (the three-dot icon near the project name), and choose Export, then CSV. Asana downloads a file with Task ID, Creation Date, Completion Date, Last Modified Date, Name, Assignee, Due Date, Tags, Notes, Project Name, and Parent Task for subtasks.
Open the CSV in Excel and use File, Save As, Excel Workbook to convert it to .xlsx so formulas and formatting persist.
The catch: this export is per project, not workspace-wide. If you manage work across five projects, you export five separate files and combine them manually in Excel. There is no "export all projects" button in the Asana UI. The export is also a frozen snapshot, so any task updates after the export are not reflected.
Method 2: Asana API via Power Query
In desktop Excel (Windows or Mac), open Data, then Get Data, then From Web to start a Power Query connection. Point it at the Asana API tasks endpoint for your project, and add your personal access token as an Authorization header. Power Query can parse the JSON response and expand it into rows.
The catch: the Asana API uses "compact representations" by default. A GET request to the tasks endpoint without any extra parameters returns only task names and IDs. To get assignee names, due dates, completion status, notes, or any other field, you must add opt_fields to the request URL (for example, ?opt_fields=name,assignee.name,due_on,completed,notes). First-time API users consistently hit this and end up with a table of task names and nothing else. Power Query is also Windows and Mac desktop only; it does not work in Excel on the web.
Method 3: Brooked for Excel (whole-workspace pulls, any platform)
Brooked for Excel is an add-in that connects to Asana, pulls tasks from one or multiple projects into a clean flat table, and keeps the data current. Unlike the native export, it covers your whole workspace in a single import. It runs inside Excel's ribbon on Windows desktop, Mac, and Excel on the web, where Power Query is not fully supported. An AI analyst lets you ask questions like "which tasks are overdue and who owns the most of them" in plain English.
Honest framing: Excel support is in beta. Manual imports and the AI analyst work today; scheduled refresh is rolling out through the beta. The Google Sheets version of the same connector is fully live, so the Asana plumbing itself is mature.
Setting up the Asana connection
Open Brooked in the Excel ribbon, choose Asana as the source, and sign in with your Asana account. Select the workspace, choose one or more projects or pull all tasks, pick the fields you want, and import into the active worksheet. No opt_fields parameters to figure out and no CSV in between.
Brooked AI, AsanaMethod comparison
| Method | Cost | Works on | Refresh | Best for |
|---|---|---|---|---|
| Project CSV export | Free, any Asana plan | Any Excel | Manual re-export per project | One project snapshot |
| Asana API via Power Query | Free (dev time required) | Windows & Mac desktop Excel | Manual refresh | Developers comfortable with API and M code |
| Brooked for Excel | Free during beta | Desktop, Mac & web Excel | Scheduled (rolling out in beta) | Whole-workspace pulls without coding |
What operations and project teams build with this
- Cross-project task rollup: all open tasks from every active project in one flat table for leadership review
- Assignee workload report: task count and due dates per person across the whole workspace
- Overdue task tracker: tasks past due, sorted by how late they are and by owner
- Project health dashboard: completion rate and blocked task count per project, refreshed weekly
- Custom field analysis: rolling up numeric or dropdown custom fields that the native CSV export does not include
Troubleshooting common issues
Related Articles
Frequently asked questions
Can I export Asana tasks to Excel?
Asana does not export directly to .xlsx, but it exports to CSV which Excel opens natively. Open the project, click the drop-down arrow in the Project Actions menu, and choose Export, then CSV. The file includes Task ID, Name, Assignee, Due Date, Tags, Notes, and Parent Task for subtasks. Open it in Excel and save as an .xlsx if you need formulas and formatting to stick.
Does Asana have an official Excel add-in?
No. As of mid-2026, Asana has not published an official Excel add-in on Microsoft AppSource. The only native export path is the per-project CSV. For live data in Excel you need the API or a connector tool.
Can I export all Asana projects at once?
The built-in export works one project at a time. There is no workspace-wide export to CSV from the Asana UI. If you need tasks from multiple projects in one sheet, you either export each project separately and combine them in Excel, or use the API, which can query across projects.
How do I use the Asana API with Excel Power Query?
In Power Query, create a new Web source pointing to the Asana tasks endpoint with your personal access token in the Authorization header. The critical gotcha: the API returns only task names and IDs by default ('compact' representation). Add opt_fields to the URL (for example, ?opt_fields=name,assignee.name,due_on,completed,notes) to get the fields you need. Without opt_fields, most columns arrive empty.
Does the Asana export work on Windows, Mac, and Excel on the web?
The CSV file opens in any Excel on any platform, so the native export works on Windows, Mac, and Excel on the web. Power Query is available in desktop Excel on Windows and Mac but is not fully supported in Excel on the web. Connector add-ins like Brooked work across all three platforms.
Why does my Asana export not include custom fields?
The standard project CSV export from the Asana UI includes a fixed set of columns (Name, Assignee, Due Date, and so on) and does not include custom fields. To get custom fields, you need the Asana API using opt_fields to request those field values by name, or a connector that handles custom field mapping for you.
Can I sync Asana to Excel automatically without exporting manually each time?
Yes, but not through anything Asana makes natively. Third-party tools handle this. Unito installs as an Excel add-in and creates a two-way sync, so changes in either direction push across automatically. Coupler.io pulls Asana tasks on a set schedule and writes them to Excel without manual exports. Both require a paid subscription beyond their free tiers. Brooked for Excel is in beta and covers one-way scheduled pulls at no cost during the beta period.
Get live Asana task data in Excel, across your whole workspace.
Brooked for Excel is in beta and free to try. Using Google Sheets instead? Read the Sheets version of this guide.
See Brooked for Excel →
