Simplifying Issue Migration between Jira Cloud Instances: Atlassian’s Journey with Deep Clone for Jira.

In the area of IT Service Management (ITSM), efficient project and issue management is key. Atlassian faced a common yet complex challenge with their own Jira Cloud instances and Jira Service Desk projects. Due to historical reasons, they were operating multiple service desk projects across different Jira instances, and it was time to streamline their processes and make their partners and internal teams happier. This is where our Atlassian Marketplace App, Deep Clone for Jira, played a crucial role.

Initial Situation: Multiple JSM projects on different Jira Cloud Instances

Atlassian managed multiple Jira Service Management projects across two Jira Cloud instances. In response to feedback from partners and internal sources, they aimed to simplify their setup by consolidating the two Jira Cloud instances with multiple Jira projects, into one instance with a unified project. Achieving this required migrating Jira issues while retaining all relevant information to ensure continuous support for customers and partners.

Did you know that Deep Clone is used for 2.5% of all created issues within Jira Cloud?

The Challenge of Jira Cloud-to-Cloud Migration

Atlassian’s migration challenge was distinct in that it entailed a transition from one Jira Cloud instance to another. While they explored different solutions, they faced substantial obstacles arising from technical limitations and timing challenges. These challenges were caused by the following factors:

  • Move issues from one Jira Cloud project type to another
  • Migrate issues from one Jira Cloud instance to another
  • Copy essential Marketplace (or third party) app data (stored in issue properties)

A Swift Consolidation of Jira Cloud Instances and Projects in Three Months

Within just three months, Atlassian was able to consolidate their Service Management projects, with the help of Deep Clone for Jira, where the actual migration only took less than one day. The initial estimates without Deep Clone suggested a three-quarter timeline, with a migration period which would have taken several weeks, due to the necessity of retrospectively inputting the missing issue data. As you can imagine, a migration without Deep Clone would have been not only more expensive, but also more complex, and heavily disruptive for the daily business. 

Moreover, the migration was a success on the first try, without any rollbacks needed.The flawless migration, is a very positive feedback for us, that we’re on the right track in case of the app’s user-friendly nature, even with complicated tasks like migrations.

Sean Yong - Atlassian

“Deep Clone did 80 percent of the heavy lifting during the migration. The entire process was completed over the weekend without any rollbacks. It worked on the first try.”

Sean Yong, Marketplace Systems Architect at Atlassian

Evaluation, Set Up, and Migration: Migrate JSM Tickets to another Jira Cloud Instance and Project

The journey to migration involved several phases:

  • Evaluation: This phase was crucial for comprehending the nuances of issue data that required cloning and verifying if Deep Clone for Jira could facilitate the migration. Atlassian also assessed whether our app met their reliability and security requirements, which it did. 
  • Setup:  After opting for Deep Clone for Jira, the next phase involved configuring Jira Service Desk projects, including essential settings like workflows, issue types, and fields. This critical step was essential for ensuring a seamless migration, as Deep Clone requires precise matching of fields names, even down to capitalization, to ensure a successful migration. 
  • Migration: Cloning and merging the Service Management projects and instances was completed in less than a day. 

Deep Clone for Jira stands out for its user-friendly nature, making it accessible to any Jira user. Even when dealing with extensive Bulk Cloning that might require additional time, it can operate in the background, and users receive a notification upon the migration’s completion. This notification includes a comprehensive log that provides insights into any potential errors, facilitating analysis. Furthermore, the cloning log is accessible throughout the process, enabling users to monitor progress in real-time.

Discover essential considerations for a successful issue migration using Deep Clone for Jira.

Deep Clone for Jira: Clone History

Conclusion

In conclusion, Atlassian’s migration journey, powered by “Deep Clone for Jira,” exemplifies the efficiency and reliability of the app. Atlassian was able to save around 6 months of work, thanks to Deep Clone for Jira. The challenges they overcame, along with the time and cost savings, showcase the value of choosing the right tool for a complex migration project. If you’re considering streamlining your Jira Cloud instances and projects, Deep Clone for Jira may well be the solution you’ve been looking for.

Share your Deep Clone for Jira success story with us! We’re eager to hear your feedback.

Evaluate Deep Clone for Jira with a 30-day free trial to see if it meets your needs.

Cookie Consent with Real Cookie Banner