Skip to main content
System StatusContact Support Agility Community

Create a Mapping to Migrate Assets from Jira to Agility (Beta)

This is a beta feature in Agility Connect 21.0. Do not use this in a production setup. 

You can now create a mapping solely for the purpose of migrating your Jira assets to Agility. clipboard_ef347add91f43b354c286b67a20f9a85b.png

Use the Data Migration configuration to specify the date range to migrate data. However, the maximum window for data migration is three months.

Once you create a mapping for the purpose of data migration, select the Schedule Now check box (it is mandatory to schedule the data migration to run immediately) and activate the mapping, all the Jira assets created or updated within the given date range are fetched and synced with the Agility. 

You have three options when you want to activate the mapping as shown in the following illustration. 



  • You can activate both the data migration and data sync, which is what you would do if you want to have the mapping do the data migration immediately and continue with the data sync going forward. 
  • You can activate data migration alone, which means the mapping would just do the data migration and not be doing the live data sync for future sync events.
  • You can activate data sync alone, which means the mapping would just do the data sync and not the data migration. This is as good as disabling the Data Migration configuration.  

A mapping, created for the sole purpose of data migration cannot be modified for any other purpose at a later point in time. 

You cannot use (modify) an existing mapping (that has been activated at least once after creation) to do the data migration. 

While you can migrate data from Jira to Agility, you cannot use this feature to migrate data from Agility to other tools.