Introduction
Most teams that choose Linear are leaving something, and the most common source is Jira. Linear already has a Jira importer that brings over issues, statuses, labels and assignees. The hard part isn't moving data. It's moving habits. Jira teams are used to custom workflows, dozens of fields, story points on everything and ticket-heavy processes. Linear is deliberately opinionated: Cycles instead of configurable sprints, a small set of workflow states, Triage instead of an open backlog, and keyboard-first speed. A migration that copies Jira's complexity into Linear makes for a disappointing Linear. I'll improve onboarding so teams arriving from Jira reach the "this is so much faster" moment quickly and keep using it.
Step 1
Clarifying Questions (5 mins)
Why it matters: The person who runs the import decides what the first week looks like for everyone else. Expected answer: At startups and scale-ups, usually an engineering lead or CTO. In larger companies, a platform team champion. Impact on approach: Design for a champion who is enthusiastic but short on time, and has to bring 20–100 skeptical colleagues along.
Why it matters: Shows whether the problem is the import itself or what happens after it. Expected answer: The import completes for most teams, but about 30% of migrated workspaces have fewer than half their invited members active by week 4. Reasons include messy imported data and "Linear doesn't have my field." Impact on approach: Focus on the 30 days after import, not just the import tool.
Expected answer: Small teams cut over in a weekend. Larger orgs move team by team and run Jira alongside Linear for months. Impact on approach: Support both paths, with a sync option for coexistence.
Expected answer: Migrated teams become paying, expanding workspaces. Strong retention after migration also feeds referrals, a key growth channel for Linear. Impact on approach: Track week-4 activation and 90-day seat growth.
Practice similar questions
Subscribe to access the full answer