Export tasks to CSV from Trello, Jira, Linear and Asana: what each file leaves out

To export tasks to CSV you need a different route in each tool. Trello gives CSV only to boards in Premium Workspaces, Jira Cloud supports up to 10,000 work items per CSV export, Linear caps a member's issue-view export at 250 issues, and Asana's project export lists eleven task columns. We read each vendor's help pages on October 25, 2026.

Export limits tend to surface the day you need the file: before a migration, an audit or a client report. This guide gives the click path for each tool, the cap you will hit, and what the CSV silently leaves out. The facts below come from the vendors' own documentation, dated where a date exists; the one judgment section is labeled as ours.

Export tasks to CSV: the four tools side by side

Here is what each vendor's documentation says, as of October 25, 2026. The details sit in the sections after the table.

"Not stated" is a finding, not a gap we filled with a guess. Where a vendor's page was silent on plans or caps, we say so rather than borrow a number from a third-party guide.

Trello: CSV is a Premium Workspace feature, JSON is for everyone

According to Trello's export documentation, any board member can export a board to raw JSON, while boards in Premium Workspaces can also be exported to CSV. On a free Workspace the answer to "can you export Trello to CSV on the free plan" is therefore no, not with the built-in tool.

To export one board:

1. Open the board menu.
2. Select Print, Export, and Share.
3. Choose an export option (JSON for any board member; CSV if the Workspace is Premium).

Three details decide whether the CSV is usable:

• Comments are not in the CSV. Trello states that comments aren't included in the CSV export, and recommends JSON for many-to-one data such as comments.
• Archived cards are skipped. The standard CSV includes only non-archived cards. Trello's workaround is to type .csv at the end of the board's URL in the browser and press Enter, which downloads a CSV with open and archived cards.
• Inbox cards cannot be exported. Move them to a board first.

JSON has its own ceiling: it includes the 1,000 most recent actions on a board, comments among them. For a complete comment history, Trello points to the Workspace-wide export, which needs Premium, is limited to Workspace admins, and can include raw attachments as a ZIP if you tick that option when you create it.

Trello also says it is not currently possible to import JSON or CSV to re-create a board. Treat the file as an archive or a data source for a spreadsheet, not as a restore point.

Jira Cloud: the limit is now 10,000 work items, not 1,000

Older guides say Jira exports stop at 1,000 issues. Atlassian's current article, titled Export over 10,000 work items in Jira Cloud and updated July 3, 2026, says the asynchronous Export CSV feature in the Issue Navigator supports exports of up to 10,000 work items. The same page marks the old trick of editing the pager/start URL parameter as deprecated as of March 2026.

The click path, per Atlassian's export documentation:

1. Search for the work items you want (Atlassian's article uses Filters, then View all work items).
2. Select the ••• (More actions) menu, then Export.
3. Choose a CSV option. The page lists "Export Excel CSV (all fields)" and "Export Excel CSV (current fields)", plus a filter-fields variant that appears only when you search with a saved filter.

Atlassian's advice is to refine your JQL so the result is small, select only the fields you need, and avoid the all-fields export, which it describes as much slower and producing large files. The export runs in the background and you get an in-product notification with a download link; large ones can take several minutes.

Exporting more than 10,000 work items

Atlassian's recommended method is to split the query with JQL:

1. Run your original JQL and note the total count.
2. Split by a field such as project, issue type, status or a date range. Atlassian says date ranges are the most flexible, and that created is the most predictable because it doesn't change.
3. Check each batch returns fewer than 10,000 results, then export each as CSV.
4. Merge the files, and confirm the batch totals add up to the original count.

One warning on the export page deserves attention: Atlassian advises against uploading the CSV to Google Sheets or Microsoft Excel because the file may execute macros, which it calls a potential security risk. The same article's first workaround opens results in Google Sheets or Excel through the Apps menu instead. In our view, it is sensible to look at a Jira CSV in a plain-text viewer first if it contains text typed by people outside your team.

Linear: three different caps depending on who you are

Linear's exporting data page separates the routes by role. Workspace admins (owners only, on Enterprise) can export all issue data from Settings, then Administration, then Import Export, using "Export data" at the bottom. Linear emails a download link that expires after 12 hours, and a toggle includes private teams. The action is logged in the audit log.

For a single view, use the Ctrl or Cmd plus K menu, or the dropdown in a project or custom view, and choose to export issues as CSV. The caps:

• Members: up to 250 issues at a time.
• Admins: views with up to 2,000 issues (owners on Enterprise).
• Guests: cannot export issues.
• Projects and initiatives: members and admins can export up to 200 at a time.

The CSVs include issue fields such as ID, title, description, status, assignee, labels, cycle and dates. Linear states that CSV exports don't include attachment files, though links may appear in descriptions. Comments are not listed as a CSV field; the Markdown copy option, by contrast, captures title, description, comments and customer requests. Teams can't be exported as CSV at all; Linear says to use its import feature to move them between workspaces.

If you need more than the CSV gives, the page says Linear's API can export issues, projects and other data, and that Airbyte or Google Sheets can sync Linear data for reporting.

Asana: a short CSV, and a page that is silent on plans

Asana's guide to exporting projects says to click the drop-down arrow in the project actions menu and select Export, then CSV. The spreadsheet includes Task ID, Creation Date, Completion Date, Last Modified Date, Name, Assignee, Due Date, Tags, Notes, Project Name and Parent Task for subtasks.

Two limits on what we can tell you. That page mentions no restriction by Asana plan, and shows no publication date beyond an editor's note that it has been updated. We also could not read the body of Asana's help-center article on importing and exporting projects: the page loaded with only its title and navigation. So we make no claim here about Asana's JSON export, comments, row caps or whole-organization exports. Check those in your own account before you plan around them.

Asana is one of the tools Upfynd lists in Task & Project Management, which had 589 products as of October 25, 2026.

Check the file before you cancel anything

This section is our judgment, not vendor guidance. A CSV that opens without errors can still be incomplete, so before you delete a board or close a workspace:

• Compare counts. Count open and closed tasks in the tool and rows in the file. Jira's own advice for split exports is to check the batch totals add up to the original count; the same habit works anywhere.
• Spot-check a card with comments. If the comments are missing, they will be missing for every card.
• Look for archived and private items. Trello's CSV skips archived cards by default; Linear's workspace export has a switch for private teams.
• Check attachments. Linear's CSV carries no attachment files, and Trello's attachments are links unless a Workspace export includes the raw files.
• Keep the raw export too. A JSON file or API pull holds fields a CSV flattens away, even if you never open it again.

Skip CSV entirely if your goal is to rebuild the same board elsewhere. Trello says it cannot import its own exports, and a flat spreadsheet is a poor container for a board's structure. In that case, we'd look for the destination tool's own importer.

Where to go after the export

If the export is the first step of a move, Upfynd's Task & Project Management category is the place to compare options, including Linear, ClickUp and Todoist. We did not cover ClickUp's export here: its help center returned an error to us on October 25, 2026, so we have nothing verified to say about it.

Upfynd product pages cover pricing and categories, so confirm import behavior in the destination's own documentation, and do it the same day you read the source's export documentation. Vendors change these pages, which is why every limit above carries its date.

If you build a task tool and your export is better than these, list it for free on Upfynd and say so on your page.