How to migrate from Jira to Plane

Move Jira projects to self-hosted Plane: the Jira importer or the API route by edition, mapping workflows and fields, a staging import and the cutover.

Start with one workloadThe steps

Written for
The engineer who will do the work
Or run by Pilae
At a fixed price, then operated

In short

  • Plane’s Jira importer is part of the Commercial Edition, free plan included; on the open-source Community Edition, the move runs through the Plane API instead.
  • Jira statuses become Plane states in five groups, sprints become cycles and components modules; custom fields become properties only on paid Plane plans.
  • Automation rules, Marketplace app data, JQL filters and dashboards do not migrate: each one still in use is rebuilt in Plane or n8n, or retired.
  • On cutover day Jira goes read-only, a final import picks up the last changes, and Jira stays readable until the subscription ends.
On this page (17)

Moving from Jira to Plane is an import, but which import depends on the Plane edition. The Commercial Edition has a Jira importer that reads your projects directly. The Community Edition, the open-source one Pilae deploys unless you need more, has no importer, so the move runs through Plane’s API. Either way, what decides the outcome happens before anything is imported: agreeing with each project owner what Jira’s statuses, issue types and custom fields become in Plane. This guide covers both routes and the order we run them in.

Jira Cloud now calls projects spaces and issues work items. Plane also says work items. This guide keeps project and issue for Jira, the names most teams still use.

Why teams move from Jira to Plane

Three reasons come up again and again.

  • Where the backlog lives. A backlog holds security findings, customer escalations and product plans. Self-hosted Plane keeps them on your premises or in a region you choose. For teams on Jira Data Center there is also a date: Atlassian stopped selling Data Center to new customers on 30 March 2026 and has announced that its Jira Data Center products turn read-only on 28 March 2029.
  • A tracker people can follow. Years of schemes, screens and custom fields make Jira hard to change and slow to learn. Plane has states, labels, cycles, modules and views, and most teams find that covers the work they actually do.
  • Cost per seat. The Plane Community Edition has no per-user fee. The cost is the machines it runs on and their operation.

What you give up is depth of configuration: workflow conditions and validators, JQL, and the Atlassian Marketplace. You also give up the fact that someone else runs the platform, which is the part Pilae takes on.

Step 1: inventory the Jira projects

Most Jira sites carry projects nobody has touched in years, workflows with statuses nobody uses and custom fields nobody fills in. Find out what is live before deciding what to carry.

  1. Active projects. Search for issues updated in the last twelve months and group them by project. Projects outside that list are archived, not moved.
  2. For each active project: its owner, the issue count, the statuses actually in use, the issue types, the custom fields that hold data, the components and versions, and the boards and sprints.
  3. Automation rules. A global administrator exports the global and project rules as one JSON file: Settings, System, Automation flows, then Export flows in the More actions menu. Note which rules still run and what each one does.
  4. Marketplace apps and the data they hold: test cases, time sheets, approvals. Each one needs a decision.
  5. Filters, dashboards and integrations people use every week: saved JQL filters, dashboards, Git hosting, CI, chat and Confluence links.
  6. Users. An organisation admin exports them from Atlassian Administration: Directory, Users, then Export users. The CSV lists each user’s email address, status and, optionally, groups, which is what accounts are matched on later.

Take the archive

Two exports keep a record of Jira as it stood, whichever route you take.

  • A CSV export per project. Open Filters, then View all work items, enter the JQL for the project and choose a CSV option from the Export menu. Jira Cloud exports up to 10,000 work items at a time in the background and notifies you when the file is ready; split larger projects by date with JQL.
  • A Jira Cloud backup. Under Settings, System, Backup manager, choose Create backup for cloud, and tick the option to include attachments if you need them. With attachments, Jira makes you wait 48 hours between backups. The backup holds work items, fields, comments, board and sprint data, users and configuration. It leaves out automation rules and Marketplace apps and their data, which is why step 1 exports the rules separately.

Step 2: choose the edition and the import route

Two routes from Jira to Plane

Plane Jira importer

  • Commercial Edition, any plan; the free plan has 12 user seats per workspace
  • Reads Jira Cloud or Jira Server and Data Center with an access token
  • Brings issues, comments, attachments, sub-tasks, links, sprints, components, watchers and worklogs
  • A re-run updates imported items in place
  • Paid plans add work item types, custom properties, epics and OIDC or SAML sign-in

Plane API

  • Community Edition, AGPL-3.0, no per-user fee
  • A script reads Jira and writes through Plane’s REST API
  • States, labels, cycles, modules, work items, comments, attachments, relations and links
  • External IDs make the script safe to rerun
  • No work item types, custom properties or epics on this edition, so the mapping is simpler

Pilae deploys the Community Edition unless your requirements need the Commercial Edition. The usual reasons to need it are the built-in importer and single sign-on through your identity provider. If you do, the proposal says so and the Commercial Edition licence is held in your name. Decide before the mapping, because the target fields differ: what becomes a custom property on a paid plan becomes a label or a line of text on the Community Edition.

Step 3: map Jira concepts to Plane

The vocabulary is close; the configuration is much smaller.

Jira Plane Edition note
Project Project
Issue Work item
Status State, in one of five groups Backlog, Unstarted, Started, Completed, Cancelled
Workflow transitions Workflows Business plan; on the Community Edition any state can follow any other
Issue type Work item type Paid plans; on the Community Edition, a label
Epic Epic, module or parent item Epics are a Pro feature; the importer brings epics in as a work item type
Sub-task Child work item
Sprint Cycle A work item sits in one cycle at a time
Component Module
Fix version Custom property, module, label The importer stores versions as properties
Priority Priority Urgent, High, Medium, Low, None
Label Label
Custom field Custom property Paid plans; on the Community Edition a label or a line in the description
Story points Estimate
Issue link Relation Blocks, blocked by, relates to, duplicate
Watchers Subscribers
JQL filter, board View with filters, board layout Plane’s query language is not part of the Community Edition

Statuses into states

Every Plane state belongs to one of five groups, and the group decides behaviour: only states in the Completed group count as done. Map each Jira status to a state, then ask whether the state earns its place. Long Jira workflows usually shrink once the team sees the states side by side. Agree it with the project owner in writing; it is the mapping people notice on the first morning.

Issue types and custom fields

On a paid plan, the importer creates work item types from Jira issue types when the Work Item Types feature is on for the project, and turns supported custom fields into custom properties. On the free plan, issues still import but issue types are not created as work item types, so check where your fields land in the staging import. On the Community Edition, keep the few fields that drive decisions: a short list of values becomes labels, a free-text field a line in the description. The CSV archive keeps every original value.

Sprints and cycles

Sprints become cycles with their dates and work items. A Plane work item belongs to one cycle at a time, so an issue carried over several sprints ends up in one of them. Cycles in a project cannot overlap by default. On the API route, bring closed sprints across only if the team reads their history; the archive keeps it either way.

Step 4: prepare users, sign-in and the projects

  1. Invite the users to the Plane workspace by email, matched against the Atlassian user export. With the importer on Jira Cloud, you upload that export at the users step instead; without it, imported items and comments show the name of the person who ran the import and assignees stay empty. On Jira Server and Data Center, the importer brings the users referenced by the issues.
  2. Connect sign-in. The Community Edition signs people in with email, or with Google, GitHub or GitLab accounts. OIDC and SAML, for Keycloak or Entra ID, need a paid Commercial Edition plan.
  3. Create the projects with the agreed states, labels and estimates, and turn on cycles and modules. For the importer on a paid plan, turn on Work Item Types before importing.
  4. For the API route, create a personal access token for a dedicated import account under Profile settings, Personal access tokens. Plane allows 60 API requests per minute per key by default; on a self-hosted instance the API_KEY_RATE_LIMIT setting changes it, so raise it for the import and set it back afterwards.

Step 5: import into staging and check

Run every import into a staging copy of Plane first. Owners check there while their teams keep working in Jira.

With the Plane Jira importer

  1. In Plane, open Workspace settings, Imports, and choose Import under Jira for Jira Cloud, or under Jira Server/Data Center.
  2. Enter the token (an API token on Jira Cloud, a personal access token on Server and Data Center), the email it belongs to and the Jira address, then Connect Jira. The account needs to read the project, its issues, statuses, priorities, issue types and labels.
  3. Pick the Plane project, then the Jira project. An optional JQL filter limits the import to matching issues.
  4. On Jira Cloud, upload the user export.
  5. Map Jira statuses to Plane states, letting Plane create any that remain, then map priorities. Unmatched priorities become None.
  6. Confirm. The import runs in the background.

Every imported work item gets a JIRA IMPORTED label and a Linked Jira Issue link back to Jira, and Plane keeps its original Jira key number. A re-run repeats the import with the same settings and updates existing items in place rather than duplicating them. On Jira Server or Data Center behind single sign-on, attachment downloads can be redirected to the login page; Plane’s Jira importer documentation describes the workaround.

Through the Plane API

On the Community Edition, a script does the same work in a fixed order.

  1. Read Jira through its REST API, or from the CSV export for a small project. On Jira Cloud, comments and multi-line fields come back in Atlassian Document Format, a JSON structure the script converts to the HTML Plane stores.
  2. Create the structure first: states, labels, modules and cycles, so work items can refer to them.
  3. Create the work items with the Jira key as external_id and jira as external_source. Plane refuses a second work item with the same pair, which makes the script safe to rerun.
  4. Set parents and relations once every item exists, since both point at other items.
  5. Add comments, attachments and a link back to Jira. Comments created through the API are posted by the account that owns the key, so the script writes the original author and date at the top of each one.

Check before anyone switches

Owners compare issue counts per project and per state against the CSV archive, open a sample of issues with attachments, sub-tasks and links, and look at their board and current cycle. Nobody works in staging: the final import in step 7 replaces it.

Step 6: rebuild automations, filters and integrations

  • Automation rules. The JSON export shows each rule’s trigger, conditions and actions. Rebuild the ones still in use in n8n, started by Plane’s webhooks and acting through its API. Rules that only existed to keep a complex workflow consistent often disappear with it.
  • Filters and dashboards. Rebuild the ones people open as Plane views with filters, per project or across the workspace. A JQL query too complex for a view becomes a report outside Plane, reading the API.
  • Marketplace apps. Export what each app holds where it allows, and decide whether its job moves to Plane, to another tool or stops.
  • Git and CI. Branches, commit messages and pull requests name Jira keys today. Agree the Plane identifiers with developers, and switch commit conventions on cutover day. Plane’s GitHub integration, which links branches, pull requests and commits that mention a work item, is a Pro feature.

Step 7: run in parallel, then cut over

Two live trackers split the truth, so the parallel period is the staging check while teams stay in Jira, then one cutover per project.

The cutover, in order

  1. Pilot: One project moves first, and its findings adjust the mapping before the others.
  2. Freeze: On the agreed day, Jira goes read-only for the projects moving. People keep browse access and lose create, edit, transition and comment.
  3. Final import: The importer re-run, or the script rerun by external ID, picks up the last changes in production.
  4. Switch: Teams start work in Plane; bookmarks, README links, CI and chat integrations point to it.
  5. Close: Jira stays readable until the subscription ends, after a last CSV export and backup.

Keep the archive from step 1 under your own retention rules. It is the record of what Jira held, including the fields you chose not to carry.

Running Plane in production

Plane is a dozen services, not one container: web, API, workers, a scheduler, real-time collaboration and a proxy, on PostgreSQL, RabbitMQ, Valkey and an S3-compatible bucket for attachments. Plane releases often and many releases carry database migrations, so upgrades want a test against a copy of your data first.

Pilae operates Plane this way, on your premises or on dedicated machines in Pilae Cloud, answering only on your private network. The database and the bucket are backed up daily, encrypted, in the country your contract names, and on Enterprise a restore test runs every month and is recorded in the console. The Pilae Agent tests each upgrade on a copy of your data and applies it in your window once you approve. If you are still comparing options, see our page on Jira alternatives.

Let Pilae run the move

Pilae runs Jira to Plane migrations at a fixed price: the inventory, the mapping agreed with each project owner, the staging import through the importer or the API, the rebuild of the automations still in use, and the cutover. Then we operate Plane for you under a contract that, from the Business plan, includes a monthly availability commitment with service credits. See migration services for what the fixed price covers, or tell us how many projects you run and we will scope it.

Questions

Does the Plane Community Edition include the Jira importer?

No. Plane documents its Jira importer for Plane Cloud and for every plan of the Commercial Edition, the free plan included, which comes with 12 user seats per workspace. On the open-source Community Edition, the move runs through the Plane API instead, with a script that reads Jira and writes work items, comments and attachments.

What happens to our Jira workflows and custom fields?

Jira statuses become Plane states, each in one of five groups, agreed project by project. Rules about who may move an item from one state to another are a Business plan feature in Plane. Custom fields become custom properties on Plane's paid plans; on the Community Edition, the few that matter become labels or a line in the description.

Do Jira automation rules and Marketplace apps come across?

No. Automation rules are exported as JSON for the record and the ones still in use are rebuilt, usually in n8n with Plane's webhooks and API. Marketplace apps and their data are not part of Jira's own backup either, so each app gets a decision in the inventory.

What happens to Jira issue keys?

The Plane importer adds a link back to the Jira issue on every work item and keeps the original key number. On the API route, the Jira key is stored as the work item's external ID with a link back to Jira. Commits and documents keep naming the old key, so Jira stays readable until the subscription ends.

Is Plane open source?

The Community Edition is, under the AGPL-3.0. The Commercial Edition is licensed by Plane Software, Inc.: its free tier adds the Jira and Linear importers, and its paid plans add OIDC and SAML sign-in and more advanced project features. Both run on your machines. Pilae deploys the Community Edition unless you need what the Commercial Edition adds, and then the licence is held in your name.

How long does a Jira to Plane migration take?

It depends on how many projects are still active and how far their workflows and custom fields have to be simplified, not on the number of issues. The inventory settles that. Pilae quotes the mapping, the import, the rebuild of automations and the cutover as one fixed price once the inventory is done.

Let us run the move for you

An inventory, a parallel run and a cutover plan, at a fixed price. Then we operate the app.

Start with one workload

  • Go deeperSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
  • CheckManaged operationsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.