Trello export handoff: records, comments and files

Before choosing a format, privately agree the selected board, recipient, permitted scope and required records: active/archived cards, comments and usable files. A request for one board does not authorize a Workspace-wide handoff. Name who will inspect the result; an export control alone is not completion evidence.

Choose the documented route

Board members: JSON via board menu → Print, Export, and Share. Board CSV requires a Premium Workspace.

Board JSON includes only the latest 1,000 actions (including comments). CSV has no comments. For all comments, use JSON from Premium Workspace → Settings → Export; creation/download requires a Workspace admin. Include raw attachments puts original files in the ZIP; otherwise exports link to Trello attachments.

Ordinary CSV omits archived cards; the documented browser route appends .csv to the board URL to include open and archived cards. Inbox cards cannot be exported. JSON/CSV cannot re-create a Trello board by import. See Export data from Trello, especially comments, Workspace exports and spreadsheets.

Check files and access separately

Computer uploads create copies in Trello; cloud-service attachments can store links. Atlassian's uploaded-attachment authorization rule prevents sharing those links with people lacking board access, with an explicit public-board exception. See Add an attachment to a card, Note and Attachment security.

Treat externally linked documents as a separate access/copy question; selecting raw attachments does not prove their contents were copied. Do not change sharing permissions just to make a handoff appear complete.

Leave missing evidence visible

Write a private handoff checklist: required records, selected route, requester role/plan, authorized breadth, recipient access, inspection responsibility and unresolved gaps. Need all comments but lack the administrative route? Mark comments unmet; do not substitute recent actions or expand authorization. Until the actual files are inspected, contents, completeness and recipient usability remain unverified. Restoration and successful underlying work are separate questions.

For card-state cleanup, use the existing complete/archive/delete guide [current article].

Evidence: English Trello Cloud documentation read at 2026-10-05T14:26:35Z; no page update dates established. Source inspection and synthetic manual decisions only; no account, export, attachment, sharing or import action. A distinct same-operator checker reread both sources by 2026-10-05T14:31:11Z, rechecked sixteen author decisions and eight additional boundaries at 2026-10-05T14:32:42.369555Z; no independent review claimed. Recheck before use, after changed controls/plan/access requirements or by 2026-11-05T14:26:35Z. Feedback should identify the disputed requirement or route without board IDs or private files. This procedure follows the task-handoff standard [current article].