Solargis: Migration of Jira Software from Server to cloud
When the trial migration of Jira software didn’t go as planned at Solargis, they turned to us. Thanks to meticulous planning on our side and client’s active involvement in the preparatory work, we managed the production migration of the entire platform, including several applications, in one evening.
05/2021 - 06/2021
Atlassian Jira Software Cloud
Solargis supplies meteorological data and software and consulting services to help solar power plants around the world identify weather-related risks and optimise their performance.
The customer contacted us to help with the migration of a medium-sized Jira Software from server to cloud when they performed a test migration – using a standard migration tool – that did not go as expected. In addition to transferring to a supported platform in a single day, the customer also needed to clear unnecessary data, provide GSuite for user management and migration of Tempo, Email This Issue, and Smart Checklist applications.
The project involved a technical team of 3 people – the administrator who managed Jira server and a representative of the project office, an on our part the Atlassian solution architect. Since the customer performed part of the preparatory work (upgrading Jira to the current version, cleaning up unnecessary data) and complete verification of the transferred instance themselves, we managed the entire migration faster.
Before the migration itself, we carried out an analysis of the environment, i.e. a revision of the overall state of Jira, an evaluation of the complexity of migration and the implementation of the initial evaluation migration. During the evaluation migration, we discovered at first glance an invisible inconsistency of data, which we subsequently solved with Atlassian support. After that, nothing prevented us from planning and executing a test migration.
The test migration helped us verify the correctness of the proposed procedure and confirm that nothing stands in the way of production migration anymore. After the successful evaluation, we prepared a production migration plan, which was carried out in one evening using an XML backup. The following day, we evaluated and approved the migration.