Migration Steps for Tempo Planner

These migration steps can be done automatically using the JCMA migration assistant tool. Tempo recommends using the automated migration assistant tool to facilitate the migration of Tempo Server and Data Center to Tempo Cloud.

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.

Key Steps for a Successful Tempo Planner Migration

1. Export plan data from the source destination with the Tempo Planner REST API. Preferably use the endpoint (POST)

   CODE

   /rest/tempo-planning/1/plan/search

   with a payload like

   CODE

   {"from": "2019-01-01","to": "2021-12-31"} 

   The export will include all necessary fields that you need to import into your Cloud instance via the REST API (Issuekey, startdate, enddate, plannedperseconds and the user that needs to be mapped to the Atlassian Account ID).

2. Export a Jira issue list that includes the Jira issue key and the Tempo Team custom field value (if set in your source instance).

3. Configure Tempo in your new Cloud instance (Jira permissions, Tempo configurations). For more details, see step #4 in the migration steps for Tempo Timesheets.

4. Set up Tempo teams in your new Cloud instance and configure team permissions. Please see #5 of the migration steps for Tempo Timesheets for more details. There are no native export options (.csv or .xls) for Tempo teams from Tempo for Jira Server or Data Center. 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).

5. 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 and/or workload schemes between your instances you will need to invest a significant amount of time. You should evaluate whether 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 schemes you will need to assign your users (Atlassian Account IDs) to these schemes.

6. Import the plans in your new Cloud instance with the Cloud REST API. As the endpoint / plans only excerpts the Atlassian account ID, you will need to map the userkey exported from your Server or Data Center instance in step#1 to the Atlassian Account ID.

7. Update the Team custom fields for the Jira issues in your new Cloud instance.

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.