Tempo for Jira Cloud

Migration Steps for Tempo Timesheets

Abstract

Steps you need to take to migrate from Tempo Server to Tempo Cloud

Note

Tempo data setups are different for every instance. Depending on your dataset, you may need to take all of the steps described below or only a selection of them.

Please note that you need to migrate JIRA data before starting to configure Tempo and / or migrating Tempo data that is not worklog data.

Warning

When you migrate from Jira Server to Jira Cloud with an XML backup from Jira all worklogs will be migrated to Jira and synced to Tempo. DO NOT attempt to import the Jira Server worklogs to the Jira Cloud instance in those cases.

Key Steps for a Successful Tempo Timesheets Migration
  1. Export worklog data from the source destination with the Tempo worklog servlet or by using the Jira Cloud Migration Assistant.

    Exporting worklogs is only needed in cases where you have worklog attributes configured or if you have not migrated the worklogs to Jira Cloud with the Jira backup/restore functionality.

  2. Export the Tempo Account data in .csv format.

  3. 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).

    Note

    Please note that the Team role Jira custom field is not supported / available on Tempo for Jira Cloud.

  4. Configure Tempo in your new Cloud instance (Jira permissions, Tempo configurations).

  5. Set up Tempo teams in your new Cloud instance and configure team permissions. There are no native export options (.csv or .xls) for Tempo teams from Tempo for Jira Server. To import/export the Tempo teams between your instances you will need to invest an amount of time that you need to evaluate if it is worth the effort compared to a manual entry of the teams in your Jira cloud instance. Moving to a new instance might be a good point to review your team setup within Tempo so that you only merge those teams that are needed. Creating and updating team permissions is not available from an REST endpoint. By default the endpoint creates two permission roles. One associated for the team lead and another one for team members. The permission role for the team lead implies all permissions (view / manage worklogs and plans and the ability to manage the team) and the role for the team members implies no additional permissions (means each team member can only see their own plans / worklogs).

  6. Set up and configure the Tempo workload and holiday schemes in your new Cloud instance. There are no native export options (.csv or .xls) for workload and holiday schemes. To import / export the Holiday / Workload schemes between your instances you will need to invest an amount of time that you need to evaluate if it is worth the effort compared to a manual entry of the workload / holiday schemes in your Jira cloud instance. After you have configured your workload / holiday scheme you will need to assign your users (Atlassian Account IDs) to these schemes.

  7. Import the Tempo Accounts .csv file. Before you import the Accounts into Tempo you need to match the current userkey from Jira Server to the new Atlassian Account ID.

  8. Update the worklogs in your new Cloud instance with missing parameters (billed hours, worklog attributes) or import all worklogs from scratch (when you have decided to move all existing worklogs). There are a few things to keep in mind when doing so:

    • Worklog attributes from the type DYNAMIC_DROPDOWN are not supported on Jira Cloud and need to be converted to a static list (type STATIC_LIST) values.

    • The values from the worklog attributes for each worklog are exported with the worklog servlet and the REST API as plain text / numeric values. However when you have worklog attributes from the type ACCOUNT (Tempo Account field) the returned value is the Account Key in the Tempo database. The Account key can be set during the Account setup process but is not editable afterwards.

    • If you have a worklog attributes of the type DYNAMIC_DROPDOWN the returned value is the key. If the key is different then the provided name from the UI you will need to match the key to the name.

  9. Update the Tempo Account and Team Custom fields for the Jira issues in your new Cloud instance. This can be done using the Jira Cloud REST API.

Warning

Tempo Timesheets v.8 (and Tempo Planner v.5) have a different Team structure than newer releases. This means you will need to adapt to the current Team permission structure if you are running one of those versions.