Hi @Hemal Vyas
Data migration is a complex proposition and needs careful planning for its smooth and successful execution. For general pointers, you can look at the blogs, A Guide to Application Data Migration and The Agile Approach to Data Migration. In addition, the following points should be considered before undertaking the ADO to Jira migration:
1) Format Retention: Azure DevOps (ADO) and Jira use different rich text formatting standards which are similar but not equivalent. ADO uses HTML text formatting while Jira uses Wiki markup text formatting. As part of the evaluation phase, you will have to validate such format transformation strategies [i.e., how to convert HTML format to the wiki for the data being migrated]
2) Two-step Sprint Migration: Jira does not let you schedule an issue in closed Sprint. If Sprints are being migrated, those need to be migrated with Open State until all other issue types are migrated. Finally, Sprint’s status needs to be migrated from ADO to Jira.
3) Adaptation to the New Environment: ADO allows for creating a work item hierarchy that is only available for Portfolio items in Jira, specifically for Epic and Deliverable. Understand the model/structural differences and plan out how teams are going to adapt to the new Agile environment.
4) Preservation of Institutional Knowledge: Opt for a solution that migrates the data with history to preserve historical knowledge.
5) Non-disruptive Migration: Depending upon the approach chosen, migration can cause massive disruptions to the operations. Often the cost of disruption can dominate all other explicit and hidden costs. So, factor in the disruption costs in your planning and bias towards solutions that minimize disruption to all aspects of current operations.
6) Impact on ADO and Jira: Jira on-premises would slow down on frequent API calls to add or update data whereas ADO’s user-wise API rate limit can cause frequent hurdles in migrating data from ADO to Jira.
Any migration solution must be able to address these challenges.
7) The following Approaches can be used for migration data from ADO to Jira:
OpsHub, an Atlassian partner, has rich experience in undertaking complex migration projects and can help you ease your agile migration journey. We are happy to help in your migration planning process. Please reach out to us for an initial free consultation on migration planning with our solutions architects.
Thanks
Hi @Hemal Vyas
Data migration is a complex proposition and needs careful planning for its smooth and successful execution. For general pointers, you can look at the blogs, A Guide to Application Data Migration and The Agile Approach to Data Migration. In addition, the following points should be considered before undertaking the ADO to Jira migration:
1) Format Retention: Azure DevOps (ADO) and Jira use different rich text formatting standards which are similar but not equivalent. ADO uses HTML text formatting while Jira uses Wiki markup text formatting. As part of the evaluation phase, you will have to validate such format transformation strategies [i.e., how to convert HTML format to the wiki for the data being migrated]
2) Two-step Sprint Migration: Jira does not let you schedule an issue in closed Sprint. If Sprints are being migrated, those need to be migrated with Open State until all other issue types are migrated. Finally, Sprint’s status needs to be migrated from ADO to Jira.
3) Adaptation to the New Environment: ADO allows for creating a work item hierarchy that is only available for Portfolio items in Jira, specifically for Epic and Deliverable. Understand the model/structural differences and plan out how teams are going to adapt to the new Agile environment.
4) Preservation of Institutional Knowledge: Opt for a solution that migrates the data with history to preserve historical knowledge.
5) Non-disruptive Migration: Depending upon the approach chosen, migration can cause massive disruptions to the operations. Often the cost of disruption can dominate all other explicit and hidden costs. So, factor in the disruption costs in your planning and bias towards solutions that minimize disruption to all aspects of current operations.
6) Impact on ADO and Jira: Jira on-premises would slow down on frequent API calls to add or update data whereas ADO’s user wise API rate limit can cause frequent hurdles in migrating data from ADO to Jira.
Any migration solution must be able to address these challenges.
7) The following Approaches can be used for migration data from ADO to Jira:
OpsHub, an Atlassian partner, has rich experience in undertaking complex migration projects and can help you ease your agile migration journey. We are happy to help in your migration planning process. Please reach out to us for an initial free consultation on migration planning with our solutions architects.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.