Migrating from Jira, GitHub or another Trello board

Three exports need no hand editing. A GitHub issues JSON dump maps itself, with title, body, labels, assignees and state all matched. Jira exports expand one level so fields.summary and fields.status become mappable columns. A Trello board export resolves list ids, labels, members and checklists, and skips archived cards.

By James Folk, who built this Power-Up. Last reviewed August 2026.

Three exports are common enough to be handled without any hand editing.

GitHub issues

Export with the GitHub CLI:

gh issue list --state all --limit 500 --json number,title,body,state,labels,assignees,milestone > issues.json

Drop that file straight in. It maps itself: title becomes the card title, body the description, labels the labels, assignees the members and state the list. Nothing to correct.

Assignees only attach if that GitHub username matches a member of the Trello board, which it usually will not. Either add the people to the board first, or set Members to Do not import and assign afterwards.

Jira

Export issues as JSON, or use the REST API. The useful fields are nested under fields, and those are expanded one level for you, so you can map fields.summary to the card title, fields.status to the list, fields.duedate to the due date and fields.labels to labels.

Jira CSV exports work too and are often simpler, because the columns are already flat.

Two things worth deciding before you import: whether Jira's statuses should become your Trello lists as they are, or be collapsed into the five kanban columns, and whether to bring the full description across or start clean.

Another Trello board

Open the source board, choose Print, export and share, then Export as JSON. Drop that file in.

List ids are resolved back to list names, labels and members come across, and checklists are rebuilt. Archived cards are left out, since you almost never want them in a fresh board.

This is the quickest way to clone a board's content into a new board, or to rebuild a board someone archived.

What does not come across

Card comments beyond the first, attachments as files rather than links, card covers, custom fields, activity history and card links between boards. If a migration depends on those, say so and we will look at it.