Skip to content
Get a quote

How do I migrate from Monday.com to Jira?

Short answer

Use Jira Cloud's built-in monday.com importer. It maps items to work items and subitems to subtasks, and groups to a status, epic or category. It skips Formula, Mirror, Doc, Button and Progress columns, and only maps users who already exist in Jira. For anything else, export boards to Excel and import them with Jira's CSV importer as a Jira admin.

By

Two native routes

Jira’s monday importermonday Excel export + Jira CSV import
ItemsWork itemsOne row per item
SubitemsSubtasksNeed Work item ID and Parent columns, with parents above children
GroupsStatus, epic or categoryA column you map
UpdatesNot described in Atlassian’s docsExport includes updates on a separate tab; subitem updates aren’t exported
FilesNot describedAttachment URLs must be reachable over HTTP or HTTPS by your Jira site
UnsupportedFormula, Mirror, Doc, Button, Progress columnsFormula results export as values
UsersOnly users who already exist on the siteMatched 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

  1. Invite users to Jira first, because the importer only maps existing users.
  2. 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.
  3. Run the monday importer for each board. Check the groups and status mapping on one board before doing the rest.
  4. Fill the gaps by CSV. Comments go in separate Comment columns, and attachments go in as URLs.
  5. Recreate formula logic as Jira fields or automation, since formula columns don’t import.
  6. 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.

Questions, answered

A few useful answers.

Do monday updates (comments) come across?

Board exports to Excel can include updates on a separate tab, though not subitem updates. For CSV import, put each comment in its own Comment column.

What happens to monday automations?

They don't migrate. Rebuild them as Jira automation rules after the import.

Can non-admins import?

Jira's admin CSV import is for administrators. Users without admin permissions can import up to 250 work items per CSV file with the basic importer.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote