A column is a section, not a board-only concept
Per Asana's own developer documentation, a board's columns and a list's section headers are the same underlying object: a section. Board view renders each section as a vertical column instead of a header above a stack of rows, but dragging a task between columns and moving it between sections in List view do exactly the same thing to the same data. There's no board-specific field that only exists in Board view.
What the native export actually pulls
Export or sync to Google Sheets is a project-level action, triggered from the project's dropdown menu regardless of which view is open when you start it. What comes out is the project's task data, including each task's section, alongside assignee, due date, completion, and custom fields, not a rendering of the Kanban board itself. Being in Board view when you export changes nothing about what's included. It carries the same gate and cap as every other Asana-to-Sheets export from this feature: Advanced and Enterprise plans only, one-way, and capped at 500 rows. See does Asana have a Google Sheets integration for the full picture of that native export, including exactly how that row cap behaves.
Step by step: getting a board's columns into a sheet
- Open the project (List, Board, or Timeline view all work identically for this) and open its dropdown menu.
- Choose Export or sync → Google Sheets, sign in, and grant Drive permission for the new spreadsheet.
- In the spreadsheet Asana creates, find the section column in the filterable data tab. It's written as plain text matching the section header you see in Board view.
- Group or filter by that column directly. Because section is the same field List view groups by, you don't need to re-derive which "column" a task belongs to from anything else.
Worked example: a support triage board
A three-column support board ("New", "In progress", "Resolved") exports as a flat list where the section value carries the column information:
| Task | Section | Assignee |
|---|---|---|
| Password reset failing for SSO users | In progress | D. Kim |
| Export button missing on mobile | New | Unassigned |
| Duplicate invoice sent to customer | Resolved | D. Kim |
A pivot table grouped by Section reproduces the board's own column counts without touching the Asana UI again.
Troubleshooting
The section column is blank for some rows
A task with no section assigned (sitting directly under the project with no column) exports with an empty section value. That's a real property of the task in Asana, not an export bug; check the task in Board view to confirm it isn't sitting outside every column.
A task appears to be in the wrong column after export
Board view and the export both read the same underlying section membership, so if the sheet disagrees with what you see on the board, refresh the export; you're most likely looking at a stale copy from before the task was moved.
The same task shows up in two different project exports
That's expected if the task is multi-homed, meaning it's added to more than one Asana project at once rather than copied. Each project's export reports the task's section within that specific project, so the same task can legitimately sit in different columns depending on which project's board you're looking at.
Reading columns back out of a spreadsheet
A board-framed report usually wants one thing: which column, meaning which section, each task currently sits in, as a plain value you can filter, group, or pivot by. That means the section needs to land in its own column of the sheet as text, not buried inside a nested object or dropped entirely. See how to export Asana to Google Sheets for handling section membership and other field types correctly, and why Asana's CSV export loses task hierarchy and sections for what the CSV route specifically gets wrong here.
Every column, on any plan
Asana Exporter writes each task's section membership as a plain spreadsheet column, on any Asana plan, with no row cap and a schedule instead of a one-off click.
See Asana Exporter