Export a Trello Board and Check What the File Preserves

Images are reused AI-generated editorial illustrations, not documentary photographs or verified product screenshots.

A Trello export is a snapshot with a defined scope, not a promise of one-click recovery. Start by deciding whether you need a spreadsheet for a handoff, nested data for an archive, comments, archived cards or the original attachment files. Those requirements lead to different export choices.

Choose the export for the job

Single-board JSON: structured data, bounded history

According to Atlassian’s export documentation, all board members can export raw JSON. A board JSON export contains the 1,000 most recent actions, which includes comments; it should not be described as the complete comment history of an older, busy board.

Board CSV: a spreadsheet, not the conversation archive

CSV export is available for boards in Premium Workspaces. Comments are not included. The normal CSV export includes cards that are not archived. Atlassian documents appending .csv to the board URL as a way to download both open and archived cards for this export workflow. Confirm your access, plan and result rather than assuming every spreadsheet has the same scope.

Workspace export: broader scope and optional attachment files

Premium Workspace exports can include board CSV and JSON data. Only Workspace admins can create and download these exports from Workspace settings. Select Include raw attachments when original attachment files are required; without that option, an export can contain hosted attachment links instead. For all comments, Atlassian directs readers to the Workspace export option.

Export a board step by step

Confirm permission. Check that you are on the correct board and are allowed to copy the data. Card descriptions, comments and attachments can contain client or personal information.
Record the scope. Note the board, export date, intended use, required archived cards, required comments and required attachment files. Keep that note with the archive, not in a public comment.
Open the board menu. Choose Print, Export, and Share, then an export option that your plan and role provide.
Save the file to a controlled location. Avoid public sharing links and unreviewed online JSON converters for confidential exports.
Inspect before signing off. Open representative active and archived cards, inspect the relevant comment history and confirm whether attachment bytes—not just URLs—were saved.

For a Workspace export, open the Workspace’s Settings → Export area as an authorized Workspace admin. Review the export options and archive contents separately from a single-board export.

Run an offline structural check

The free Trello export inspection practice ZIP contains a readable Python inspector, synthetic checks, recorded results and a README. No signup or third-party Python package is required. Review the files first. Use Python 3.9 or newer on a trusted computer; do not upload a private board export to this website.

python3 check_fixture.py
python3 inspect_trello_export.py /path/to/board.json

The inspector counts cards, archived cards, lists, action entries, comment actions and attachment entries. It flags cards whose list ID is absent from the supplied list data. It prints counts rather than card names, comments or attachment URLs, makes no network calls, does not download attachments and does not modify the export.

The checker rejects a missing section instead of silently calling it an empty board. A successful summary means the supplied file matched the script’s expected structure; it does not establish that the export includes every source record or can recreate the board.

What was actually tested

On October 31, 2026, six synthetic checks were executed in an AI-assisted Linux environment using CPython 3.13.15. They checked known counts, an unresolved list reference, invalid top-level data, missing sections, a non-object card, a non-boolean archive flag and a valid empty-board case. The combined count/reference expectation is one check. All six checks passed.

The synthetic example has three cards: two open and one archived; two action entries, of which one is a comment; one attachment entry; and one card referring to a list not present in the file. These are invented fixtures, not observations from a live Trello account.

No live Trello export, Workspace ZIP, actual attachment download, large-file performance test or production restore was tested. The inspector reads the whole JSON file into memory. Unsupported or unusually large files need a different review rather than a forced success.

Use a handoff verification record

Copy this outline into your team’s private handoff note. It makes missing evidence visible without treating a count as proof of completeness.

Purpose and owner: who needs the archive, who may access it and who approves completion.
Scope and time: board or Workspace, export time, selected format and relevant plan or role.
Cards: which active and archived examples were compared with the source.
History: which comments are required and whether the selected export includes them.
Attachments: whether original files were saved, which samples open offline and whether linked external resources remain separate.
Recovery: what reconstruction procedure exists, what has actually been tested and what remains unverified.
Handling: approved storage, access, retention and any separately controlled encryption or recovery keys.

A realistic example

Illustrative scenario: a freelancer hands off a completed client project. The client needs archived work, approval comments and final design files. A normal CSV does not meet that requirement: it omits comments and its ordinary export view omits archived cards. A Workspace admin reviews a Premium Workspace export with raw attachments, checks selected archived cards and approval comments, opens sampled files offline and records any gaps. This is a decision example, not a report of a performed Trello test.

Common questions

Can JSON or CSV be imported to recreate the board?

Atlassian says it is not currently possible to import these export formats directly to re-create a Trello board. Do not label an untested reconstruction plan as a verified restore.

Does an attachment count prove that files were downloaded?

No. A JSON attachment entry or URL is metadata. Inspect the actual saved files and the Workspace export options when offline file retention is required.

Why might a JSON view look more complicated than a spreadsheet?

Cards can have several comments, checklist items and action records. These one-to-many relationships do not fit neatly into one spreadsheet row. Atlassian’s JSON guide explains this nested structure.