Switch from Trello to BugBoard
Connect Trello, choose the boards, say who is who, and the import runs in the background. Cards, comments, labels and checklists come across. Your Trello boards are not touched.
Who this is for
- Teams that used a Trello board as their bug list and want issue types, a triage column and a coding agent on the same board.
- Anyone who wants to try BugBoard on real data before deciding: the import only reads from Trello, so you can run it and keep both.
What you need
- A BugBoard account. The Free plan is enough to try one board; a larger team needs a larger seat package.
- A Trello API key and a token from the account that can see the boards. The wizard links to where Trello issues them.
- A few minutes to match Trello members to your BugBoard team. Trello never shows other members’ email addresses, so this step is by hand.
Three steps
Connect
Open Settings, then Import, and choose Trello. Paste the key and token. BugBoard lists the boards the token can see and scans them, so you know how many cards and comments to expect before anything is written.
Map
Choose the boards. Each Trello list becomes a column. Match each person to a BugBoard member, invite them by email, or leave their assignments out. The wizard will not continue while a person is undecided, because an undecided person would silently lose their cards.
Import
Start the run. It works in slices, keeps its place, and can be resumed if it stops. When it finishes, the report compares what Trello held with what BugBoard now has, and lists anything skipped.
What maps to what
| Trello | BugBoard |
|---|---|
| Board | A new project. Each board you pick becomes its own project; an import never merges into an existing one. |
| List | A board column. The list name is the status. |
| Card | A task, with its original dates. |
| Labels | Tags, with their colours. A label with no name becomes a tag named after its colour, so it stays visible. |
| Members | Assignees, through the mapping you set in the wizard. |
| Checklists | Checkboxes in the task description. A switch turns checklist items into subtasks instead; it is off by default because items have no comments or attachments of their own. |
| Comments | Comments, in order, with their original dates. |
| Attachments | Files uploaded to Trello are copied, within your plan’s storage. A link to another site is kept as a link. |
| Archived cards | Imported as archived when the card, its list or its board is archived in Trello. |
| Custom fields | Mapped, not recreated: to a native field, to tags, to the description, or skipped. |
Limits
- Trello has no priority, so priorities stay empty unless you map a custom field to one.
- One new project per board. You cannot merge a board into a project that already exists.
- Re-running an import resumes it. It does not sync: changes made in Trello afterwards do not follow.
- Dependencies stored by Power-Ups are not read.
- Trello limits how fast its API answers, and the import keeps to that limit, so a large board takes longer.
Before you decide, read the BugBoard and Trello comparison or the overview of all imports.