The Project Configurator Checklist includes prerequisites, key tasks, and best practices to help ensure that your data migrations run smoothly with Project Configurator. We recommend that you refer to the Project Configurator Checklist whenever you prepare for a migration process whether you are merging multiple instances or simply promoting a few changes from a development environment to production.
Project Configurator Migration Checklist
|1||It is recommended that your Jira versions be the same on both source and target instances. While this is not a necessary requirement for migrations to work, it is best practice. The greater the difference in Jira versions between the source and target, the higher the possibility of issues arising from the migration.|
|2||If an app provides configuration objects, such as custom fields, in the source instance but is not installed on the target instance, errors can occur due to these objects being missing in the target.|
|3||PC only exports users from the Jira internal directory so any users in other directories will need to be created before the migration.|
|4||Use the Jira built-in XML backups for your source instance before exporting projects or when cleaning an instance. This is best practice in case a rollback is required for unwanted changes that occur during an export.|
|5||When making changes to a production environment, define and announce an outage window to avoid performance impacts on users, or in case a rollback is required.|