# How do I export Asana custom fields to a spreadsheet? Asana custom fields export, type by type: text, number, select, date, people, formula, reference. How each lands in a Sheets cell, and which plans have them. ## Key takeaways - Custom fields only exist on paid Asana plans, from Starter at $10.99 per user per month billed annually, and formula fields need Advanced. - Asana has 10 custom field types: text, number, currency, percentage, single-select, multi-select, date, people, formula and reference. - Number, currency and percentage fields land as numbers, so SUM and AVERAGE work on them in Sheets. - Select fields land as the option's name, and a two-way sync only accepts options that already exist on the field. - Formula fields land as their result and stay read-only, because Asana calculates them. Your team tracks Priority, Budget, Client and Effort in Asana custom fields. The weekly report lives in Google Sheets™. So every Friday somebody copies those 4 columns across by hand, and every Friday one of them comes out wrong. An Asana custom fields export sounds like one job. It's really 10 small ones, because Asana has 10 kinds of custom field and each one behaves differently once it leaves Asana. A budget wants to stay a number. A multi-select wants to stay readable. A formula wants to stay out of the way. This guide goes type by type, from what Asana stores to what lands in the cell and what can travel back. Sources are Asana's help center and pricing page, checked on 21 October 2026. ## The short answer Asana has text, number, currency, percentage, single-select, multi-select, date, people, formula and reference fields. All of them can land in a spreadsheet as plain, readable values. Number fields stay numbers, so `SUM` and `AVERAGE` work on them. Select fields arrive as the option's name. Formula fields arrive as their result and you can't edit them from the sheet. 2 plan gates matter before any of that. Custom fields only exist on paid Asana plans, Starter and up. Formula fields need Advanced or higher. ## Asana plans with custom fields On the free Personal plan there are no custom fields at all. Asana's help page on field types lists Starter, Advanced, Enterprise and Enterprise+, and the CSV import guide says it plainly: "Custom fields are only available with a paid subscription." | Asana plan | Price per user, per month | Custom fields | Formula fields | | --- | --- | --- | --- | | Personal | $0 | No | No | | Starter | $10.99 billed annually, $13.49 monthly | Yes | No | | Advanced | $24.99 billed annually, $30.49 monthly | Yes | Yes | | Enterprise and Enterprise+ | Contact sales | Yes | Yes | So if a project shows no Priority column at all, check the plan before you check the export. A free workspace has nothing to export. Our post on [Asana free plan limitations](/blog/asana-free-plan-limitations) lists the other reporting features that start at Starter. ## Asana custom field types, cell by cell This is the table to keep open. The last column applies to two-way sync, where edits in the sheet go back to Asana. | Asana field type | What it holds | What lands in the cell | Edit from the sheet? | | --- | --- | --- | --- | | Text | Up to 1,024 characters | The text, as typed | Yes | | Number | A plain number with set decimals | A number Sheets can add up | Yes | | Currency | A number with a currency code | A number, ready for `SUM` | Yes | | Percentage | A number shown as a percent | A number, ready for `AVERAGE` | Yes | | Single-select | One option from a list | The option's name, such as High | Yes, if the value is an existing option | | Multi-select | Several options from a list | The chosen names, together in one cell | Yes, existing options only | | Date | A date, or a date and time | A date | Yes | | People | One or more Asana users | The people's names | Yes | | Formula | A value Asana works out | The result | No, Asana calculates it | | Reference | Links to tasks or projects | The linked names | Yes | A few of these need a sentence more. **Currency and percentage are numbers wearing a format.** In Asana they're both number fields with a display style on top. That's good news for reporting. A budget column of 4,250 and 1,180 sums like any other number, and you can format the column as dollars in Sheets. **Single-select is the one people mean by "status" or "priority".** The cell holds the option's name. If you type a new word into that cell during a two-way sync, Asana has nowhere to put it. It only accepts one of the options already set up on the field. Add the option in Asana first. **Multi-select puts several names in one cell.** That reads well and filters badly. A plain `COUNTIF` can't count a task tagged Design and Copy under both. Use a wildcard instead, such as `=COUNTIF(F:F, "*Design*")`. **Date fields can carry a time.** A time can move the date by one day once it reaches a sheet set to another time zone. Check the sheet's time zone under File, then Settings, if dates look a day off. **Formula fields stay read-only.** Asana works the value out from other fields. A sheet can show it and chart it. It can't overwrite it, so a two-way sync leaves those cells alone. ## Priority, points and effort are custom fields too Asana has no built-in priority. It has no story points either. When your project shows a Priority column, somebody on your team created a single-select field and called it that. The same goes for Story points, which is usually a number field. That has 2 effects on any export. The column name is whatever your team typed, so "Priority", "Urgency" and "P-level" are all possible. And if a project never had the field added, its tasks come through with nothing in that column. That gap means the field isn't on that project. It doesn't mean nobody set it. Estimated time is the odd one. Asana stores it as a number field shown as a duration, in minutes, and it only exists on plans with time tracking, which means Advanced and up. A task estimated at 1 hour 30 minutes is 90 in the underlying field. Divide by 60 in the sheet to get hours. ![Screenshot of an Asana project named Website Relaunch in List view, with tasks grouped into To do and In progress and columns for Assignee, Due date, Priority, Effort (pts), Budget and Team](/images/product/asana-before.png) ## Field types Asana doesn't have People moving from other tools look for these and don't find them. Asana has no checkbox field, no star rating, no progress bar, no location field and no signature field. There's no attachment field either. Asana keeps files as attachments on the task itself. Teams work around each gap in Asana before any export happens. A yes or no question usually becomes a single-select with 2 options. Progress usually becomes a percentage number field. Whatever your team built is what lands in the sheet, because the export can only carry what Asana holds. ## 3 routes for an Asana custom fields export **CSV export.** Open the project's dropdown menu, then Export, then CSV. It works on every plan and costs nothing. Asana doesn't publish the current column list, though, and doesn't say whether every custom field type makes it into the file. Open your own file and check before you build a report on it. And it's a snapshot. Next Friday it's stale. Our [Asana CSV export](/blog/asana-csv-export) post covers what else to watch for. **Asana's own Sync to Google Sheets.** Asana makes a Google Workspace™ add-on called Asana Exports. It needs Advanced or higher, stops at 500 rows and only pulls data into the sheet. Fine for a small project on a plan that already includes it. The full breakdown is in our post on [Asana's native Google Sheets sync](/blog/asana-native-google-sheets-sync). **A sync add-on.** Our [Asana to Google Sheets](/) add-on, Asana to Sheets, runs in the Sheets sidebar. Pick a workspace, a team and a project, and the custom fields come across as their own columns alongside name, section, assignee and dates. Starter is $9 a month for up to 3 manual syncs. Pro at $19 refreshes every 3 hours. Business at $39 adds two-way sync, so a changed budget or priority in the sheet goes back to the task. | | CSV export | Asana's Sheets sync | Sync add-on | | --- | --- | --- | --- | | Asana plan needed | Any | Advanced or higher | Starter or higher for custom fields | | Stays current | No | Every few hours | Every 3 hours on Pro, seconds with live sync on Business | | Edits go back to Asana | No | No | Yes, on Business | ## Building reports on custom field columns Keep the synced tab as it is. Don't delete or reorder its columns. Resizing and hiding are safe. Then build on a second tab. A few patterns that work well with custom fields: - High-priority tasks per person: `=COUNTIFS(Synced!E:E, "High", Synced!C:C, "Dana")`, where E holds Priority and C holds the assignee. - Budget by client: a pivot table with Client as rows and Budget as a summed value. - Overdue high-priority work: `=FILTER(Synced!A:H, Synced!E:E="High", Synced!D:D