# Jira to Monday.com Migration 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 [**Pricing Page**](https://www.getint.io/pricing) and click on the **Migration** tab for more details. Contact our team through our [**help page**](https://getint.io/help-center) 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: [Starting the Free Trial and Access the Getint App](https://docs.getint.io/getting-started-with-the-platform/starting-the-free-trial-and-accessing-the-getint-app). Also, see our full migration guide: [Master Jira Migration with Getint - Your Ultimate Guide](https://www.getint.io/blog/mastering-jira-migration-a-comprehensive-guide-with-getint). ### **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. For any custom field creation steps, refer to our guide: [How to Create Custom Fields](https://docs.getint.io/guides/integration-synchronization/how-to-create-a-custom-field-in-all-supported-software). #### **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.

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

3. 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. You can also migrate values from **multiple source fields into one** text field. You can read more about how to set up this option [here](https://docs.getint.io/guides/integration-synchronization/how-to-map-fields#concatenating-fields). For more tips, refer to [Master Jira Migration with Getint - Your Ultimate Guide](https://www.getint.io/blog/mastering-jira-migration-a-comprehensive-guide-with-getint). ### **How to Set Up Your Jira to Monday.com** **Migration** #### **1. Set Up a Jira to Monday.com** **Integration** Before migration, you must set up an integration between Jira and Monday.com. Follow our [Jira-Monday Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-monday.com-integration) to configure the connection.

#### **2. Access the Migration Feature** Once your integration is set, open the **Getint App** and: * Click **Migrate Data** from the left-side menu.

{% hint style="info" %} 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.** {% endhint %} * 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.

{% hint style="warning" %} **Important:** Ensure that your **JQL filter or item IDs align with the creation/updating date range** to avoid missing items during migration. {% endhint %} * **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**.

{% hint style="info" %} Migration runs appear under the **Mode** column as **MIGRATION** instead of **SYNC**. {% endhint %} #### **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 additional **assistance or troubleshooting**, visit our [**Help Center**](https://getint.io/help-center). Considering migration? [**Schedule a Demo**](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team) with our **experts** to explore how **Getint** can optimize your **Jira to Monday.com** migration.