• There are no suggestions because the search field is empty.

Atlassian Migration Case Study

One of the Largest Bamboo Instances in the Atlassian Ecosystem

Global mergers and acquisitions are currently recovering after an initial hit from the pandemic–– M&A activity dropped by 50% in Q1 2020, but has increased by 24% this year as companies have adapted. Data transfer is an essential part of ensuring a smooth M&A process, and an Atlassian platinum solutions partner can be an invaluable asset to navigate a successful cloud migration.

One marketing solutions company looked to up-level their offerings and acquired a digital marketing firm to further develop their AI capabilities and better leverage the data they’ve acquired from supporting their clients. As part of this acquisition, the marketing agency needed to migrate data from the acquired company to their hosting environment. This meant transferring four Atlassian applications: Jira, Confluence, Bitbucket and Bamboo. Each of these tools are critical components to different aspects of the DevOps infinity lifecycle that, when optimized, enable software development and IT operations teams to increase their output of reliable, secure software releases, and ultimately, keep corporate initiatives in motion.

The marketing agency’s team needed assistance from a professional services team to help them with the migration so Dev and IT teams, as well as the organization at large, could continue achieving milestones without interruption from the company-wide transition. Contegix, equipped with expert knowledge of Atlassian products and how to effectively migrate them, was uniquely positioned to execute the task, having hosted the agency on Amazon Web Services (AWS) since July 9th 2020.

Atlassian expert and Contegix engineer Joshua Sneed led the agency through the migration process with innovative cloning and compressing solutions to ensure functionality remained after the apps and their data were moved to AWS. With help from Contegix, the agency successfully adopted the acquired company’s Atlassian applications.

Overcoming Data Restrictions with Cloning Solutions

To kickstart the migration process, Sneed and his team of engineers needed to access the data from each application so they could transition from their existing environments to AWS. The apps that the Contegix team needed to move were Jira, Confluence, Bitbucket and Bamboo. This included the database (Postgres) and all related files. The catch? Due to the customer’s company policy, Contegix engineers couldn’t access the production instance.

“We worked around this obstacle by cloning,” explains Sneed. “All four applications were cloned over to sandbox instances. This way, our team could securely perform changes to the applications without touching the customer’s production.”

But when it came time to actually migrate each application’s data to AWS, massive file sizes threatened to stop the process in its tracks. The Bamboo instance in particular was thought to be the largest Bamboo instance in the entire Atlassian ecosystem, too large to transfer at all.

Compressing Massive Files Sizes to Drive Mobility

The team needed to reduce the application sizes to generate movement, but another challenge presented itself: the agency’s team didn’t have Atlassian admin permissions after the apps were cloned. Sneed edited the database to grant the the customer personal admin access, where they formulated scripts to run against Bitbucket and Bamboo to greatly reduce their size––reasonable enough for them both to move.

Although the cloning and compression processes were time-consuming, the pressure was on to work swiftly. If the apps weren’t successfully migrated by the end of July, the agency would have incurred hundreds of thousands of dollars in relicensing fees. Each application took a few hours to clone, reducing the size of the Bamboo instance took about twelve hours, plus an added three hours to export, then another six hours of import time—all just to move the data.

After a collaborative effort between Sneed and the agency’s team, the Bamboo instance was reduced by 80% and the database became much more manageable to migrate.

“The original estimated synchronization set was five days, or around 44 and a half total hours. We got it down to 14 hours for the production run for Bamboo,” Sneed says.    

Ensuring Functionality, Making Deadlines and Saving Dollars

Any successful migration hinges on each app functioning properly once all is said and done. Due to the nature of the application, data stored in Bamboo is constantly changing as teams use it, which triggers changes across a number of areas in the file system. So when users stopped using the app for the migration, it was critical Sneed’s team completed the data transfer before teams logged back in.

“After the migration is complete, and as soon as you turn on the applications, each tool is going to try and connect all the things it thinks it should connect to. We did have to make sure that quite a few pieces of the app were functioning as expected, with new values or new routes of communication, so that when users were granted access again to the applications that all the expected functionality remained, even though various parts of the applications had changed,” explains Sneed. “That's how we ensure that the continuous infinity loop of the development cycle continues on.”

Now, the agency’s newly acquired division is completely hosted on AWS, the most compatible database that most teams utilize for Atlassian products, which helps to improve the longevity of the instance overall. Sneed’s team executed a timely, completely synchronized migration, which allowed users to pick back up right where they left off and avoided additional costs for the agency.

Learn more about how Contegix can support your team during an Atlassian migration.