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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Since some time has passed and now surely a few have migrated to the cloud, I would like to know if there were any problems or difficulties after the migration.
Yes sort of a “Pitfalls to be wary of”.
If you do the migration correctly then there are not really any problems after the migration. I would say that the biggest difficulty is the different subtleties between server / DC and cloud. Some users are thrown off by this and get frustrated or complain. As you prepare to migrate just do not forget to prepare your users for the differences that they will experience. I believe that this is the biggest issue that most face if they follow standard migration best practices.
Nice question! I would like to hear opinions about the post-migration period!
Nice Question !! I would like to hear opinions about after Migration. What are the challenges and how to fixed them?
CCMA is a gift from the gods. There is just so much to consider.
But I have really appreciated the tools that Atlassian provide and the information from the Community.
Has anyone had issues with attachments not being migrated, but no errors being flagged?
We are currently in migration testing (Server to Cloud) so I cannot really answer your question about the experience from the other side. But I thought I'd add some observations.
The recommended health checks and clean-up on your instance are technical (e.g. running SQL queries). If you're not confident doing that you might need to consider finding a migration partner.
The last time I checked Atlassian's documentation the PRE-migration checklist has 18 steps:
Have a read before you get started.
Why don't Atlassian automate more of this for you?
If you run a vanilla Jira server with few apps and not much customization, the Jira Cloud Migration Assistant (JCMA) could make the process relatively easy.
This was not true for us. We have a good number of 3rd party apps - some support migration, and some do not. We can work-around some of these so the impact should be minimal.
We found that our workflows include validation that cannot be migrated by JCMA. We're still working to clean-up workflows so they will migrate. , with a number of support requests to Atlassian and App developers.
If you do not require ongoing security fixes, AND you don't want to purchase more Atlassian products I would not recommend migrating to Cloud. The migration effort so far would easily amount to a few years worth of server admin/maintenance.
As noted above we're still testing. But I know that some aspects of our Server Instance cannot be replicated in Cloud. At present my main concerns are:
As a side-note the cost of apps on Cloud is substantially higher than on Server at our user tier. You should check pricing for your apps, and factor that into your budget.