# Jira to Asana Migration Migrating tasks and projects from Asana to Jira is an important process when transitioning between project management platforms. Whether you're unifying workflows, scaling operations, or consolidating tools across departments, Getint’s Migration Feature ensures a structured and accurate transfer of historical data. Unlike standard integrations that sync only newly created or updated items, the migration feature enables a one-time, bulk transfer of existing data while preserving essential details such as custom fields, status, relationships, and item types. This guide walks you through the steps to configure and execute a migration from Asana to Jira using Getint. ### Requirements for Migrating Historical Data #### Migration License Migrating historical data requires a migration license, as integration licenses alone do not support this functionality. Migration licenses are billed separately. To purchase a license, visit our [Pricing Page](https://www.getint.io/pricing) and select the "Migration" tab. You can also contact our team via the [Help Center](https://getint.io/help-center) for assistance. Before purchasing, we encourage you to test the process using our trial version, which allows: * Up to 20 migration runs * A maximum of 5 items per run To begin your trial, visit: [Getint for Asana and Jira on Atlassian Marketplace](https://marketplace.atlassian.com/apps/1223932/asana-integration-for-jira-2-way-sync-and-data-migration?hosting=cloud\&tab=overview) For best practices and advanced tips, see: [Master Jira Migration with Getint](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 starting the migration, ensure that all required custom fields exist on both Asana and Jira. If a field does not exist on one side, you must create it before attempting to map it. Need help? Refer to: [How to Create Custom Fields](https://docs.getint.io/guides/integration-synchronization/how-to-create-a-custom-field-in-all-supported-software#hardbreak-asana). #### Migrating Values Without 1:1 Mapping If a field in Asana doesn’t have a direct counterpart in Jira, you can use the **Use label from the other side** option to inject its value into a custom text field. **Steps:** * Create a custom Text field in Asana.

* In the Getint field mapping screen, map the source Asana field to the Jira text field.

* Enable **Use label from the other side** to insert the original value.

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

To avoid live data conflicts, we recommend either disabling the integration after setup or scheduling the migration outside of active working hours. #### 2. Access the Migration Feature Once your integration is set: * Click **Migrate Data** from the left-side menu.

{% hint style="warning" %} 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:** Choose whether data flows from Asana to Jira or vice versa.

* **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 Run the 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 Asana 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 Asana** migration.