Nadica Gaber, Senior Application Operations Engineer and Nenad Micic, Technical Support Specialist @ Seavus, share their expertise in Asset Management and Cloud Migration using Atlassian tools.
Learn from Seavus, Atlassian Platinum Solutions Partner, about the possibilities and challenges of Cloud Migration automation and Asset Management though real-life examples in the interview below.
Join us on November 22nd in Stockholm and November 24th in Malmoe if you are faced with other challenges related to the Atlassian ecosystem, feel free to bring them up in the discussion. Our experts are eager to understand your difficulties and offer applicable solutions.
What are some of the main reasons companies migrate to the cloud?
Nadica: The main reason is, of course, the discontinued Atlassian Server Licenses. However, there are clients that had migrated to cloud even before this decision. Their main motive was the convenience of not having to handle the infrastructure, upgrades and maintenance. When on the cloud, companies only need to take care of the settings on application level.
What are the steps involved in planning a cloud migration project?
Nenad: Deciding clearly on what needs to be migrated to the cloud is the first and most important step to take. After this has been determined, you need to investigate projects that are part of the scope so you can check for the details that are not migrated with the tool and start preparing and writing down everything that needs to be done manually. This includes checking workflow customization, inactive groups, backup of attachments and avatars, and the compatibility of add-ons and their possibilities in cloud version. Then the first test migration can be done in a separate test environment. This process is repeated until you get it right. In order to prepare properly for production migration, you need to document everything in a workbook with time estimation for every step.
Do you think it’s possible to automate all cloud migrations? If yes, what would your approach be?
Nadica and Nenad: With the current state of the add-ons for server and cloud, to automate the add-on data is possible only for some add-ons and to some extent. As for the main application data itself, it has already been automated with the migration assistants, tools that Atlassian is providing for partners and customers to migrate the application data. Both Atlassian and the vendors are actively working on facilitating the migration of add-on data as well, so I believe in the future we will be able to automatically migrate the plugins data as well, at least for the bigger part of them.
What are some common issues that occur during cloud migration?
Nadica and Nenad: The most important step for cloud migrations is the preparation. So, trying to speed up the migration without checking all legal requirements in the company, not communicating with the end-users about the migration in a timely manner, not taking into consideration that some integration is in place or not having a clear user migration path are the most common ways that cause issues during and after the migration.