How to export data from Trello: JSON, CSV and migration
You can export any Trello board as JSON. CSV export is available for boards in Premium Workspaces, and Premium Workspace admins can export every board together. If your goal is to move projects rather than create a backup or spreadsheet, a direct importer can avoid the export-file step and preserve more of the working structure.
This guide covers Trello's built-in export options, what each format leaves out, and how to move a board directly into Breeze. Trello's export and print behaviour was checked against Atlassian's official documentation on August 13, 2026.
1. Which Trello export method should you use?
Use JSON when you need structured board data, CSV when you need a spreadsheet, and a full Workspace export when you need a proper account backup. For a tool-to-tool move, check whether the destination can connect directly before spending time converting files.
| Method | Who can use it? | Best for | Main limitation |
|---|---|---|---|
| Board JSON | Any board member | Structured data, technical work and compatible importers | Hard to read manually; board actions include only the 1,000 most recent actions |
| Board CSV | Members of a Premium Workspace | Excel, Google Sheets, reporting and simple records | Comments are excluded; archived cards are excluded from the normal download |
| Full Workspace export | Premium Workspace admins | All-board backups and complete comment history | Produces files rather than a ready-to-use project in another tool |
| Print or PDF | Anyone who can open the board | A human-readable snapshot for a client or an archive | Board printing covers card fronts only, so descriptions are lost; no destination tool can import it |
| Direct Breeze import | A Trello user with access to the boards | Moving active projects without file conversion | Attachments become links; Trello automations still need separate review |
2. How do you export one Trello board as JSON or CSV?
Open the board menu, select Print, Export, and Share, then choose JSON or CSV. JSON is available to every board member; the CSV option appears for boards in Premium Workspaces.
Export a Trello board as JSON
- Open the Trello board you want to export.
- Open the board menu.
- Select Print, Export, and Share.
- Select Export as JSON.
- Save the JSON page or file to your computer.
JSON is machine-readable and keeps nested information that does not fit spreadsheet rows, but it is not a practical way to review a large board by hand. Use a compatible importer, a JSON viewer or a script.
Export a Trello board as CSV
- Open a board in a Premium Workspace.
- Open the board menu.
- Select Print, Export, and Share.
- Select Export as CSV.
- Open the downloaded file in Excel, Google Sheets, Numbers or another spreadsheet tool.
CSV is the better choice for filtering, reporting or creating a simple offline record. It is not a complete copy of the board: comments are not included, and the normal CSV download includes only cards that are not archived.
Need archived cards in the CSV? Atlassian documents a separate shortcut: open the board, add
.csvto the end of its URL, and load that address. This download includes open and archived cards.
3. How do you export all Trello boards and attachments?
A Premium Workspace admin can export every board in the Workspace as CSV and JSON. This is the better native option when you need a full backup, all comments, or the original attachment files.
- Open Trello while signed in.
- Find the Workspace in the left navigation and open Settings.
- Select Export.
- Create a new export or download an export that has already finished.
- Select Include raw attachments when creating the export if you need the actual files rather than links.
Only Workspace admins can create and download this export. If you are a board member but not an admin, you can still export an individual board as JSON, but you cannot create the full Workspace package yourself.
4. How do you save a Trello board or card as a PDF?
Trello has no PDF export. The route is its print view plus your browser's Save as PDF print destination, and what you actually get depends on whether you print a whole board or a single card.
Print a whole board
- Open the board menu.
- Select Print, export, and share.
- Select Print.
- In your browser's print dialog, set the destination to Save as PDF.
One limit is worth knowing before you rely on this. Atlassian is explicit that "Printing a board will print the front of every card on the board. It won't include details from the back of cards." You get card titles, labels and badges laid out by list - and none of the descriptions.
Print a single card
- Open the card.
- Open the actions menu and select Share.
- Select Print, then save as PDF from the browser dialog.
A card print does include the card back "and however much of the description is visible", which makes two things worth doing first: open the comments and activities section if you want the discussion included, and select Show more under a long description so it is not cut off at the fold.
Printing is not available in the Trello mobile app. And because the output is a page layout rather than structured data, a PDF is a reasonable status snapshot or an archive a client can read, but it is the one option on this page that no destination tool can import.
5. What does a Trello export leave out?
No single format is perfect for backup, reporting and migration. The gaps depend on which method you choose.
- Board JSON limits comment history: comments are stored as board actions, and the board export includes the 1,000 most recent actions. Use the full Workspace export when you need all comments.
- CSV excludes comments: it is useful for card-level reporting, not conversation history.
- Normal CSV excludes archived cards: use Atlassian's documented
.csvURL method when those cards matter. - Attachments are not automatically raw files: select Include raw attachments during a full Workspace export if you need an independent copy.
- Inbox cards cannot be exported directly: move them to a board before exporting.
- Automations and Power-Ups require a separate plan: moving card data does not recreate Butler rules, connected apps or another tool's equivalent workflow.
Before closing a Trello account, keep both a full backup and a short inventory of automations, Power-Ups and externally hosted files. A successful data export does not prove that the new workflow behaves the same way.
6. How do you migrate a Trello board to Jira, Asana or monday.com?
Most destinations read a Trello board directly, so you rarely need the export file at all. What differs is how much of the board survives the trip, and the gaps are wider than the marketing pages suggest. One rule holds everywhere: a CSV-based migration cannot carry comments, because Trello's CSV does not contain them.
| Destination | How you move | The limit that catches people out |
|---|---|---|
| Jira | Built-in Trello importer | Org admins only; without a software space, checklists and custom fields are dropped |
| Asana | CSV import | Comments are absent from Trello's CSV, so nothing can recover them |
| monday.com | Built-in Trello importer | Names, labels and dates only - descriptions and checklists are not supported |
| Breeze | Built-in Trello importer | Attachments arrive as links rather than copied files |
Trello to Jira
Jira and Trello are both Atlassian products, so Jira ships its own importer at Settings → System → External system import → Trello. Cards become work items and lists become workflow statuses. You need to be an org admin to run it.
How much arrives depends on which kind of Jira space you land in. With a software space, checklists become sub-tasks and archived cards import as Done. Without one, Atlassian's own documentation is blunt about the losses: "Any checklists created in Trello won't be imported", "Any custom fields created in Trello won't be imported", and archived cards and lists are skipped. The documented field mapping does not mention comments or attachments at all, so run a pilot board and check rather than assuming they came across.
Trello to Asana
Asana has no direct Trello importer, so the route is the CSV file from section 2. Asana's CSV import reads task name, description, section, assignee and collaborators, which a Trello CSV maps onto reasonably well. The problem is upstream rather than in Asana: because Trello's CSV omits comments and archived cards, no amount of column mapping brings them back. Going the other way is a different problem again, because Asana exports JSON as well as CSV but only reads CSV back in - see exporting from Asana.
Trello to monday.com
monday.com has a built-in importer under your profile picture → Import data → Trello, capped at 10,000 rows per run. It is also the most lossy of the three. monday.com lists exactly three supported Trello fields - task name, label and dates - and names description, checklists, activities and files as unsupported. A board whose value sits in its card descriptions will arrive close to empty. Worth reading what monday.com will and will not let you export before you commit to it as a destination, because archived boards and workdocs are outside every route it offers.
Destination importers were checked against each vendor's documentation on August 13, 2026.
7. How do you move Trello projects directly into Breeze?
You do not need an export file at all. Breeze connects to Trello with read access, lets you choose the boards, shows what will be imported, and leaves the original data unchanged. Import a whole Workspace as new projects, or bring one board into a project you already created - the full process is in the Breeze import guide.
Import a Trello Workspace as new Breeze projects
In Breeze, open the menu in the top-right corner, select Settings, open the Import tab and select Import next to Trello. The wizard then runs in four steps.
- Connect. Trello opens a window so you can give Breeze read access.
- Choose. Pick the boards to import. Each one becomes a Breeze project.
- People. Match Trello members to Breeze teammates. Anyone you leave unmatched is assigned to you.
- Review. Check what is about to happen, then select Start import.
Only a Breeze account owner or admin can import a whole Workspace as new projects.
Import one Trello board into an existing Breeze project
- Open the Breeze project and open project settings from the three-dot menu.
- Open the Import tab and choose Trello.
- Choose one Trello board.
- Breeze matches Trello lists to existing Breeze lists by name and creates any list that is missing.
- Review the import and start it.
What comes across from Trello?
| Trello | Breeze | Import behavior |
|---|---|---|
| Board | Project | Each selected board becomes a project, unless you import it into an existing project |
| Lists | Lists | Order is retained; missing lists are created when importing into an existing project |
| Cards | Tasks | Names, descriptions, due dates and assignees are imported |
| Labels and custom fields | Tags and custom fields | Supported values are carried across |
| Comments and checklists | Comments and checklist items | Checklists become checklist items on the Breeze task |
| Attachments | Attachment links | Breeze adds a link to the Trello file rather than copying the original file |
Large imports continue in the background, so you can close the window and keep working. Breeze emails you when the import finishes and reports anything it could not bring across.
If you import the same board later, Breeze can update the project created by the earlier import. It adds new tasks, comments and checklist items and refreshes changed tasks. It does not delete work you added in Breeze.
8. How do you move from Trello without losing important context?
Run one representative board as a pilot first - it verifies both the data and the new working habits before the old system goes read-only.
- Create a separate backup: use Trello's full Workspace export with raw attachments when your plan and permissions allow it.
- Choose a representative board: include comments, checklists, labels, custom fields, members and attachments in the test.
- Inventory Power-Ups and automations: decide which rules are still needed and how they will work in the destination.
- Run the import: review the counts before starting and compare the finished project with Trello afterward.
- Test the daily workflow: create, assign, comment on, move and complete a task in the new project.
- Choose a cutover date: stop updating Trello after that date, but retain read access until the team has signed off.
If you are still deciding whether to move, compare the practical differences in Breeze vs Trello or review other Trello alternatives. Exporting data is useful even when you decide to stay because it gives you an independent backup and shows which parts of the workflow are portable.
Common questions about exporting Trello data
- Can you export a Trello board for free?
- Yes. Any board member can export a board as JSON. CSV export is available for boards in Premium Workspaces.
- Can you export Trello to Excel?
- Yes. Export the board as CSV from a Premium Workspace, then open the file in Excel. A CSV is useful for reporting, but it does not include Trello comments.
- Which tool keeps the most of a Trello board?
- It depends what your board holds. monday.com's importer supports only task name, label and dates. Asana goes through CSV, which cannot include comments. Jira keeps checklists only in a software space. Breeze carries labels, custom fields, comments and checklists, and links attachments back to Trello.
- Can a Trello export be imported back into Trello?
- No. Atlassian says Trello cannot currently use its JSON or CSV exports to recreate a board. Keep the export as a backup or use a destination tool that supports the data.
- Does Breeze need a Trello JSON or CSV file?
- No. Breeze connects directly to Trello with read access. You choose the boards and review what will move before the import starts.
- Does Breeze copy Trello attachments?
- No. Breeze adds stable links to Trello attachments instead of copying the files. Download a Trello Workspace export with raw attachments before closing the old account if you need an independent copy.
Export for the job you actually need to do
Use JSON for structured data, CSV for spreadsheets, a full Workspace export for backup. If you are moving active projects, a direct import skips the file step entirely.
See exactly what Breeze imports from Trello, then try Breeze with one representative board before moving the rest of the Workspace.



