Import a Trello board
into Noots.
Connect with a Trello API key and token, pick a board, and Noots reads it through the Trello API and builds the project here. Closed boards, archived lists and archived cards are all left out.
How a Trello import runs.
Nothing is written back, nothing keeps syncing, and your credentials are not kept.
Connect
Paste the credential the import wizard asks for. It is used for that request and discarded.
Pick
A Trello board that the token's owner can see. Closed boards are filtered out.
Import
One column per open list, in the board's own order. Archived lists are not read.
Mapped, field by field.
- The card name becomes the task title.
- The card description comes across exactly as written, including its markdown, up to four thousand characters.
Completion follows the column, not a flag. A card arrives in a column named after the one it was in, and it counts as complete only when that name is one this product already treats as done.
Left behind, on purpose and in full.
- Card members and assignees
- The due date itself, though a card marked complete on its due date is read
- Start dates
- Labels and their colours
- Checklists and checklist items
- Attachments, covers and comments
- Custom fields, watchers and the card's short link
- Priority: Trello has no priority field, so cards arrive at the default priority
If one of these is the thing you cannot lose, export a CSV and use the paste importer instead. It is on every plan and it maps an assignee and a due date, which the live importer does not.
The ceilings a big workspace will meet.
Measured from the importer itself rather than estimated. A migration that quietly stops at a limit is worse than one that tells you the limit first.
- A board is read in one request rather than page by page, and a very large board can exceed the response size the importer accepts. When that happens the import fails cleanly and creates nothing, rather than importing half a board.
- The board picker is a single request with no page size of its own.
- An import is a one-off copy, not a running sync. Nothing is written back to the source, and running the same import twice creates a second project with the same tasks in it.
- Your credentials are never stored. They travel with the request, make the calls and are discarded; there is no token table behind this.
- There is no undo. If an import is wrong, delete the project it made and run it again.
- Every import writes an audit row: which source, how many columns, how many tasks, who ran it and whether it finished cleanly.
- The person who runs the import becomes a manager on the new project, and the project takes your organisation's default visibility.
Moving from Trello.
Do checklists come across?
What about archived cards?
Is my Trello token stored?
Start on the free tier.
Import into a free workspace first and look at the result before anybody pays for anything.
No card for the free tier. 10 people and 10 projects.