ShareShare on LinkedIn.Share on Facebook.Share on Twitter.Share via email.

Jira and Tempo Cloud Migration

September 5, 2020
<p>Once we decided to migrate from Jira Server to Jira Cloud, our migration planning began. Which method should we use to migrate? How will we train and transition our users? What about our plug-ins, are there cloud compatible versions and are they different in feature sets from the server version?</p> <p>At Highway Three Solutions, we decided to use the Jira Cloud Migration Assistant (JCMA) rather than a full site import. It provided the ability to migrate project by project, which means you can have a soft launch of your cloud site and can migrate users in batches.</p> <p>One of the features included in the JCMA is the ability to assess application compatibility between the Server and Cloud instances.</p> <div class="wp-block-image is-style-h3-screenshot"><figure class="aligncenter size-large"><img loading="lazy" decoding="async" width="642" height="283" src="" alt="" class="wp-image-271" srcset=" 642w, 300w" sizes="(max-width: 642px) 100vw, 642px"></figure></div> <p>Tempo Timesheets, an app created by Tempo for Jira, is commonly used to extend the basic Jira worklog management features in order to manage time tracking, planning, budgets, customers and accounts. In Jira Server, the Tempo data is stored alongside Jira in the server database, but in Jira Cloud, plug-in data is stored in a vendor-specific storage. This architectural difference makes the migration to the cloud a little more complicated. Tempo supports a Jira full site import via a combination of automatic migration and manual steps, but at this time, they do not support the migration of Tempo data using the Jira Cloud Migration Assistant.</p> <p>In our environment we had years worth of data we needed – thousands of worklogs covering about 60 projects. Recreating the content manually was not an option. We needed a solution that would:</p> <ul><li>Support migration using the Jira Cloud Migration Assistant (project by project migration)</li><li>Perform “delta” updates of Tempo worklogs so that we can test the migration multiple times</li></ul> <p>The technical difficulty with migrating Tempo using the Jira Cloud Migration Assistant is that Jira user and worklog IDs are regenerated on migration. Worklog data can not be migrated automatically because of this. Luckily, both Jira and Tempo provide REST APIs that can support the migration with a little bit of coding.</p> <p>Our approach to the Tempo migration utility allowed for dual production environments, with users actively using both environments until the migration was complete.</p> <div class="wp-block-image h3-screenshot"><figure class="aligncenter size-large"><img loading="lazy" decoding="async" width="624" height="291" src="" alt="" class="wp-image-272" srcset=" 624w, 300w" sizes="(max-width: 624px) 100vw, 624px"></figure></div> <p>We created a utility that would query the Jira Server REST API for Tempo data, and then use the Tempo Cloud REST API to push the data into the cloud environment while matching to the Jira Cloud user and worklog IDs.</p> <div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" decoding="async" width="645" height="649" src="" alt="" class="wp-image-273" srcset=" 645w, 298w, 150w" sizes="(max-width: 645px) 100vw, 645px"></figure></div> <p>We split our utility to separately migrate the different categories of Tempo data:</p> <ul><li>Worklogs &amp; worklog attributes</li><li>Accounts</li><li>Categories</li><li>Customers</li><li>Programs</li><li>Roles</li><li>Teams</li><li>Timesheets</li></ul> <p>This approach allows us to continue to use the server environment by providing the ability to run delta migrations to keep the cloud environment up to date (or to have both environments live) while remaining server projects are migrated.</p> <p>Limitations of the Utility:</p> <ul><li>Timesheet approval, rejection, or submission dates are not retained</li><li>Accounts still need to be manually migrated (although the utility automatically updates the output file to match the required format)</li></ul> <p>Good planning and testing of your migration will ensure a successful move to Jira cloud.</p> <p>The Jira Cloud Migration Assistant app is a great tool to move Jira Server data to a Jira Cloud instance. With version 1.0.0 released on March 9, 2020, it is still a rather new application. Tempo Timesheets is able to migrate worklogs with a full site import, and with time it may do the same with the new migration tool. For now, we can migrate Tempo data through our utility using the Jira and Tempo REST APIs.</p> <h2 class="wp-block-heading"><strong>References</strong></h2> <ul><li><a class="h3-inline-link" href=""></a></li><li><a class="h3-inline-link" href=""></a></li><li>Tempo Rest API version 3: <a class="h3-inline-link" href=""></a></li><li>Tempo Server API documentation: <a class="h3-inline-link" href=""></a></li><li>Jira Rest API: <a class="h3-inline-link" href=";utm_medium=302#about">;utm_medium=302#about</a></li></ul>