Migrate
Statuses, priorities, labels, sub-issues: Linear's CSV imports 1:1 into a Tasks list.
Launching soon: this surface is rolling out
| Linear | In idapt | How |
|---|---|---|
| Issues (title, description, dates) | Tasks, with a provenance line linking back to the Linear ID | Automatic |
| Statuses & priorities | 1:1. Backlog/Todo/In Progress/In Review/Done/Canceled/Duplicate and Urgent→Low map by name | Automatic |
| Labels | List labels (find-or-create) | Automatic |
| Sub-issues (parent links) | Sub-tasks | Automatic |
| Assignees | Matched to workspace members by email or exact name; unmatched stay unassigned | Automatic |
| Issue numbers (ENG-123) | New list-scoped numbers; the original ID is kept in the description | Manual |
| Cycles, projects, estimates, comments | Not in this importA full-fidelity API-token import is on the roadmap. | Planned |
In Linear: team → ⋯ → Export CSV (or workspace settings → Export). You get one CSV per selection.
Open the target list → ⋯ menu → "Import from Linear (CSV)". Up to 2,000 rows per upload; the summary reports imported/skipped/errors.
Imports dedupe on the Linear ID: re-uploading the same CSV (or next week's fuller one) only adds what's new.
Yes. 'Parent issue' links become sub-tasks in a second pass, with a cycle guard for malformed data.
Task numbers are list-scoped and minted fresh (LIN-1, LIN-2, …). Every imported task's description ends with 'Imported from Linear ENG-123' so old references stay findable via search.