Migration and upgrade can be done at a single time ?

Question

We are in a process of migrating our atlassin apllications from windows servers to linux servers.

Current Versions
____________________

Jira 7.1.9, Crowd- 2.11.1, Bitbucket- 49.1, confluence -5.10.0

So while moving from windows to linux, we are planning to go for the upgraded versions. (Jira-7.3.8, Confluence -6.2, crowd - 2.11.2)

So can we proceed with same upgrade and migration at a time ?

What are the actions to be carried out ?

We are using MSSQL DB, DB side any change need to be done, for upgrade ?

We are familiar with migrating from one server to new server, but for upgrade what actions are need to be done?

Is license is need to be renewed idf we are going for upgraded versions.

Andy Heinzer · Answer

That depends on the expiration date of the license.   If the licenses have already expired, then you need to make sure that the version you are upgrading to was released by  Atlassian before the expiration date on your license, else you won't be able to upgrade that product.

If the licenses applied have an expiration date in the future, then yes you can use the same license.

But typically you don't have to apply this license key to a new installation when migrating because the license is stored in the database, and Jira will let you simply import your XML backup during the setup, or you can connect to a clone of your database that contains that same license key.

Technically your license agreement states that the license should not be applied to more than one installation at the same time.  However Atlassian does not actively prevent you from doing so because we're not trying to make migrations more difficult than they need to be.

vivuu · Answer

Thanks for the guidelines . Can same license can be used for the upgraded versions.

Andy Heinzer · Answer

Technically it is possible to both migrate and upgrade at the same time, however it does make the process considerably more complicated at times.  And it might make troubleshooting unexpected problems worse because multiple things have changed at the same time which can make figuring out the source of some problems more difficult sometimes.

That said, Jira does allow you to do this.  The guide in Migrating Jira applications to another server does a good job at detailing all the information that has to be done and in what sequence to make sure this will work.  One common mistake users make is they forget to copy their attachments and flat files over to the new server before importing the XML backup.   The documentation explains that this has to happen in that sequence to make sure this data is upgraded, but we still see cases with this step gets skipped.

The Crowd Guide on Migrating Crowd Between Servers though explicitly states these steps are for cloning the existing environment.  However you should be able to follow the method #2 in Upgrading Crowd as a means to complete this upgrade.

With Confluence, the same concepts apply as the Jira upgrade.  It can be done, but you have to make sure that you closely follow the steps in Migrating Confluence Between Servers.

I would also recommend reviewing all the upgrade notes for the associated products.

* JIRA Core release notes - Atlassian Documentation
* JIRA Software release notes - Atlassian Documentation
* Crowd Release Notes - Atlassian Documentation
* Confluence Release Notes - Atlassian Documentation