Move your Trello boards into Fareeqy

Not automatically. A long-running Trello board can contain more archived work than active work, so closed Lists and Cards stay out unless you choose to include archived items during upload. Turn that option on and those records appear in the preview before confirmation. Leave it off and the importer reports that archived Trello content was excluded, so its absence cannot look like a silent parsing mistake.

The choice applies at every Trello level. A closed Board does not create a project by default, a closed List does not become a task list, and a closed Card cannot crowd the current work. With inclusion enabled, positions recorded by Trello preserve List and Card order, while descriptions, due dates, comments, and Checklists return according to the JSON. A genuinely empty Board inside a larger workspace upload still does not create a useless empty project.

Archiving is not completion in Trello. Only dueComplete decides whether a Card arrives as a finished task, using its due time as the completion time when available. Sitting in a List called Done is insufficient because List names are editable and may describe a stage rather than a state. An active Card can therefore arrive completed, while an archived Card included on request can still arrive open. The importer reads the file's explicit flag instead of inferring meaning from a column title.

This also matters on a later export. Migration records use Trello Board, List, and Card identifiers to recognize work that already arrived. The preview keeps edits made inside Fareeqy and adds new Cards to the existing project and task list. Including archived content does not turn the importer into an update that rewrites old records over current work; it decides which exported Trello objects enter the candidate set before comparison and creation.

The importer distinguishes two kinds of Trello attachment. An external link remains clickable in a links section inside the task notes, using the name shown on the Card. A file uploaded into Trello is different: its bytes are not present in the JSON and its download URL needs permission from your Trello account. We do not create a fake file that nobody can open, and the preview names that loss before confirmation.

A link keeps its Card context. The parser examines Card attachments, accepts a real web address, retains the attachment name your team supplied, and places it under a links heading after the description and flattened details. It does not turn that link into a project file detached from the task that explains why it matters. If the attachment has no label, the address itself remains as the link text rather than creating an unnamed row.

An uploaded attachment is technically different because Trello's isUpload flag means the content is stored behind that account's session. The export describes it but contains no bytes Fareeqy could upload. Keep access to the old Trello workspace if those files must be downloaded manually, and review the does-not-transfer list before confirming. Comments, Checklists, and Labels do not depend on fetching attachment bytes; the importer reads them from other parts of the JSON and keeps them with the task.