Asana to Jira migration
Last updated
Was this helpful?
Last updated
Was this helpful?
Migrating items from Asana to Jira with Getint is an excellent option as it facilitates a smooth and efficient transfer between platforms. Getint automates the migration process, preserving essential details and minimizing disruptions to your projects. Its intuitive interface and powerful features simplify the complex task of moving data, making it an ideal choice for teams looking to transition or integrate project management tools effortlessly.
To learn more about how our tool works and how you can maximize its potential, visit
For migrating historical items, you will need to have a migration license with us as an integration license won’t suffice in this case.
The migration licenses offer different features depending on the scale of your migration.
In case you would like to learn more about and purchase our migration license, please access our pricing page for more details and select the "Migration" tab:
When you set up the integration, new items created in Asana or Jira will sync across both platforms. To avoid issues with live environments, you can disable the integration right after setup, schedule migration with the integration off, or pause work in both systems during the migration.
2. With your integration set, click on the "Migrate Data" button, located in the left side menu:
Check the "Enable Migration on Next run" box to continue.
3. On this screen, you can customize your migration by choosing the direction (Right to Left or Left to Right), determining the handling of previously migrated items (replace, update, or skip), and specifying any fields you want to resync to capture updated data post-migration.
Configure your migration preferences, then either enter the specific item IDs you wish to migrate or leave the field blank to, instead, add a date range at the bottom to include items created within that period. The tool will migrate all items that fall within the specified date range, so please make sure that in case you want to migrate specific items by their IDs, to fill a date range that covers the date of creation of these items.
4. With the migration set per your preference, click "Schedule Migration" at the bottom. The tool should migrate the items based on the specifications on the next synchronization run.
5. After scheduling a migration, you can observe the results of your migration through the reporting section or the "latest runs" from the left menu.
Your items should have been successfully migrated, you can check the receiving end to verify the integrity of the migrated data (note that migration runs are displayed as "MIGRATION," under the "Mode" column)
To access our app and install the trial, please go to:
1. You can check the steps for setting up this integration on our informative guide:
If you are using the app's trial version or have a limited integration license, you'll see a warning indicating that you have a restricted number of Migration Runs available. Each Migration Run is capped at migrating a maximum of 5 items. If you’d like to learn more about the different licensing models and pricing, please visit:
If you experience any issues while performing the process above, please raise a ticket through our
