To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.
Migrating Tempo data between Jira hosting environments
When you decide to move your Jira instance to another hosting environment (Data Center to Cloud) you might want to ship your existing Tempo installation and Tempo data to the new hosting platform alongside with your Jira instance.
The most common way to migrate data between hosting environments is by using a Jira xml back and restore that backup in your Cloud or Data Center instance. As all 3rd party application data (like Tempo) is not stored in the same infrastructure as Jira you will need to migrate the Tempo data by yourself. However the worklog data is reserved in the Jira xml backup but with no additional Tempo data (billed hours and worklog attribute data).
When you migrate from Cloud to Data Center you will see that all worklogs belong to an anonymous user “Tempo Timesheets”. As you can´t update the worklog author from a worklog you will need to erase all worklog data from Jira and repopulate the worklog dataset using the Tempo REST API.
Below you can find some general guidelines that you should have in mind when migrating the Tempo data. Bulk import/export of Tempo data can be achieved with the usage of the Tempo REST APIs if available. An exception are Tempo Accounts that offer a possibility to export/import accounts with a csv file.
Dynamic dropdown fields are not supported in Tempo for Jira Cloud.
Workflow
Recommended migration steps
Export worklog data from the source destination with the Tempo REST APIs (Cloud) or the worklog servlet (Data Center)
Export the Tempo Account data
Export a Jira issue list that includes the Jira issue key, the Tempo Account and Tempo Team custom field value (if set in your source instance)
Configure Tempo into your destination instance (Jira permissions, Tempo configurations)
Setup the Tempo teams into your destination instance and configure the team permissions
Import the Tempo Accounts
Update the worklogs in your destination instance with missing parameters (billed hours, worklog attributes) or import all worklogs from scratch (when you have decided all existing worklogs)
Update the Tempo Account and Team custom field on the Jira issues in the destination instance
Timesheet approvals are not covered in this article. But if you decide the timesheet approvals as well you will need to export the timesheet approval status from the REST API and recreate them in the destination instance. For Timesheet approvals it is recommended to migrate only the latest status. The timesheet approval history would show not the right picture as the timestamp will not match to the source instance.
Related articles
https://tempo-io.atlassian.net/wiki/spaces/KB/pages/780042241
https://tempo-io.atlassian.net/wiki/spaces/KB/pages/1400471783
https://tempo-io.atlassian.net/wiki/spaces/KB/pages/488931333