When you create a new Jira-connected project in Ketryx, you have two options for Jira configurations:

1. Use Ketryx Issue Types, Screens and Workflows
2. Use existing Jira configuration

If you would like to establish a new project utilizing Ketryx default items and workflows, you may desire migrating existing data into that project. This FAQ outlines steps to executing your migration:

1. Download the Ketryx connector app for Jira. See this FAQ about what happens when the app is downloaded.
2. Deconflict issue types in Jira - Review this FAQ and de-conflict any issue types in Jira that overlap with Ketryx defaults. If conflicting issue types are not de-conflicted prior to connecting a project to Ketryx, global configuration changes may occur.
3. Determine if you'd like to use a monolithic or SoS architecture. Most clients that pursue a SoS architecture do so for the reasons of aligning with team structure, or supporting versioning and reporting of components at different rates. This FAQ summarizes the benefits of this architecture. This video describes cross-project referencing in more detail.
4. Establish your Ketryx projects - Create company-managed jira-connected Ketryx project(s), and establish cross-project referencing (if desired). The project must be created in Jira before establishing a new project in Ketryx. This must be a company-managed project in Jira.
5. Prepare data for migration -
   1. Itemize configuration items from source systems in xls/csv format.
   2. If items are already in Jira, download your items so that they can be re-uploaded to a new project.
6. Prepare Jira and Ketryx projects for migration (optional) - To support mapping of risks, custom item types or custom fields, you may need to configure Jira screens and Ketryx field mappings in the advanced settings, in advance of data import. This FAQ summarizes how to create custom fields in Jira and Ketryx.
7. Map data between existing fields and Ketryx fields - Use Jira's external systems import to import data (without any relations) into the respective Jira fields and projects.
   1. Map your CSV columns to Jira fields during the import process.
   2. If you have more than 1,000 items, you may need to split your data into multiple CSV files (each with fewer than 1,000 items).
   3. If pursuing a SoS, import and field mapping will need to be done project by project
8. Establish trace between items - After data has been imported to your Jira projects, you can either establish trace manually, or connect with your client operations representative for support. See this FAQ about Ketryx relations v. Jira relations. 

Please reach out to us with any questions!