Import a monday.com board
into Noots.
Connect with a monday.com API token, pick a board, and Noots reads it through monday's GraphQL API and builds the project here. This is the thinnest of the five importers and the section below says exactly how thin.
How a monday.com 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 monday.com board. Noots lists a hundred active boards, most recently used first, with an item count beside each.
Import
One column per group, in monday's own order.
Mapped, field by field.
- The item name becomes the task title.
- The group becomes the column.
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.
- Every column value without exception: status, person, date, timeline, numbers, text, dropdown, tags, checkbox, formula, mirror, dependency and files
- Updates and comments
- Subitems
- Files and the board description
- The item creator, its timestamps and the link back to monday.com
- Descriptions: nothing on a monday.com item becomes a task description
- Priority: items 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.
- Up to two thousand five hundred items per board. A larger board is cut off at that point without a warning on screen.
- The board picker shows the hundred most recently used active boards, not all of them.
- 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 monday.com.
Why does so little come across?
How do I bring the column values?
Does it keep syncing?
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.