There’s no native, one-click migration from Microsoft Planner to Jira — and the CSV export-import route everyone reaches for loses your buckets, checklists, and assignees in field-mapping hell (and drops your attachments entirely). The fix is to decide the Planner-to-Jira field crosswalk before you import, or use a connector that does the mapping in one pass. This page covers both.
The pain is well documented. The canonical Atlassian Community migration thread is built entirely around matching Planner fields — “Bucket Name, Checklist Items, Completed Checklist items, Labels, Late” — to Jira, and the accepted answer walks through ticking a manual “Map field value” box for each one (Atlassian Community). Another thread frames it as going from a “napkin to a blueprint” — the two tools model work differently enough that a raw dump doesn’t survive the trip (Atlassian Community).
The manual route: CSV export and import
The DIY path is four steps:
- Export the plan. From Planner (or via the Microsoft 365 export), get the plan’s tasks into a CSV or Excel file.
- Clean the columns. Planner exports fields like Bucket, Progress, Priority, Assigned To, Checklist items, Labels, Start, Due, and Late. Some map cleanly; some don’t.
- Import into Jira. Use Jira’s external-system CSV import and map each column to a Jira field by hand.
- Map field values. For every Planner value that has no Jira equivalent, tick “Map field value” and choose a target — one row at a time.
It works for a one-time move of a small plan. It falls apart on volume, and step 4 is where things silently go missing.
Two things bite harder than the docs let on. If you want buckets to become epics rather than just labels, one import isn’t enough — you have to run two passes: import a spreadsheet of bucket names to create the epics first, then import the tasks CSV mapping the bucket column as the epic link. That’s the workaround one migrator landed on after they “couldn’t figure out how to import all these tasks at once and create epics from the values in the ‘bucket’ column” (Atlassian Community, 2021). And attachments never make the trip at all: Planner leaves them out of the export by default because they live in the plan’s SharePoint document library, not the CSV — so unless you pull them from SharePoint and re-attach by hand, every file link is dropped (Microsoft Q&A, 2025).
The Planner → Jira field crosswalk
Decide these mappings once, up front, and apply them consistently:
| Planner | Jira | Note |
|---|---|---|
| Task title | Summary | Clean 1:1. |
| Notes / description | Description | 1:1, but Planner’s formatting is thinner. |
| Bucket | Status, component, label, board column, or epic | No single right answer — pick one convention before importing. For epics, you need a two-pass import (create epics from bucket names first, then map the bucket column as the epic link). |
| Progress (Not started / In progress / Completed) | Status | Map the three Planner states to your workflow’s statuses. |
| Assigned To | Assignee | Only works if the person exists as a Jira user with a matching identity. |
| Checklist items | Sub-tasks or a description checklist | No native Planner-checklist equivalent in Jira; choose sub-tasks (heavier, trackable) or inline (lightweight, not trackable). |
| Priority | Priority | Map Planner’s Urgent/Important/Medium/Low to your scheme. |
| Labels | Labels | 1:1. |
| Start / Due date | Start date / Due date | 1:1 if your Jira has the fields enabled. |
| Late (flag) | (no field) | Derived from due date in Jira — drop the flag, don’t map it. |
| Attachments | (not in the export) | Excluded from the Planner CSV — files live in SharePoint. Download and re-attach in Jira separately, or they’re lost. |
The three that bite people are buckets, checklists, and attachments — the first two have no native Jira twin, and the third isn’t in the export file at all. If you don’t decide the target field for buckets and checklists before you import, the same bucket ends up scattered across statuses on one task and labels on another. (If your goal is an ongoing link rather than a one-time move, syncing Planner with Jira sidesteps the crosswalk entirely — the mapping lives in the connector, not your spreadsheet.)
Why the DIY route stays painful
Even done carefully, the CSV path is a one-time snapshot. It doesn’t keep Planner and Jira in sync afterward, so if some of the team stays in Planner during a phased move, the two drift apart immediately. That’s worth deciding before you export at all: if marketing or ops are never going to live in Jira, sync the two tools instead of migrating and let each team keep the one it knows. Building it as a live integration by hand means wiring the Microsoft Planner API to the Jira API yourself — the kind of multi-step glue job that platforms like Pipedream exist to paper over (Pipedream). If you’re weighing that build-vs-buy call, it’s worth comparing a purpose-built connector against Power Automate and Unito before you commit a month to CSV surgery or glue code.
The one-pass alternative
If you’d rather not do CSV surgery, point a purpose-built connector at the plan and let it recreate the tasks as Jira issues with buckets, checklists, and assignees mapped in a single pass — and keep them in sync afterward if you need a phased cutover.
That’s what the Microsoft Planner to Jira Connector does: install it from the Marketplace, choose the plan and the target Jira project, and it handles the field crosswalk above so you’re not ticking “Map field value” a hundred times. See the quickstart for the exact setup.