Trello JSON vs CSV exports: check comments, archives and recovery scope

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Define what must survive

Trello documents board export to JSON for board members, with CSV available for boards in Premium Workspaces. Its export guide says JSON and CSV cannot currently be imported to recreate a board. Treat export and full restoration as different requirements.

The same guide explains important scope differences: CSV excludes comments, the standard CSV download excludes archived cards, and board JSON includes the most recent 1,000 actions. Workspace export offers another scope and an option to include raw attachments. Check current permissions and plan availability before relying on that route.

A fictional project handover

Assume an agency needs to hand over an eight-card project. Six cards are active and two archived; three cards contain review comments and two have files. A spreadsheet containing six rows might be correct for one export option yet incomplete for this handover.

Write the required evidence first: all eight card references, the review history needed for the engagement and accessible copies of the agreed files. These are example requirements, not a claim that an export has been performed.

Create an evidence inventory

• Cards: identify the expected active and archived populations separately.
• Comments: decide whether recent activity is enough or older discussion matters.
• Attachments: distinguish file content from a URL pointing back to Trello.
• Context: retain the board name, export date and scope selected.
• Recovery: state which destination and reconstruction steps would be needed.

Inspect a sample before accepting the file

1. Choose one active card, one archived card and one card with a known review comment.
2. Export through the supported option available to your authorized account.
3. Open the output in an appropriate local viewer and locate each sample.
4. Inspect the required comment and file content, rather than only their presence as headings or links.
5. Compare the whole expected card population with the output.
6. Document omissions and choose a different scope when necessary.

Make attachment handling explicit

Our advice is to distinguish an evidence package that can be read independently from an index of resources that still require service access. If attachments are represented by links, record who can open them and what happens after access changes. Do not distribute a raw export more broadly than the information it contains permits.

For an audit or handover, keep a short readme describing how the export was produced and what was intentionally excluded. A large file size does not prove complete history, and successful download does not demonstrate future restoration.

Acceptance criteria

Accept the package when its declared scope matches the reader's needs, representative records and files can be inspected, and limitations are documented. If restoration is required, validate a separate supported recovery process with synthetic data before depending on it. This article provides an editorial verification method; it does not certify a backup, perform an export or claim every Trello object can be reconstructed from the downloaded files.