The Project Configurator Checklist provides a quick reminder of the prerequisites, key tasks, and best practices that help ensure that your data migrations run smoothly. 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.
Have Jira System Administrator permissions
Have a paid PC license; you must have a paid license to import to a production instance
Jira language and locale are the same on both source and target instances; your Jira versions should be close to each other, if not the same1
Apps installed on your source Jira instance are also installed on your target instance2
Ensure that the naming schemes for user accounts are consistent between the source and target instances3
Provision a staging instance to test before importing to a production environment; this should be the same version as your source and target instance to ensure test results are accurate
Run the Object Dependencies Report at the source instance to give you visibility of where objects are used or referenced by other objects in your configuration
Create backups of your source and target instances4
Disable outgoing mail for user accounts5
Run an Import Simulation in the target instance before proceeding with actual import
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 attachments6
If the export process fails, to save space on your local disk, manually clear these files before launching the export process again
Review migration resources
If you are new to using Project Configurator for any migration task, refer to our use cases and demo videos to help you identify how best to use it
Review our knowledge base articles to help you anticipate or easily resolve some common errors
1 It is recommended that your Jira versions be the same on both source and target instances. This applies especially to complete project imports. You can import project data from an earlier version of Jira, however the greater the difference in Jira versions between the source and target, the greater the possibility of issues arising from the migration. If your versions are not the same when importing complete projects, ensure that the target instance has the more recent Jira version as differences between the two could cause the data import run by the built-in Jira data import functionality to fail.
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. It is also important that the apps on both instances are the same version otherwise the built in Jira data import functionality that PC uses will give errors when importing issue data.
3 You should not have the same user with different user names, e.g.
jan.smith. If you are using an external user directory such as LDAP or Active Directory, ensure that these users exist in the target instance before the migration.
4 Use the Jira built-in XML backups for your source instance if cleaning the instance prior to export.
5 To learn how to disable outgoing mail, see Atlassian’s guide to configuring email notifications.
6 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.