Skip to content
Case Study

greenconsus — Jira & Confluence Cloud Migration

greenconsus — migration to Atlassian Cloud

Recently, we have noticed a great emphasis by Atlassian on the use of cloud versions of its products. For most SME companies, it is much more advantageous to use the most modern and flexible cloud products, where the effort associated with the maintenance of servers and applications is eliminated and the need to ensure the security of applications is minimised.

Atlassian allows you to continue to use its applications (Jira, Confluence and others) even after the support license expires, but without the possibility of updating with new functionalities and improvements and without support from the security point of view. The applications thus gradually become obsolete and do not meet the customer's expectations. They also become a dangerous invitation for potential attackers.

For the reasons mentioned above, the greenconsus company decided not to maintain its solution anymore but to migrate data to the Atlassian Cloud and use cloud versions of the products.

How we approached the migration

Data analysis was the first step of the migration project, which we implemented in cooperation with the technology company VisionLake. What will need to be migrated? Which users will be affected by the migration? What to do with historical data? How to maintain the consistency of information about employees and users who are no longer active but still need to know their details?

In the second step, a short migration feasibility study was carried out when the company was already actively using Atlassian Cloud solutions, and new data was added daily. The migration had to be done so that the customer did not lose new data (generated by using the cloud version) or old data (stored in the on-premise Server version).

Due to the significant differences between the current cloud version and the server version the customer had, it was not technically possible to implement a one-time migration to the most recent cloud version. Therefore, it was necessary to find out which versions of the applications were still compatible, and thus it was necessary to perform a multi-step migration. It was also necessary to solve the licensing for the given migration since, without licenses, it is impossible to update to compatible versions.

After a successful migration, a data consistency check was performed in both systems, and we used a bit of scripting magic to fine-tune information about users who are not active in the new cloud solution.

Atlassian Jira Cloud after the migration
Jira running on the modern Atlassian Cloud after the migration.

Outcome

And as a bonus, in addition to the migrations, a check of the settings of individual projects in Jira, authorisation settings, notifications and the reduction of the number of Custom Fields was also carried out. The result is a modern and flexible solution with significantly increased data security. Server maintenance and restoration costs have been reduced, and the company has a better overview of resources and can plan work better.

A modern, flexible Atlassian Cloud setup with significantly stronger data security — lower maintenance costs and a clearer overview of resources and planning.

Provided services

Consulting

Key technologies

Atlassian Jira Atlassian Confluence

How We Work

Pragmatic migrations — done without losing data and with security built in — are part of what we do. We figure out the path, handle the licensing and compatibility, and verify the result. Explore our services or read more of our case studies.

Planning a migration you can't afford to get wrong?

We map the path, handle compatibility and licensing, and verify nothing is lost. No pitch — just a focused conversation about your move.

Schedule a call with us