Use Case 3: Migrating from Jira Server to Data Center with Project Configurator

Assumptions

It is assumed that you have installed Jira Data Center and configured your instance according to Atlasssian's DC installation guide.  It is also expected that you are familiar with the concepts of migrating and merging Jira instances as described in the following Atlassian guides: Migrating Jira Instances and Merging Jira Instances.

Setup & Best Practice

Migrating from Jira Server to Data Center involves upgrading an existing instance to the new Data Center setup and then merging your remaining instances into the Data Center instance. While we’ve tried to make Project Configurator as easy to use as possible, there are a number of things you should do to ensure your data is safely and successfully imported.

• Ensure Project Configurator is installed on both your source and target instances. You can install Project Configurator either through the UPM or by downloading the app from the Atlassian Marketplace. Apply your license to the target instance only – Project Configurator will allow you to export without a license on the source instance. You must have Jira Administration permissions to complete this process. 
• Ensure that the same apps are installed on both the source and target instances. You should also ensure that all your instances are on the same Jira version and in the same language and locale.
• All user accounts must be the same in both the source and target instances whether or not they are used in the target instance.
• Make full backups of your source and target database including attachments.
• Read the supported types of objects list verify that the objects you wish to migrate are supported.
• Disable Outgoing Mail to not spam users.
• For each instance, run the Object Dependencies report to identify all objects that are directly or indirectly part of the configuration of any project in your instance, and where they are being used or referenced by other configuration objects. 

• After you have moved your first instance, verify that conflicts don’t exist between your source and target instances and if they do, decide how each of them should be handled.

• Simulate the import on a staging environment to check the system load and to ensure that your target Jira instance performs the way that you expect.

• Perform the configuration promotion out of office hours. The larger the amount of data, the longer the process takes. This could mean running the process over multiple days; splitting your projects across multiple export/imports.