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.
Would this be a good forum to use for cloud migration questions?
Joining the community group to obtain our recommendation + for consultant assistance it depends on the complexity of your migration process (i.e. your existing DC/Server env content etc..)
This board is not the best place to ask questions. I would second @Karen Rogalski 's recommendation to check out the Migration Program group. You could also post questions in the product-specific forums
Here is a good place to start regarding finding helpful documentation:
It is great to know that community leaders are thinking alike in regards to the ask from the community members.
Welcome to the community, here is a link containing a lot of information on migration -
Here is the group that you should join and participate -
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Being one of the "consultants" in question, representing TechTime – a Gold Solution Partner in New Zealand and Australia, I suggest you at least investigate offloading migration onto one of the local Partners in Partners Directory. Asking around for availability and some estimates won't hurt. Some, like us, may offer this as a fixed-cost project.
See this post to glean possible complexities a Partner will deal with in stride:
Having said this, if a Partner can do it, so can you, yourself. This is merely a question of time vs. money.
Thank you for the information. This is very helpful.
There are dozens of tools in the market that can migrate data from Jira Server to Cloud. But migration projects are typically complex and require careful planning and strategy. You must first define the must-haves (e.g., comment synchronization, inline images sync, etc.) you expect from migration and then evaluate the different migrators available:
You can consider the following criteria while evaluating a third-party migration tool:
1) Downtime: Downtime adds operational costs and impacts development operations as teams may not be able to use Jira during ongoing migration. As part of the evaluation, validate that no downtime is involved that can cause business disruption.
2) Project key restrictions: Jira Server allows underscore (_) and few other characters in the project key, whereas on-cloud allows only letters in the project key. Any migration needs to factor in strategy to address these differences.
3) Field template inconsistency: Analyze if there are any field scheme configuration differences between your Jira Server and the On-Cloud instance. Make sure you have a strategy for bridging those differences if needed.
4) Skills required: Some tools are a collection of unsupported beta versions of scripts, requiring a very high degree of sophistication + consultants. These can be highly time-consuming, error-prone, and can hinder operations. As part of the evaluation, analyze what part of the migration may require script and involvement from your side.
OpsHub has an extensive experience in undertaking complex migration projects, ensuring zero downtime, no data loss, complete data integrity and full ownership of the migration process. OpsHub Migration Manager can be a suitable choice for your use case as it supports the migration of all System & Custom Issue Types, Sub-Task Types, Worklogs, Versions, etc., from Jira Server to Jira Cloud.
Please reach out to OpsHub’s Migration Experts, for an initial discussion on migration planning.