Key Migration Steps

Get Access to the Migration Assistant App

The first step is to obtain access to the Jira Cloud Migration Assistant App from the Atlassian Marketplace.

Do the following necessary steps before starting the migration:

1. Upgrade to the latest version of Jira. See Tempo version compatibility.

2. Install the highest Tempo version compatible with the installed Jira version. See Tempo latest versions.

Audit and Assess Your Server Apps

Atlassian recommends auditing your Server apps, including Tempo, and assessing your Server apps before using Jira Cloud Migration Assistant tool.

Install and Configure Tempo on Your Cloud Site

It is strongly recommended to install and to configure Tempo on your Cloud site before you attempt the migration. It's a necessary step to eliminate any possible risks that can be caused by your apps blocking your migration during the crucial migration steps.

Connect Your Instance and Run the Migration App

Atlassian has a comprehensive documentation set about the steps you should follow once your access to the Cloud Migration Assistant app is enabled. Generally speaking, you are required to follow these key steps:

• Connect to your destination Jira Cloud site

• Choose your migration options:

  1. Make sure that you select the Projects and the Tempo Apps they are associated with in order to be migrated together; otherwise, data will not be migrated correctly.

  2. We recommend that you select the option to migrate all projects as well as all users and groups from the Jira directory.

     

• Check for errors before you either save or run the migration

Monitor Your Migration Progress

Once you've initiated the migration, you can use Jira's Migration dashboard to monitor its progress. The dashboard indicates whether your migration projects are Saved, Running, Finished, Incomplete, or Failed.

Select View details to see detailed information about the progress of your migration project while it is running, from the migration dashboard and navigate to the logs and Reports tab. A progress report screen also shows the details of processing the migration.

Update the Worklogs with Missing Parameters

The DYNAMIC_DROPDOWN field type is not supported on the Cloud. The missing attributes from the DYNAMIC_DROPDOWN field type for worklogs must be updated in your Cloud instance. For example, billed hours or worklog attributes. Here are a few things to keep in mind when doing so:

• The worklog attributes from the DYNAMIC_DROPDOWN field type must be converted to a static list field type (STATIC_LIST) values. The DYNAMIC_DROPDOWN type is not supported on Jira Cloud.

• 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 ACCOUNT type (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 it cannot be edited afterwards.

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

Verify that Data Migrated as Intended

Once your migration is complete it is critical that you confirm that everything is migrated as intended. It is especially important that you confirm the migration of the Tempo data.

A key way to confirm that your worklogs are migrated is to go to Tempo's Logged Time Report:

• If you have the proper permissions, then you should be able to see all worklogs there.

• If you have the right permissions but you don't see your Tempo worklogs, then they may not be sync'ed yet from Jira to Tempo. Contact Tempo support team for Assistance.

• If you have Work attributes that are configured, then verify that the migration is completed and worklogs are in place, then contact support to execute the migration of Work attributes.

Depending on the size of your organization, you may need to supplement your in-person verification of the remaining data with scripting, so you can verify the data at a larger scale.

If you are missing data during migration, then consult the Migration Steps. This can happen if you are using older versions of the software where some data might not migrate properly. You must contact Tempo support team for assistance.

Feedback and Support

One of the key goals is to get feedback on how the Migration Assistant App is working for you, particularly with regard to your Tempo data. Please contact Tempo support team with your comments and questions, and they will do their best to help you.