Migrate from monday Work Management to Jira

monday Boards map to Jira Projects. We preserve the board name as the project name, board owner as the project lead, and workspace assignment as the Jira project category or shared configuration. Board-level settings (default view, notification preferences) do not migrate; Jira project configuration is set up during discovery and applied uniformly across all imported boards. Teams migrating multiple boards should decide whether to create one Jira project per monday board or consolidate boards into a single project with issue type filters — this decision affects how sprints and backlogs are scoped.

monday Items map to Jira Issues. The Item name becomes the Issue Summary field. Status maps to a Jira workflow Status, and Assignees map to Jira Assignee by email match. Priority, Due Date, and any custom column values map to their Jira equivalents. Issue Type defaults to Task for general Items; we configure a mapping rule if monday uses a Status column with values that represent issue types (Bug, Story, Epic) — in that case the Status label is used to set the Issue Type at import time rather than the default.

monday Groups (the horizontal row containers representing status buckets or phases) map to Jira Sprint assignment if the group name matches a sprint name pattern, or to Labels if groups represent categories rather than workflow stages. We inspect the board structure during discovery: if groups are status labels (To Do, In Progress, Done), they map to a Jira workflow; if groups are phase buckets (Discovery, Design, Development, QA), they map to Labels on the Issue. The customer chooses the strategy during scoping.

monday columns (text, number, date, dropdown, person, formula, link, file, vote, and others) map to Jira system or custom fields. Status columns become Jira Status transitions in the configured workflow. Date columns become Jira Due Date or a custom date field. Person columns become Jira Assignee. Dropdown and labels columns become Jira Select (single) or Multi-Select picklists. Number columns become Jira Number fields. Formula outputs that monday computes at display time may return null in the API unless the formula column is explicitly requested — we inspect the column list and handle nulls by either skipping the field or mapping a default value per the customer's preference.

monday Subitems map to Jira Sub-tasks under their parent Issue. This is the highest-risk mapping in the migration because monday.com exposes no bulk export endpoint for Subitems — we must query each parent Item individually to retrieve its Subitems, which doubles or triples API call volume and can exhaust daily call limits on Basic and Standard plans. We handle this by first batching all Item ID retrieval, then making secondary API calls per Item during off-peak hours, and pacing to stay within the plan's limit. Subitems without a parent Item in the migrated set are flagged for the customer's admin to resolve.

monday Dependency columns link Items as predecessor-successor pairs, sometimes across boards. Jira Issue Links support blocks, is blocked by, relates to, and duplicate link types. We flatten the cross-board dependency graph into a flat relationship table during extraction, then create Jira Issue Links using the appropriate directional type. Circular dependency chains are flagged and resolved by removing the link on the last item in the chain before import. Cross-board links that reference an Item not included in the migration scope are preserved as URL references rather than live links.

monday Users and Owners map to Jira Users by email match. Any monday User without a matching Jira User is held in a reconciliation queue for the customer's Jira admin to provision before record import proceeds. Inactive Jira users can receive issues if the migration admin has the necessary permissions; we configure the issue assignee accordingly during the migration window.

monday Updates (threaded comments on Items) map to Jira Issue Comments. We preserve the update text, author, timestamp, and thread reply structure. HTML-formatted updates are sanitized to plain text or Jira-compatible markup before import. Rich media embedded in updates (image URLs, file links) migrate as text references with the original URL preserved.

monday File column values and inline attachments store file metadata — name, URL, uploader, timestamp. We migrate file references as attachment metadata on the Jira Issue. Actual binary file download is outside scope for the monday API; the URL reference is preserved on the Jira attachment record and teams should verify URL accessibility post-migration. Files stored in monday's Google Drive or Dropbox integrations migrate as external link references rather than native Jira attachments.

monday Tags (Labels column type) map to Jira Labels by name. Jira Labels are a flat tag namespace, so all monday Tags from all boards migrate into the same Jira Labels space — we recommend the customer review for duplicates or namespace collisions before import. Tag colors from monday are noted but have no Jira equivalent and are dropped.

monday Time Tracking column entries (duration, description, assignee, timestamp per entry) map to Jira Issue work logs with the time estimate and time spent fields. Jira's worklog format (time in seconds or Jira duration notation like 3h 30m) is applied during the transform. Multiple monday time entries for the same Item are merged into a single Jira worklog entry with the combined total and a summary description.