You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
First start anything, we need have clear ideas and we have to plan any step before. If we wanna migrate to a cloud instance, as I wrote in a blog post, Use your head.
Before execute a migration from server/on premise to cloud instance, think about features you use on Atlassian Tool in your environment.
Make a list of functionalities and classify them, so you can understand if are:
For this second point, check all addons/apps installed and check which is used. In my experience, I always migrate instances with a tons of addons but only 2-3 were really used :-)
For each addon/app check if exists in cloud environment
If addon doesn't exists in cloud, well, this is the workaround :
In MrAddon blog, I've described how create calculated fields both in Server/on premise and cloud environments.
So we have possible solution if we have to migrate a server instance with calculated fields.
This is the first step of a big process. So: