Same issue prefix
Your Jira project key becomes your Linear team key. Commit messages, docs, bookmarks and Slack threads that mention ENG-1423 still point at the right issue.
Compare
See what Linear's built-in importer leaves behind
The Jira to Linear migration that actually works
Keep your issue prefix and bring every comment, attachment, release, sprint, pull request link and subscriber with you. Back up, inspect, import — then keep syncing until you're ready to switch.
acme.atlassian.net → Linear
Backup verified
- ENG-1423 Checkout fails when a coupon and a gift card are combined
- ENG-1422 Move billing webhooks to the new event bus
- ENG-1419 Rate limit password reset emails per account
- ENG-1416 Export audit log to CSV
- ENG-1411 Flaky test: SessionRefreshSpec times out on CI
- ENG-1408 Dark mode for the admin dashboard
- ENG-1402 Add SAML login for enterprise workspaces
- ENG-1398 Retry failed webhook deliveries with exponential backoff
- ENG-1391 Upgrade Postgres to 17 on staging
- ENG-1385 Search results ignore archived projects
ENG is in Linear
Syncing
100%
Jira ENG → Linear ENG
- Issues
- 4,812
- Comments
- 31,207
- Attachments
- 6,944
- Pull requests
- 2,377
- Releases
- 64
- Sprints → projects
- 118
Synced ENG-1423 · 2 new comments
1.0 Comparison
The official importer gets you started. We get you all the way there.
Linear's built-in Jira importer moves titles, descriptions, statuses and comments. Releases, sprints, pull request links, watchers and most of your files stay behind in Jira — the instance you are about to switch off.
| Capability | Linear's Jira importer | Jira-to-Linear-importer |
|---|---|---|
| Keeps your issue prefix ENG in Jira stays ENG in Linear | Only when importing into a new or empty team | Always |
| Releases Jira fix versions | Not imported | Imported as releases |
| Pull request links The code that shipped each issue | Not imported | Imported |
| Comments The full discussion on every issue | Imported | All comments |
| Attachments Specs, logs, recordings, designs | Images only — other files link back to Jira | Every file uploaded to Linear |
| Sprints What shipped when | Not imported | Imported as projects |
| Subscribers Jira watchers keep getting notified | Not imported | Imported |
| Backup A complete copy of your Jira data | Not available | Included |
| Browse & inspect before importing See exactly what will be moved | Not available | Every project, issue and file |
| Incremental sync Pick up changes after the first import | One-time — re-imports skip existing issues | Sync until you cut over |
Based on Linear's published Jira import documentation as of October 2026. Linear also offers a separate Jira Sync integration for keeping new issues in sync.
2.0 Everything comes across
Everything in Jira. Now in Linear.
An issue is only as useful as its context. We import the history around it, too — so nobody has to go back to Jira to find out why something was built.
Releases
Every fix version arrives in Linear as a release, with its issues attached.
Pull request links
Every issue still shows the pull requests that shipped it.
Every comment
The whole discussion comes across — the part that explains why.
Attachments, uploaded
Files are uploaded to Linear — not left as links to a Jira you're switching off.
Sprints become projects
Each sprint arrives as a Linear project with its issues, so the record of what shipped when survives the move.
Subscribers stay subscribed
Jira watchers become Linear subscribers, so the right people keep getting notified from day one.
3.0 How it works
A migration you can rehearse. Switch over when you're ready, not when the import is done.
-
01
Back up
Take a complete backup of your Jira data before anything is written. Keep it as an archive long after Jira is gone.
-
02
Browse & inspect
Explore every project, issue, comment and file before you import. Spot surprises while they're still cheap to fix.
-
03
Import
Issues, prefixes, comments, attachments, releases, sprints, pull request links and subscribers — in one run.
-
04
Sync incrementally
Your team keeps working in Jira. Each sync brings over only what changed, until you cut over.
4.0 Build or buy
Spend a week building a migrator. Or spend it on your product.
A script that copies issues from Jira to Linear takes an afternoon — with an AI agent, maybe an hour. A migration your team can trust takes a lot longer. The time goes into everything the first script gets wrong.
-
Mon
The first script works
Then you read the output. Descriptions and comments arrive as Atlassian Document Format — nested JSON with mentions, tables, panels and inline images, all of it to be converted to Markdown.
-
Tue
Attachments
Every file needs an authenticated download from Jira, an upload to Linear, and rewritten links in each description and comment that embeds it.
-
Wed
Rate limits and restarts
Run three stops at issue 18,000. The restart creates duplicates, so you add checkpoints, retries and idempotency — then clean up the test workspace.
-
Thu
Everything else
Jira often hides email addresses, so people don't match up. Statuses differ per project. Fix versions, sprints, watchers and pull request links each need their own API calls.
-
Fri
The team kept working
A week of new issues and comments landed in Jira. Now you need incremental sync — or a freeze and a weekend cut-over.
Build it yourself
- A week or more of engineering time
- Test runs write to your real Linear workspace
- Edge cases found after cut-over
- Thrown away once you've switched
Jira-to-Linear-importer
- The edge cases above, already handled
- Back up and inspect before anything is written
- Sync incrementally until you cut over
- Priced by size, known up front
5.0 Pricing
Priced by the size of your Jira. Know the cost before you start.
Estimate your migration in seconds
Two numbers decide the price: how many issues you have, and how much has been attached to them.
$100 per 1,000 issues
100,000+
GB
$10 per GB
1,000 GB+
Estimated price
$700
- 5 × 1,000 issues
- $500
- 20 GB of attachments
- $200
Issues round up to the next 1,000 and attachments to the next whole GB.
Start your migrationLarge migration? Recommended at this size
Lots of projects, custom workflows or years of history? Request handholding and we'll guide your team through the migration.
6.0 FAQ
Questions, answered.
How is this different from Linear's built-in Jira importer?
The built-in importer is a one-time import of the basics: titles, descriptions, statuses, comments and images. We also bring releases, sprints, pull request links, subscribers and every attachment, keep your issue prefix, and let you back up, inspect and keep syncing. See the comparison for details.
Can my team keep working in Jira during the migration?
Yes. Run the first import, then sync incrementally. Each sync brings over only what changed since the last one, so Linear stays current until the day you switch.
Are attachments really copied?
Yes. Every file is uploaded to Linear, not just images. Nothing in Linear depends on your Jira instance staying online.
What happens to sprints and fix versions?
Fix versions become Linear releases. Sprints become Linear projects, each with the issues that were in the sprint.
Can I see what will be imported before I import it?
Yes. Browse every project, issue, comment and attachment first, and keep a complete backup of your Jira data alongside.
Are you affiliated with Linear or Atlassian?
No. Jira-to-Linear-importer is an independent product. Linear and Jira are trademarks of their respective owners.
Your Jira history deserves better than a backlink.
Bring all of it to Linear.
Maria · Mar 4, 2024
Repro'd on staging. Only happens with the 3.x payment SDK.
Jonas · Mar 5, 2024
Pinned the SDK for now. Real fix tracked in v2.14.