Migration guide

How to migrate from Jira to Plane

Issues and tasks usually migrate fine via CSV; what almost never survives is your automation and custom workflow-state configuration.

1. 1

   Export your projects from Jira to CSV

   Filter by project and export issues/tasks with all fields (status, assignee, labels, due date). Export one project at a time to keep field mapping simple.

2. 2

   Map fields when importing into Plane

   Before importing, create the same statuses and labels in Plane that you used in Jira — if the names don't match exactly, the importer will leave those fields empty.

3. 3

   Rebuild your automation workflows

   Rules like "notify X when an issue closes" aren't exported. Write down your current automations before migrating and recreate them one by one in Plane.

4. 4

   Migrate team by team, not all at once

   Start with one pilot team or project for a full sprint before moving the rest — that way you catch mapping issues at low risk.

These steps are a general guideline — the exact export menu can vary depending on Jira's plan and version.