
A successful Linear migration gives the team a working place to pick up its issues on Monday. An import count alone can't tell you if files open, subtasks point at the right parent or restricted work kept the right audience. Test those things while you can still fall back to the old process.
Linear documents a workspace CSV export under its administration settings. The export includes fields such as issue IDs, statuses, estimates, labels, projects, cycles and parent issues. The CSV does not include attachment files, though descriptions may contain links. Treat comments, attachments, linked references and access rules as separate checks for the destination and importer you choose. Linear export documentation.
| Data | What to do before cutover |
|---|---|
| Statuses and priorities | Map each used value to a destination value and check unmapped rows |
| Assignees and teams | Decide how to handle departed users and private teams |
| Issues and parents | Preserve an old-ID to new-ID map and verify parent links |
| Comments and files | Confirm which content the tool transfers and whether files open under correct access |
| Internal links | Test links to other issues and identify where old links remain |
| Dates and cycles | Compare date semantics and what a completed cycle looks like |
Let people know which historical material will remain in a retained archive. Set its access and retention before the move.
Pick a project with an ordinary task, a parent and subtask, a closed issue, a link to another issue, an attachment and any restricted work you are authorized to test. Use a non-production destination with appropriate access. Compare source and destination counts, then open the sample items as someone with the ordinary team role. For private records, confirm that people outside the allowed audience cannot see them.
Check the exact destination release and deployment. A feature advertised for a hosted service can differ in a self-hosted edition. For the design choice between tools, see Linear vs Plane.
Agree on a pause for new edits, preserve a protected copy of the export, and record when the final copy was taken. Import once using a documented process or a supported way to reconcile changes. Compare counts by project and status and check the critical examples again. Switch the team's working links after someone signs off. If a required check fails, keep work in the agreed source and identify which changes need reconciliation before retrying.
Use SelfManager.ai Team as a coordination table if the team needs owners and due dates for export, sample verification, sign-off and follow-up. Keep issue payloads and credentials in their approved systems. The coordination table should tell people who owns the next checkpoint and what evidence is required to pass it.

Plan smarter, execute faster, achieve more
Create tasks in seconds, generate AI-powered plans, and review progress with intelligent summaries. Perfect for individuals and teams who want to stay organized without complexity.
Get started with your preferred account