Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Tempo is working closely with Atlassian on a Jira Cloud Migration Assistant app that will streamline the migration process. The migration assistant app is in Atlassian's early access program and is expected to be released to all customers sometime in 2021.

In the meantime, we have created a migration guide that outlines the manual steps you need to take to migrate Tempo data. Tempo data can be migrated using a combination of the Jira Cloud migration app, Tempo REST APIs and manual configuration and migration of data through the UI. There is no “one size fits all” approach at this point, so you should examine the options to determine which is the best fit for your organization.

The easiest and recommended first step is to use the Jira Cloud Migration Assistant app. The app handles a lot of issues in the background that will make the rest of the migration steps less painful by retaining the database identifications from the Jira Server instance. The Jira Cloud Migration Assistant app is now offered through Atlassian's early access program, and customers enrolled in that program can benefit from the automated migration process.

The remaining data can be migrated by using Tempo REST APIs or entering the data manually through the UI. Leveraging the APIs will allow you to complete the migration in one shot, giving you a significant advantage compared to manual data entry. It will likely be the preferred method if your final migration is happening on a specific date, as it will allow you to minimize the downtime of your production environment.

For some of you, however, manual data entry may be the right approach, particularly when it comes to Tempo configurations, team permissions, and workload and holiday schemes. This will allow you to avoid the start-up costs of working with the REST APIs. However, it will likely mean that you will need to do data entry twice - once for your Cloud test environment and another time for your Cloud production environment.

Not yet sure which is the right approach for you? Read on to learn more about the steps you need to take to migrate, and let us help you decide which is the right path to take.

Watch this short video to get an overview of your help options:

Looking for migration information for our sister company, Timesheet Reports and Gadgets? You can find it here.

In this section

  • No labels