Can Jira v7.8 projects migrate to Jira v8.11.1 version using ConfigurationManager?

[Shankar.kalagadandu]

We have 2 separate instances

Instance1: Jira v7.8.0 hosted in AWS 

Instance2: Jira v8.11.1

We are planning to migrate all projects from Jira v7.8.0 to Jira v8.11.1 using configuration manager. Please suggest the approach.

[Gonchik Tsymzhitov]

Hi @Shankar.kalagadandu , 

you're already set the some info. 

You have a few option to consolidate: 

1. Configuration manager for Jira - that app, is cover all needful things, also not needed after make after too much cleanup. (json based migrations) 

You need to think about downtime, if you plan merge a huge installation in one shot, when you can meet with bottleneck. Hence you can follow with next step.

2. Project Configurator - you need to make the same fields, many preparation, and note that app use the xml backup functionality. (if your instance too different, is not good way. it's my subjective opinion after migration several instances). 

https://confluence.atlassian.com/adminjiraserver/merging-jira-instances-938847939.html

3. You can do by yourself consolidation via json.

Please, checkout the next one as well.

https://confluence.atlassian.com/jirakb/merge-multiple-instances-of-jira-server-244352137.html

4. Another option, do sync with 2 Jira, via Backbone app.

[Shankar.kalagadandu]

Hi @Gonchik Tsymzhitov , Thanks for information.

Actually we have commercial "Configuration Manager" add-on in our Target environment.

Also we upgraded source QA environment to v8.11.1. and planning to migrate the project in QA( source QA to Target QA). both are in same versions.

But Source Prod is still in v7.8.0. Can I use Configuration manger to migrate the projects from v7.8.0 to 8.11.1 when Production migration? Please advise. 

[Milan Chheda [INFOSYSTA]]

Hello @Shankar.kalagadandu ,

Yes, you can use Configuration Manager to merge projects along with its configurations from one instance to another, but as I remember, you need to have same version of JIRA as well as same version of add-ons installed on the both the instances else it might result in problems during merge.

I would highly recommend you to perform this on staging or development instance before performing the merge on production.

Thanks,
Milan