After Atlassian announced its change of strategy to become a cloud-first company, many of us are trying to find the most effective way and conditions for his or her Atlassian Cloud migration. during this blog post, you will find some tips and considerations when migrating to Jira Cloud with an expired Jira Server license. Considering migrating Jira or Confluence to Atlassian Cloud? visit sentify.co
To migrate to the cloud, existing server users have a time window with an expired license – detailed below. To do this, it is necessary to consider a series of steps i.e., the instance has not been updated to the most recent version. Whatever your case, we’ll provide more context as we walk you through each step needed to achieve this objective: Download Report.
Determine if you need to upgrade to a newer version
If your current server license has expired or is about to expire, it is still possible to migrate to the cloud at no additional cost. Considering the work that this process may entail, Atlassian Servers offers a free 60-day cloud migration trial for clients whose maintenance is similarly finished.
In most cases, it is possible to migrate directly from your current server site to the cloud. If you have an older version of the server, you may need to upgrade to a newer version before you can migrate using Jira Cloud Migration Assistant.
Which versions are supported before migration?
- To migrate to Jira Cloud, you must have Jira Server (or Jira Data Center) version 7.6.0 or later. If you have an earlier version, you will need to upgrade to the newer version.
- To migrate to Jira Service Management Cloud, you must be on Jira Service Management 3.9.0 or later. If you have an earlier version, you will need to upgrade to the next version.
Assuming the migration process requires integrating Bitbucket Server or Bamboo, examine this metrics. In that case, it will inform you whether you have a compatible version of Bitbucket Server or Bamboo before starting.
Let’s say you have a non-supported server or data center version and you don’t have an active server license maintenance (which needs to be upgraded). In that case, it is possible to fix it by using a free trial license to upgrade in preparation for your migration. If you have further questions about this, contact our team of Atlassian Certified Professionals.
After considering the upgrade of your instance, let’s consider the following:
Using trial licenses to upgrade and migrate
If you have an unsupported version and don’t have maintenance enabled for your server license (which is required to upgrade), use a free evaluation license to upgrade and be ready for migration. This can be done from my.atlassian.com.
Given the timeline of changes established due to Atlassian’s cloud-first strategy, it is no longer possible to create a new evaluation license for the server (check the schedule for server license changes); However, the Data Center Evaluation license can be used for server installations. Please note that this type of evaluation license only lasts 30 days. If you believe you will need more time to complete the migration, request an extension of 90 days.
Why upgrade your current version?
The answer to this question depends on the product and deployment option. However, the overall reason for upgrading is to allow the system to match the features available for your server or data center product with those available in the cloud. Let’s look at product by product from a general point of view:
- For Jira, it is recommended to switch to an improved version as version 8.0 brought significant changes in terms of reindexing as they updated the Lucene library responsible for indexing in Jira; It is also recommended to disable apps that are not compatible or update them to current versions as these may block Jira updates.
- Check out this upgrade matrix, which shows the features most relevant to each version.
- For Confluence, follow the steps for this process described by Atlassian in its documentation. It is important to check that you are reading the documentation regarding the tool version you have. This link corresponds to version 7.17 (look for it at the top-right of the screen).
If you need to upgrade to a supported version, follow the step-by-step upgrade instructions for your product. In addition, if you want to achieve a successful version upgrade, it is important to keep the following points in mind:
- Back up your site before upgrading.
- Perform pre-upgrade checks, including status checks (where supported).
- Set up a test environment in which you can simulate the upgrade.
- Atlassian’s documentation provides step-by-step instructions on each of these processes.
The most cumbersome step in this process is to upgrade the version, which will allow you to use the migration wizard we mentioned at the beginning of this article. After the update, be sure to review the guide created by Atlassian on Migration Planning for common questions, best practices, pre-migration checks, and step-by-step instructions on migrating.
If you need further assistance with this process of capturing the Atlassian Cloud First strategy, contact us. We’ll help you, whether you need help managing your licenses, more information about migration planning, technical troubleshooting, or perhaps you need support on your strategy or specific guidance based on a specific method be required.