Import a Linear team
into Noots.
Connect with a Linear personal API key, pick a team, and Noots reads it through Linear's GraphQL API and builds the project here. Read access is enough.
How a Linear 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 Linear team. Noots lists the first hundred, with the team key and an issue count.
Import
One column per workflow state, ordered the way Linear orders them. Cancelled states get a column of their own rather than being folded into anything.
Mapped, field by field.
- The identifier and title become the task title, as ENG-42: Ship the thing.
- The description comes across exactly as written, including its markdown, up to four thousand characters.
- The priority is mapped from Linear's own scale. Urgent and High both arrive as high, Medium as medium, Low as low, and No priority is left at the default.
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.
- Assignee, creator and subscribers
- Due dates and estimates
- Labels
- Projects, project milestones and cycles
- Parent issues, sub-issues and issue relations
- Comments, attachments and links
- Triage state, SLA fields and every timestamp
- The link back to Linear
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 issues per team. A larger team is cut off at that point without a warning on screen.
- The team picker shows a hundred teams in one page, and up to fifty workflow states per team become columns.
- Completed and cancelled issues are imported like any other.
- 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 Linear.
Do cycles and projects come across?
What happens to Urgent issues?
Does it keep syncing with Linear?
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.