Getint: Where every ticket finds it's place.
Support portalCase studiesSchedule a demo
  • Welcome to the Getint Documentation Hub
  • Getting started with Getint
    • About Getint / Concepts
      • How Getint works (how it syncs the data)
      • Onboarding
      • What is a Connection?
      • What Are Runs
      • One-directional / Bi-directional integration
      • Migration vs Integration
      • How Integrations Are Executed By Getint
    • Starting the Free Trial and Accessing the Getint App
      • Selecting the Correct app per license
      • How do I extend the trial of getint.io?
      • Jira Access and User Management
    • Deployment options
      • Getint for Jira Data Center / Jira Server
        • Getint Jira Server / Jira Data Center App (native)
        • Getint for Jira Data Center / Jira Server - Architecture
      • Getint for Jira Cloud
      • Getint On-Premise
        • Architecture
        • Installation
          • How to Install Getint On-Premise in Windows Server
          • On-Premise/Standalone Guide
        • Updating On-Premise
        • Cluster High Availability
    • Prepare for the integration
      • Understanding the difference between platforms you integrate
      • One-to-One, One-to-Many, and Many-to-Many integration
      • Simplifying Workflow Sync with Getint: Jira
    • Connectors
      • Jira
      • Asana
      • Azure DevOps
      • Freshdesk
      • GitLab
      • HubSpot
      • Monday.com
      • Notion
      • Salesforce
      • ServiceNow
      • Zendesk
  • Guides
    • Quickstart
      • Integration
      • Connection
    • Integration Guides
      • How to Map Fields
      • How to create a custom field in all supported software
      • Git Repository integration
        • Git Connector - Azure DevOps
        • Git Connector - GitHub
        • Git Connector - GitLab
      • Azure DevOps Asana integration
      • Jira Airtable integration
      • Jira Asana integration
        • Jira - Asana: Subtasks synchronization
      • Jira Azure DevOps integration
        • How to Setup a Connection with Azure DevOps On-Premise
        • Jira - Azure DevOps: Epics and Subtasks Synchronization
        • Syncing Dependencies between Jira and Azure DevOps using Getint
      • Jira ClickUp integration
      • Jira Freshdesk integration
      • Jira Freshservice integration
      • Jira GitHub integration
      • Jira GitLab integration
        • Attachments Sync in GitLab Integration
      • Jira HubSpot integration
      • Jira Jira integration
        • Jira Jira licensing
        • Time Tracking in Getint – One-Way Synchronization
      • Jira Monday.com integration
        • Synchronizing Attachments in a Monday.com Integration
        • How to Insert Monday.com Items into Specific Groups Using Getint
      • Jira Notion integration
      • Jira Salesforce integration
        • Salesforce OAuth Authentication
      • Jira ServiceNow integration
        • Creating a ServiceNow User for Getint Integration
        • ServiceNow OAuth authentication
        • Creating a Custom Field in ServiceNow
        • How to Restrict "Incident" Data to Specific 3rd Party Companies
        • How to Restrict Access to Specific Tables for Integration
        • REST API requests list
      • Jira Trello integration
      • Jira Wrike integration
      • Jira Zendesk integration
        • How to Manually Provide Zendesk Organization ID and Name
    • Migration Guides
      • Migrating Data with Getint
      • Migration support, and onboarding
      • Jira to Jira migration
      • Asana to Jira migration
      • Azure DevOps to Jira migration
      • GitLab to Jira migration
      • Jira to Monday.com Migration
      • Jira Zendesk migration
  • Using Getint
    • Core Features of Getint
    • Workflows
      • Type Mapping
      • Integrations List
      • Configuring Your Data Sync: Bidirectional and Unidirectional Options
      • Syncing Attachments
      • Hierarchy
      • Assignees (users) mapping
      • Mapping Labels
      • Filtering Items for Integration in Getint
        • Troubleshooting Sync Issues: Unmet Filter Conditions
        • How to Filter Comments
        • Filtering by Assignment Group and Status
      • Shared Mappings in Getint – Centralized Mapping for Efficient Integrations
      • How to Use JQL Filters for Jira Integrations
      • Integration status
      • Storing counterpart link in the task comment
      • Storing Reference IDs/URLs Across Integrations
    • Connections
      • Troubleshooting Getint Integration Connectivity Issues
      • Permissions Issue: Status Code 500
      • Editing Connections for Existing Integrations
      • Changing the URL or Transitioning Between Instances
      • Debugging Connections in Getint: How to Troubleshoot and Resolve Issues
    • Quick Build
    • Reporting
    • Notifications
    • Request type issue on Jira Service Management how to select and work with it
    • Integrating one project with many: Streamlining synchronization across multiple projects.
      • One to Many Project - El Ride Use Case
    • Transition Fields
    • Resync and Hard Resync
    • Synchronizing Existing Items on Both Sides
    • Handling Syncs for Deleted Items
    • Advanced Scripting
    • Platform Release History
      • Getint Version 1.82
      • Getint Version 1.81
      • Getint Version 1.80
      • Getint Version 1.79
      • Getint Version 1.78
      • Getint Version 1.77
      • Getint Version 1.76
      • Getint Version 1.75
      • Getint Version 1.74
      • Getint Version 1.73
      • Getint Version 1.72
      • Getint Version 1.71
      • Getint Version 1.70
      • Getint Version 1.69
      • Getint Version 1.68
      • Getint Version 1.67
      • Getint Version 1.66
      • Getint Version 1.65
      • Getint Version 1.64
    • Settings
      • Data Storage
      • Sharing Access Permission
      • How to Override Getint Behavior Using Custom Properties
  • Support, legal & others
    • FAQ
      • Technical FAQ
      • Security FAQ
    • Troubleshooting Guide for Getint Users
      • Resolving Error 500 in Jira ServiceNow Integration
      • Locating Your Instance ID for Support
      • Connection Error: Certification Path Failed/PKIX Path Building Failed
      • Error: Field '<field-name>' cannot be set. It is not on the appropriate screen, or unknown
      • Connection timed out error
      • Troubleshooting: Integration Task Retrieval Error
      • Upgrade to newest version from version lower than 1.52
      • Debug Requests Feature
      • Troubleshooting: Resolving Hanging Integration Runs in Getint
      • Troubleshooting License Issues in Getint
    • Security and compliance
    • Support / SLA
    • Privacy & Security
      • Data Residency with Getint
    • Procurement & Legal
      • Enhanced Support for Vendor Onboarding and Security Assessments
      • EULA
      • Privacy policy
  • Billing & Services
    • Transparent and User-Friendly Pricing
    • Consulting and Custom Development
    • Understanding Getint Licensing and Pricing
      • How to pay for the apps
      • Migrations
      • Network License
      • Jira-Jira Licensing Model
      • Partners
      • Seamless Transition Offer: Migrate from Competitors to Getint with Exclusive Benefits
  • Use cases
  • Pricing Comparison: Getint vs. Alternatives
  • Battlecards (getint.io vs competitors)
  • Free migration from ConnectAll, Backbone, Exalate, Unito, Workato, TFS4JIRA and other tools
  • Anything missing? Getint is feedback driven
Powered by GitBook
On this page
  • Requirements for Migrating Historical Data
  • Preparing Your Environment Before Migration
  • How to Set Up Your Jira to Monday.com Migration
  • Why Choose Getint Migration Over CSV Import?
  • Need Help?

Was this helpful?

  1. Guides
  2. Migration Guides

Jira to Monday.com Migration

PreviousGitLab to Jira migrationNextJira Zendesk migration

Last updated 21 days ago

Was this helpful?

Migrating issues, tasks, and projects from Jira to Monday.com is a crucial step when transitioning project management platforms. Whether your team is shifting tools, consolidating data, or merging teams, Getint’s Migration Feature ensures an accurate and structured transfer of historical data.

Unlike standard integrations, which sync new and updated items, the migration feature allows for bulk transfer of existing items while maintaining their associated data, including custom fields, relationships, and hierarchies.

This guide walks you through the step-by-step process of setting up and executing a Jira to Monday migration using Getint.

Requirements for Migrating Historical Data

Migration License

Migrating historical data requires a migration license, as a standard integration license will not suffice. Migration licenses are billed separately from integration licenses.

To acquire a migration license, please visit our and click on the Migration tab for more details. Contact our team through our to proceed with your purchase.

Before purchasing a license, you can test the migration with a trial version, which allows:

  • Up to 20 migration runs

  • A maximum of 5 items per run

To access the trial version, follow the steps here:

Also, see our full migration guide: .

Preparing Your Environment Before Migration

Handling Fields That Cannot Be Mapped

Before you begin, ensure that all custom fields required on both Jira and Monday.com are created and available. If a counterpart field is missing on either side, it must be created first to allow mapping.

Migrating Values from Fields Without 1:1 Mapping

If a field in Jira doesn’t have a direct counterpart in Monday.com (e.g., assignees, priority), you can still capture its value by using a custom text field and the Use label from the other side option.

Steps:

  1. Create a custom Text field in Monday.com.

  1. In the field mapping screen, select the Jira field to be migrated and map it to the new custom field in Monday.

  1. Enable Use label from the other side.

This approach will insert the label/value of the original field into the destination field. Especially helpful for migrating the Assignees. You probably don’t want to recreate the accounts of people no longer in the company in Jira. This way, no mapping is required; we will inject the value to a text field.

How to Set Up Your Jira to Monday.com Migration

1. Set Up a Jira to Monday.com Integration

2. Access the Migration Feature

Once your integration is set, open the Getint App and:

  • Click Migrate Data from the left-side menu.

If you're using a trial version, a warning will appear indicating your migration run limitations. Each trial migration run allows only 5 items to be transferred, and 20 runs.

  • Check the Enable Migration on the Next Run box to proceed.

3. Configure Migration Settings

  • Migration Direction: Define whether data flows from Jira to Monday or vice versa.

  • Handling of Previously Migrated Items: Choose how to handle items that were already migrated:

    • Replace (overwrite existing items).

    • Update (sync only new changes).

    • Skip (ignore already migrated items).

  • Selective Resync (Optional): If a previous migration was incomplete, choose specific fields to resync, such as Assignee, Status, and Description.

    • To resync all fields, enter ALL.

  • Selective Item Migration (Optional):

    • Enter specific item IDs to migrate only selected tasks.

    • Use JQL filtering for refined selection.

Important: Ensure that your JQL filter or item IDs align with the creation/updating date range to avoid missing items during migration.

  • Time Range Filtering:

    • Select a creation date range in the UTC timezone.

    • Only issues created or updated within the selected period will be migrated.

4. Schedule and Execute Migration

  • Click Schedule Migration to queue the process.

  • The system will begin migration during the next synchronization run.

  • Monitor progress in the Reporting section or the Latest Runs tab.

Migration runs appear under the Mode column as MIGRATION instead of SYNC.

5. Enable Continuous Sync After Migration (Optional)

If you want to keep the items in sync after migration:

  • Open the Integration Settings.

  • Click More > Enable Continuous Sync.

You can also uncheck the box below when you are setting up the migration.

This ensures that newly created tasks, issues, and updates flow between Jira and Monday.com moving forward.

Why Choose Getint Migration Over CSV Import?

Traditional CSV imports require manual data manipulation and lack automation, often leading to data loss and inconsistency. Getint eliminates these issues by providing:

1. Smart Field Mapping

✔ Getint enables precise manual field mapping, ensuring correct data alignment ❌ CSV imports require manual restructuring after import

2. Selective Migration

✔ Getint supports JQL filtering, item ID selection, and date-based migration ❌ CSV imports transfer all data, requiring manual clean-up

3. Real-Time Monitoring

✔ Getint provides sync logs, error tracking, and live migration updates ❌ CSV imports offer no real-time feedback

4. Seamless Integration

✔ Getint automatically syncs data post-migration ❌ CSV imports require additional steps to align projects and workflows

Need Help?

For any custom field creation steps, refer to our guide:

You can also migrate values from multiple source fields into one text field. You can read more about how to set up this option

For more tips, refer to .

Before migration, you must set up an integration between Jira and Monday.com. Follow our to configure the connection.

For additional assistance or troubleshooting, visit our .

Considering migration? with our experts to explore how Getint can optimize your Jira to Monday.com migration.

Pricing Page
help page
Starting the Free Trial and Access the Getint App
Master Jira Migration with Getint - Your Ultimate Guide
How to Create Custom Fields
here
Master Jira Migration with Getint - Your Ultimate Guide
Jira-Monday Integration Guide
Help Center
Schedule a Demo
Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!