This documentation has moved. For the most recent documentation, check out Please update your bookmarks and links.

Skip to end of metadata
Go to start of metadata

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

  • 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 or development instance to test before importing to a production environment
  • Create backups of your source and target instances4
  • Disable outgoing mail for user accounts
  • 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
1It 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.
2If 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.
3PC only exports users from the Jira internal directory so any users in other directories will need to be created before the migration.
4Use 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.
5When 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.