Atlassian migrate to cloud
If you’re planning on migrating to Atlassian’s cloud service then there are a number of tasks you need to consider and prioritize before initiating the migration process. Our case studies demonstrate Think&Do’s approach and what is involved in a typical migration for both small or large companies
Atlassian migrate to cloud case study – boutique software gaming company
Client has been using Jira for some time but no longer have the admin capability to support the product and would like to move to the cloud.
his medium size gaming company had seen its use of Jira grow and were now becoming more reliant on the product to support their business practice. They no longer had the admin capability in-house to support a business-critical application and were looking to outsource the overhead by moving to Jira Cloud.
Given the size of the organization and their instance of Jira, this was a relatively quick engagement. It was important to understand which apps were in use and whether they would continue to function within a cloud instance of Jira. After some analysis of the customer’s Jira instance, we were able to identify which apps would not be supported and provide alternatives and, where there was no alternative, we were able to demonstrate how to replicate that functionality with some bespoke development. After we understood what was being migrated and performed some housekeeping, we migrated the Jira Server to the cloud over a weekend to minimize the impact of downtime.
Admin overhead is significantly reduced, and the client is happy that the bespoke development has replicated the app functionality that wasn’t available natively within Jira Cloud.
Atlassian migrate to cloud case study – large business
Our client, a large insurance company, was working with multiple instances of Jira, across two locations are wanted to merge their Jira instances before migrating to the cloud. A lightweight approach was not appropriate in this instance and instead, we undertook several rounds of requirements gathering, analysis, and investigation to ensure that the complexities of the merge and migration were fully understood and documented and that the approach was clear to everyone involved.
The complexities of the merge and migration, coupled with the client’s more traditional approach to the business process, meant that this project was completed over several months, something that the client understood and signed-up to from the beginning thanks to the detailed requirements gathering phase. When dealing with a client that doesn’t typically work in an agile way (or when dealing with a project that runs over several months), it’s important to ensure good communication is maintained. Our Project Manager kept the client up-to-date with daily check-ins and weekly reports detailing what had been completed, what was left to do, and any blockers that would prevent the project from being delivered on time.
The client is happy that their instances have been rationalized and that the housekeeping completed as part of this phase has resulted in a cleaner and easier to use Jira instance.