Overview
This article explains the best practice of Migrating data between Jira Servers using Configuration Manager for Jira app.
Best Practice
The Configuration Manager for Jira app (CMJ) can migrate Project with issues along with the associated attachments. The Configuration Manager app is designed to support the export and import snapshots from different Jira versions. You can migrate projects from one Jira version to another.
It's always ideal to have the same version of Jira running on both source and target instances. However, with the latest version of Configuration Manager for Jira app, one can have two different Jira versions on the source and target instances provided the version of Configuration Manager for Jira app is identical.
Example: Configuration Manager for Jira v6.6.8 is supported for Jira versions between 7.8.0 to 8.11.0. In the 6.6.8 version of CMJ, any version of Jira can be installed between v7.8.0 to v8.11.0 in the source and target, but the CMJ app version should be identical to v6.6.8 at both places.
Another important point to remember: If the Jira versions are different, the target instance shouldn't be running on an older version than the source instance.
Example: Jira source instance is on v7.8.0 and the target is on v8.10.0. Then CMJ Works perfectly. However, if the Jira source instance is on v8.10.0 and the target is on v7.9.0, the CMJ might not give accurate results.
Please check the compatibility matrix to make sure the version of the Configuration Manager for Jira (CMJ) is identical between the data center Jira instance and server instance.
For more information, refer to this link: https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784162/Compatibility+Matrix