As COO of Isos Technology, I am heavily involved in Isos IT operations, and I regularly meet as a client of our Managed Services team for our Atlassian Server tools. After many discussions and getting clear direction from Atlassian that the future is Cloud, we have decided that the time has come to migrate from all our server applications to Atlassian Cloud.
We have always adhered to the philosophy that our Atlassian toolset should be set up to represent our recommended use to clients. We have hosted and used the Atlassian Server versions of the applications until now, as that was the gold standard platform. Over the last few years, and even more so in the last few months, it has been made explicitly clear that the Atlassian Cloud versions of the applications are the new gold standard. We must therefore migrate to Cloud as we want to experience what our clients will experience on a day-to-day basis.
I am super excited about some of the benefits we gain by transitioning to Atlassian Cloud including:
Reduction of Effort for Our Internal Support Team
Here are just a few examples of how a move to Cloud will benefit our support team:
- We no longer have to worry about testing and applying application upgrades across the suite ourselves.
- We will use the new Sandbox functionality to replace using our own dev servers to test rolling out new apps and updates.
- We'll have no more sysadmin-related duties, which include digging into applications logs, scheduling application restarts, OS upgrades, etc.
Security is Handled by Cloud
From an IT perspective, we no longer have to second guess the handling of security for the infrastructure. Now, all I have to do is visit the Atlassian Trust Center to see all security, reliability, compliance, and privacy practices.
Cloud Provides Cost-Effective Hosting
We no longer need to pay our own separate hosting costs. Now that we can rely on Atlassian to host our Cloud-based tools, we can take the money we save and invest it in other areas in our company, like innovation, research and development, etc.
Of course, migrating to Cloud is not all benefit without paying some costs upfront. Given the number of years we've been on Server and all the various dependencies we have in the way we work, it's going to be a sizable effort for us to migrate.
So, how will we start this process? By becoming our own customer! We will engage our business development team to measure the effort and estimate the hours and timeline of the migration. The project will then be handed off to our project delivery department, which will assign a functional lead to head a team consisting of a solutions architect, engineers, and additional subject matter experts. They will begin the process of working through the plan and executing the migration to completion. However, given our dependency on the Atlassian toolset and all the parts of the company it touches, I see us involving a large number of our employees in user acceptance testing to make sure we haven't dropped any functional use of the applications in the transition to Cloud. We'll have our work cut out for us!
I am looking forward to an exciting journey as we undertake our migration. In the coming months, I expect to write additional blog posts to share stories of our victories and setbacks as we begin the transition that many of our clients have already started to undertake. I can't wait!