What data is missing when copying a Trello board compared to exporting its JSON for rollback?
0 reputation · 07 Jun 2020, 16:27 UTC
0 reputation · 07 Jun 2020, 16:27 UTC
Teams preparing for high‑risk board changes need a reliable snapshot that can be used to roll back to a known state if the change introduces problems.
Because Trello is a cloud‑only service, the only user‑controlled options are creating a board copy or downloading a board‑level JSON export. Documentation confirms that a copy duplicates lists, cards, descriptions and labels, but it does not guarantee preservation of comments, activity history, attachment fidelity, checklist items or custom fields, and workspace limits may block the copy operation. The JSON export captures cards, lists and metadata at a point in time, yet Trello does not provide a documented one‑click restore path from that file, and it is unclear whether all board elements are included in the export.
Which specific board elements (comments, activity history, attachments, checklists, custom fields) are retained in a copied board? Does the JSON export contain all necessary data to reconstruct a board’s state, and is there a documented method to import it back into Trello?
35275 reputation · 08 Jun 2020, 02:55 UTC
When you copy a Trello board, the duplicate retains lists, cards, card descriptions, labels, checklists, attachments and custom fields, but it does **not** copy card‑level comments or the board’s action/activity history. The JSON export (Board → More → Print and Export → JSON) includes lists, cards, descriptions, labels, checklists, attachments, custom fields and the comments that belong to each card, yet it omits the action history array and Trello provides no native import function to rebuild a board from that file.
Trello’s copy operation is designed to create a reusable template, so it strips mutable audit data (comments and action log) to keep the artifact lightweight and privacy‑focused. The JSON export aims to give a portable snapshot of the board’s current state; it retains the mutable content (comments) but deliberately excludes the action log for the same reasons, and because there is no native restore path, rebuilding a board from the JSON requires custom scripting via the Trello API.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.