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.

Set Debug Level Logging

Enable the debug level logging option on your Data Center instances so that any issues that might be encountered during migration can be traced back for better troubleshooting purposes. To do so:

1. Click the Cogwheel for Settings and select System.

2. Click Logging and profiling in the side panel.

3. Scroll down the page to Default Loggers.

   

   
   

4. Click the Configure logging level for another package.

   

   
   

5. In the Configure logging level for another package window, do the following:

   1. Enter the com.atlassian.Jira.migration.appPackage name and set the Logging Level to DEBUG.

   2. Enter the com.tempoplugin.core.migrationPackage name and set the Logging level to DEBUG.

6. Click Add after each addition.

This enables debugging and logging that can provide the support team with troubleshooting clues in case problems are encountered during the migration process. A Support.zip file is needed.

Audit and Assess Your On-prem Apps

Atlassian recommends auditing your On-prem apps, including Tempo, and assessing your on-prem apps before using Jira Cloud Migration Assistant tool.

Install and Configure Tempo on Your Cloud Site

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

When configuring your Cloud instance, be sure to set up your global Tempo settings just as they are configured for your DC instance, such as the first day of the week, global time zone, workload/holiday schemes, etc., to avoid issues after your migration.

Match Time Zones

Jira Cloud Migration Assistant (JCMA) migrates worklogs with their timestamps, and Tempo then syncs them from Jira. If the Jira time zone differs between your Data Center and Cloud instances during the migration, worklogs can shift forward or back by hours or even a full day and may appear on the wrong date in Tempo.

Do the following before you migrate:

1. Check the effective Jira time zone on your Data Center instance. Time zone can be set in more than one place (such as the server/OS, the JVM, and Jira’s Default User Time Zone), so confirm which value Jira is actually using.

2. Check the time zone on your Cloud site. You can see it by opening /rest/api/3/serverInfo on your site and checking serverTimeZone.

3. Make sure both match before you start the migration.

4. If you are unsure which setting applies to your environment, confirm with Atlassian Support, as Atlassian migrates worklogs.

Connect Your Instance and Run the Migration App

Atlassian has comprehensive documentation outlining 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 you select the Projects and the Tempo Apps they are associated with so they are migrated together; otherwise, data will not be migrated correctly.

  2. We recommend selecting the option to migrate all projects, 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 from the migration dashboard to see detailed information about the progress of your migration project while it is running. A progress report screen also shows details of the migration processing.

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 synced yet from Jira to Tempo. Contact the 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, and 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.

14-Day Limit for Post-Migration Tasks

If you require Tempo Support to run specific post-migration actions, such as the Worklog Attribute sync, please submit your request within 14 days of the migration completion.

This 14-day limit is imposed by Atlassian as part of their app data migration policy. After this window expires, automated sync tasks cannot be run, and data may need to be updated manually via API.

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 the Tempo support team with your comments and questions, and they will do their best to help you.