A complex Jira migration
Type of assignment: Atlassian consultancy
Client: A large supermarket chain in the Netherlands
One central place to collaborate
Our customer, a well-known Dutch supermarket chain, uses Atlassian software to support their agile software development. Specifically, they use Jira for planning, issue tracking, and monitoring project progress. The end goal of this project was for their teams to work in one centralized Jira environment to facilitate reporting across teams and stimulate collaboration.
Before the start of this project, our customers' situation was less than ideal. Some of their teams worked in an Atlassian Cloud environment, while other teams worked in an on-premise environment. On top of that, the environment was also shared with multiple organizations. Our customer asked us to come up with a solution in which the on-premise instance of Jira would be phased out and migrated to the Cloud environment.
Migrating an on-premise Jira instance to a Cloud environment is no easy feat. There are some substantial differences in the underlying infrastructure and in the way Jira is structured. We encountered a number of challenges during this customer's Jira migration, including:
- Atlassian Cloud does not offer an option to import projects (JRACLOUD-31806)
- The shared environment uses Jira version 6.3, which is no longer supported by Atlassian (end of life)
- The shared environment could not be changed as it is also used by other organizations
- Some user names did not match