On this page:
|
Migrating from Jira Server to Jira Data Center
This use case presents the same process as our our Migrating Projects From One Instance to Another use use case, which is applied to each of the source instances being merged to the Data Center. Migrating from Jira Server to Jira Data Center involves upgrading an existing instance to the new Data Center setup and merging your remaining instances into the Data Center instance.
...
Suppose you are a Jira System Administrator with multiple Jira Server instances that you want to move to Jira Data Center, but you need to retain all your project data, including configuration, history, and user mappings. You want to identify one of your Jira Sever Server instances to convert to Data Center, then merge your servers with your new instance as seamlessly and as easily as possible.
...
It is assumed you have installed Jira Data Center and configured your instance according to Atlasssian’s Atlassian’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.
...
Run the Object Dependencies Report on your source instance. This gives you visibility of where objects are used or referenced by other objects in your configuration. You can use this information to clean up your instance and to help you make the best choices for your export options.
Ensure that the naming schemes for user accounts are consistent between the source and target instances. You should not have the same user accounts with different user names, e.g.,
jsmithandjan.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.If you are cleaning your instance before export, you can use the Jira built-in XML backups to first back up your source instance.
...
Make a full backup of your target instance, including attachments.
Perform the migration out of office hours whenever possible and announce the planned downtime to your users. The larger the amount of data, the longer the process takes. This could mean running the process over multiple days , and splitting your projects across multiple export/imports.
Disable Outgoing Mail to not spam users.
Run a simulated import, and verify the import will make the changes you expect. This report helps you visualise visualize which objects will be created, those that will be modified, and those that or result in errors. You can then disable any actions you do not want to apply. You can also investigate any errors and make any necessary changes to the target instance. At this stage, you may discover that you need to resolve issues in the source instance and build a new export file. You can review our trouble shooting troubleshooting articles in the Project Configurator Knowledge Base to help you anticipate and resolve some common errors.
Perform the import on a test instance before moving your changes to a live environment.
...
Open a Jira session as a system administrator on the target Data Center instance.
Select Add-ons from the Jira Administration menu, then select Import Projects under Project Configurator in the left sidebar.
You have two options when uploading your zip file:
Option | Required Actions |
Server Upload |
...
- useful for larger files | Create a folder called |
...
|
...
under |
...
|
...
in the |
...
TARGET Jira installation. Copy the zip file created in the export to that folder. If your server is Linux-based, ensure that the zip file permission is set so that it is owned by the same operating system |
...
User |
...
and |
...
Group |
...
under which Jira is running. Select |
...
Server Upload |
...
in the |
...
Import Projects |
...
screen. |
Browser Upload |
...
- uploads the file directly from its original saved location on your computer, providing quicker access to locally stored files | Select |
...
Browser Upload |
...
in the |
...
Import Projects |
...
screen. |
Type the name of the exported file (include the ".zip" extension) into the Project File input box on the Import Projects page.
Ensure that the Run a Simulated Import option is selected.
Select any required import options. Keep in mind that the default options support 90% of import tasks.
Click Import Projects.
The Import Simulation results are displayed once the process is complete. The displays the configuration changes that will be applied to the target instance. Review the proposed changes, and
...
if you are happy with them, click Apply Configuration. When the process is finished, your project(s) will be in the target instance, including their configuration, issues, and attachments.
Review the import log and the target instance to ensure the migration was as expected.
Repeat this process for each of your export files created for the source
...
Congratulations
...
instances
...
.
...