Project Configurator Checklist
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 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.
__ Have a paid PC license; you must have a paid license to import to a production instance
__ Jira version, language, and locale are the same on both source and target instances1
__ Apps installed on your source Jira instance are also installed on your target instance2
__ All User accounts are the same in source and target instances3
__ Provision a staging instance to test before importing to a production environment
__ Create backups of your source and target instances4
__ Disable outgoing mail for user accounts
__ Read the list of supported object types to make sure the objects you expect to migrate are supported
__ Run the Object Dependencies Report at the source instance
__ Run the Import Conflict Detection Report in the target instance after the export
__ Follow a tested and defined process for all your migration tasks
__ Limit disruption to users by performing tasks out of hours; consider staging the import through separate files and limiting the exporting of attachments5
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 considered 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.