Import from Linear
The Linear importer migrates issues, workflow states, labels, priorities, assignees, and comments from a Linear team into a SetGet project. Because both Linear and SetGet use state-group-based workflows, the mapping is straightforward.
What gets imported
| Linear field | SetGet field | Notes |
|---|---|---|
| Issue title | Work item title | Direct mapping |
| Issue description | Work item description | Markdown preserved |
| Workflow state | State | Mapped via state table |
| Priority | Priority | Direct mapping (both use 5 levels) |
| Assignee | Assignee | Matched by email |
| Labels | Labels | Created if they do not exist |
| Comments | Comments | Imported with author attribution |
| Sub-issues | Sub-work-items | Imported as child items |
| Due date | Due date | Direct mapping |
| Estimate | Estimate | Direct mapping |
| Cycle | Cycle | Optional mapping |
Prerequisites
- A Linear account with access to the team you want to import.
- Admin or Owner role in your SetGet workspace.
Setup steps
Step 1 -- Connect to Linear
- Go to Settings > Import.
- Select Linear.
- Click Authorize with Linear.
- Linear's OAuth page appears. Click Authorize.
- You are redirected back to SetGet.
Step 2 -- Select the Linear team
- Select the Linear workspace from the dropdown (if you belong to multiple).
- Select the team to import.
- SetGet scans the team and displays: issue count, state count, label count, cycle count.
Step 3 -- Choose the target project
- Create new project -- uses the Linear team name.
- Import into existing project -- select an existing project.
Step 4 -- Map workflow states
Linear and SetGet both organize states into groups, making this mapping natural:
| Linear state group | Linear state (example) | SetGet state group | SetGet state (suggested) |
|---|---|---|---|
| Backlog | Backlog | Backlog | Backlog |
| Unstarted | Todo | Unstarted | Todo |
| Started | In Progress | Started | In Progress |
| Started | In Review | Started | In Review |
| Completed | Done | Completed | Done |
| Cancelled | Cancelled | Cancelled | Cancelled |
The importer auto-suggests mappings based on matching group names. Adjust as needed.
Step 5 -- Map priorities
Linear and SetGet both use five priority levels:
| Linear priority | SetGet priority |
|---|---|
| Urgent | Urgent |
| High | High |
| Medium | Medium |
| Low | Low |
| No priority | None |
This mapping is automatic and does not require manual intervention.
Step 6 -- Map labels
Linear labels are imported as SetGet labels. The importer creates any labels that do not already exist. If a label with the same name exists in SetGet, it is reused.
| Behavior | Description |
|---|---|
| Matching names | Reused without creating a duplicate |
| New names | Created with a default color |
| Label groups | Flattened (Linear label groups become individual labels) |
Step 7 -- Configure options
| Option | Description | Default |
|---|---|---|
| Import comments | Import issue comments | On |
| Import sub-issues | Import as child work items | On |
| Import completed issues | Include issues in Done/Cancelled states | On |
| Import cycles | Map Linear cycles to SetGet cycles | Off |
| Import estimates | Bring over estimate values | On |
Step 8 -- Start import
Click Start Import. Monitor progress on the real-time screen.
Post-import validation
| Check | What to verify |
|---|---|
| Count accuracy | Work item count matches Linear issue count |
| State distribution | Board columns match Linear workflow |
| Priority spread | Filter by priority in list view |
| Labels | Check Settings > Labels for correct import |
| Cycles | If imported, verify cycle dates and member items |
| Sub-issues | Expand parent items to check child items |
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| No teams listed | Insufficient permissions | Use an account with team access |
| States not mapping | Custom state names | Manually adjust state mappings |
| Duplicate labels | Slight name variations | Merge labels after import |
| Estimates missing | Option disabled | Enable "Import estimates" and re-import |
| Assignees unmatched | Email mismatch | Invite members with matching emails |
TIP
If you are migrating from Linear, the workflow model is very similar to SetGet. Most teams find the transition seamless with minimal state remapping needed.
Linear concept mapping
| Linear concept | SetGet concept | Notes |
|---|---|---|
| Workspace | Workspace | Direct equivalent |
| Team | Project | One team maps to one project |
| Issue | Work item | Core trackable unit |
| Sub-issue | Sub-work-item | Child of a work item |
| Cycle | Cycle | Same concept |
| Project | Module | Linear projects map to SetGet modules |
| Label | Label | Direct equivalent |
| View | View | Same concept |
| Roadmap | No direct equivalent | Use modules and views |
| Triage | Intake | Similar concept |
Handling Linear projects
Linear uses "Projects" as grouping containers above issues (similar to epics). In SetGet, the equivalent is a Module. During import:
- If you enable "Import as modules", each Linear project becomes a SetGet module.
- If you prefer a flatter structure, Linear projects are imported as labels instead.
- Work items retain their project/module association.
TIP
If your Linear workspace uses projects extensively, map them to modules for the closest structural equivalent. This preserves the ability to track progress by module.
Post-import team communication
After importing from Linear, help your team find their way:
- Share a mapping of Linear team names to SetGet project names.
- Point out any differences in the sidebar navigation.
- Note that Linear's "Triage" maps to SetGet's "Intake" feature.
- Remind the team that keyboard shortcuts differ between the two tools.