Jira to Asana Migration
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
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 and select the "Migration" tab. You can also contact our team via the 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:
For best practices and advanced tips, see:
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.
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.
To avoid live data conflicts, we recommend either disabling the integration after setup or scheduling the migration outside of active working hours.
Once your integration is set:
Click Migrate Data from the left-side menu.
If you're on a trial version, a warning will appear regarding your migration limits (5 items per run, 20 runs).
Check the Enable Migration on the Next Run box to proceed.
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.
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.
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.
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.
Traditional CSV methods can result in data loss, manual fixes, and inconsistencies. Getint Migration offers key advantages:
✔ Allows precise manual field mapping for accuracy
❌ CSV imports require manual rework after upload
✔ JQL filtering, item ID targeting, and date-based migrations
❌ CSV imports require entire bulk imports
✔ Live sync logs, error reports, and migration tracking
❌ CSV imports offer no live visibility
✔ Integrated post-migration syncing
❌ CSV requires additional manual alignment
Need help? Refer to:
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 migrating, you must set up a working integration between Jira and Asana. Follow our full to configure your connection properly.
If you need further assistance with your Jira to Asana migration, please open a ticket at our
Considering migration? with our experts to explore how Getint can optimize your Jira to Asana migration.
