Linear Import and Export
Few teams start with a blank slate. Most bring existing tasks from another tool, and many need to send Linear data to reports or backups. Import and export features handle both directions, so switching tools does not mean losing history.
Everyday Comparison
Moving to a new home needs two jobs: carrying boxes in and keeping a copy of important papers. Importing resembles carrying the boxes into the new house. Exporting resembles making photocopies of those papers for safekeeping.
OLD TOOL ──► IMPORT ──► LINEAR ──► EXPORT ──► SPREADSHEET / BACKUP
(Jira, │ │
CSV, etc.) Map fields Choose what
and statuses to download
Import Sources
Linear supports imports from several common tools. Available sources change over time, so check the import screen for the current list.
| Source | Typical Use |
|---|---|
| Jira | Teams moving from a large legacy tracker |
| Asana | Teams moving from task boards |
| GitHub issues | Open source projects and small dev teams |
| CSV file | Any tool that exports a spreadsheet |
Plan the Import
Clean the Source Data
Remove outdated tasks, duplicates, and abandoned projects before you import. Clean data creates a clean start. Importing ten thousand stale tickets only moves the clutter.
Map Statuses
Decide how old statuses match Linear statuses. The table below shows a sample mapping.
| Old Status | Linear Status |
|---|---|
| To Do | Todo |
| In Review | In Review |
| Closed | Done |
| Won't Fix | Canceled |
Match People
Invite team members before importing so assignees map correctly. Unmatched names can leave issues without owners.
Run an Import
- Ask an admin to open the import tool from workspace settings.
- Choose the source tool.
- Connect the account or upload the file.
- Pick the destination team.
- Review the field and status mapping.
- Start the import and wait for the confirmation message.
Test with a small batch first. Check that titles, descriptions, labels, and assignees arrive as expected. Run the full import after the test looks right.
Export Data
Admins can export issue data to a CSV file. Open the file in a spreadsheet to build reports, share lists with outside partners, or keep an archive. Choose the team and date range you need, then download the file.
Use the API for Regular Exports
Teams that need frequent exports can pull data through the Linear API. A scheduled script writes fresh results to a database or spreadsheet each day.
Protect Sensitive Information
- Share exports only with people who need them.
- Remove personal data such as customer emails before you send a file outside the company.
- Store backups in a secured location with limited access.
- Delete temporary export files after use.
After the Migration
Review the new workspace with the whole team. Archive the old tool in read-only mode for a short period. Announce a clear cutover date, so nobody keeps working in two places.
Troubleshooting
Issues Arrive Without Assignees
The import could not match user names or emails. Invite the missing people, then run a small corrected import or assign the issues by bulk edit.
Labels Look Messy
Old tools often use many overlapping labels. Merge similar labels after the import and delete unused ones. A short, clear label set helps filters work well.
Dates or Estimates Look Wrong
Check the estimate scale of the destination team. A scale mismatch, such as T-shirt sizes versus numbers, changes how values appear. Adjust the team setting and re-run a test batch.