Two native routes
| Jira’s monday importer | monday Excel export + Jira CSV import | |
|---|---|---|
| Items | Work items | One row per item |
| Subitems | Subtasks | Need Work item ID and Parent columns, with parents above children |
| Groups | Status, epic or category | A column you map |
| Updates | Not described in Atlassian’s docs | Export includes updates on a separate tab; subitem updates aren’t exported |
| Files | Not described | Attachment URLs must be reachable over HTTP or HTTPS by your Jira site |
| Unsupported | Formula, Mirror, Doc, Button, Progress columns | Formula results export as values |
| Users | Only users who already exist on the site | Matched by name or email in the CSV |
| Size | — | monday exports up to 100,000 items per board; Jira recommends about 1,500 work items per CSV file |
Steps
- Invite users to Jira first, because the importer only maps existing users.
- Design the Jira project: work types, workflow statuses (monday status columns rarely match Jira workflows one to one), custom fields for the monday columns you keep.
- Run the monday importer for each board. Check the groups and status mapping on one board before doing the rest.
- Fill the gaps by CSV. Comments go in separate Comment columns, and attachments go in as URLs.
- Recreate formula logic as Jira fields or automation, since formula columns don’t import.
- Rebuild automations and dashboards in Jira.
What the native tools do / where they stop
Atlassian’s monday importer covers the structure (items, subitems, groups) well. Older community answers assume there is no importer, so check the current Atlassian docs rather than old threads. What doesn’t map well are monday’s board-level concepts: mirror and connect columns that link boards, formula columns, and automations. Jira expresses those as issue links, fields and automation rules, so they’re redesigned rather than imported.
Where FlitStack AI fits
FlitStack AI migrates projects, tasks, subtasks, custom fields, comments, attachments and dependencies between PM tools, and matches users by email. See Jira migrations.