# Jira to Zendesk Migration Guide Migrating data from Jira to Zendesk is more than a technical transition — it’s a strategic move to unify engineering workflows with customer support operations. Whether you’re shifting responsibilities across teams, retiring legacy tools, or preparing for a broader digital transformation, Getint provides a structured, reliable solution to bring your Jira issues into Zendesk with clarity and control. This migration is not just about transferring tasks or tickets. It’s about preserving the integrity of your historical data, aligning workflows across departments, and ensuring that no context is lost when engineering hands off to support. With Getint’s Migration Feature, you can move key issue types, comments, attachments, and custom fields into Zendesk in a single, organized process, tailored to fit the nuances of both platforms. In this guide, we’ll show you how to configure and execute a successful Jira to Zendesk migration using Getint. ### Requirements for Migrating Historical Data #### 1. 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://docs.getint.io/guides/migration). ### Preparing Your Environment Before Migration #### Handling Fields That Cannot Be Mapped Before starting the migration, ensure that all required custom fields are created and available on both Jira and Zendesk. If a corresponding field is missing, it must be created in advance to allow proper field mapping. For help creating custom fields, 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#hardbreak-zendesk). #### Migrating Values from Fields Without 1:1 Mapping If a Jira field does not have a direct counterpart in Zendesk (e.g., priority, component, or assignees), you can still migrate the information using the **Use label from the other side** setting. Steps: 1. Create a custom Text field in Zendesk.

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

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 into 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 Zendesk Migration #### 1. Set Up a Jira to Zendesk Integration Before migrating, you must set up a working integration between Jira and Zendesk. Follow our full [Jira-Zendesk Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-zendesk-integration) to configure your connection properly.

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

{% hint style="info" %} If you're on a trial version, a warning will appear regarding your migration limits (5 items per run, 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 Zendesk.

* **Handling 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**.

Alternatively, you can uncheck the disable box when setting up the migration.

This ensures that **newly created** tasks, issues, and updates flow **between Jira and Zendesk** moving forward. ### Why Choose Getint Migration Over CSV Import? Traditional CSV methods can result in data loss, manual fixes, and inconsistencies. Getint Migration offers key advantages: #### 1. Smart Field Mapping * ✔ Allows precise manual field mapping for accuracy * ❌ CSV imports require manual rework after upload #### 2. Selective Migration * ✔ JQL filtering, item ID targeting, and date-based migrations * ❌ CSV imports require entire bulk imports #### 3. Real-Time Monitoring * ✔ Live sync logs, error reports, and migration tracking * ❌ CSV imports offer no live visibility #### 4. Seamless Transition * ✔ Integrated post-migration syncing * ❌ CSV requires additional manual alignment ### Need Help? If you need further assistance with your Jira to Zendesk migration, please open a ticket at 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 Zendesk** migration.