Jira Cloud Migration Assistant Application

About Jira Migration Assistant Application

Tempo is excited to offer the Jira Cloud Migration Assistant (JCMA) application, built upon Atlassian's Jira Cloud Migration Assistant. The JCMA tool enables you to automatically migrate nearly all your Tempo data, as well as data from other Jira add-ons. It is designed to support Server or Data Center customers who are using the latest Tempo versions and their compatible Jira version.

For more information, refer to Tempo's Server products compatibility list.

Jira Pre-Migration Checklist

Before you start the migration, follow the pre-migration checklist as recommended by Atlassian. The checklist is required when migrating by JCMA or by manual import.

Set Debug Level Logging

Enable the debug level logging option on your Server or 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.

   Open

   

    

4. Click the Configure logging level for another package.

   Open

   

    

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.

Migration in Batches

You can migrate your data in batches in case you have instances with large data. It is then recommended to migrate your data in batches. For example, if your instance has 1000 projects, then break down your data and migrate it in multiple batches.

We recommend the following best practices when migrating in batches:

1. When migrating in batches, make sure to select Tempo and the projects to migrate for a specific date for each batch.

   It is mandatory to select Tempo for every batch otherwise, any information that's related to Tempo will not be migrated for the migrated batches.

2. Projects must be in the same batch as issues. For example, if reports of projects are not included in the same batch then problems will be encountered during the migration.

3. Migrating Tempo batches are deemed incorrect if all related projects and data are not in the same batch.

4. Avoid changing any Tempo configuration related to accounts, teams, etc.

5. A reminder that batches are only used to migrate data.

Tempo Data Included in Automated Migration

The migration application automates the packaging and migrating the application data with your Jira data to the Cloud. The following Tempo data is included in the migration with the status that indicates a full migration, or data that requires manual intervention from Tempo support.

Full migration. Completed by Jira Migration Assistant App.

Requires manual adjustment by contacting Tempo support for assistance.

Tempo Data Excluded from Automated Migration

Tempo is working with Atlassian to include all Tempo data in the EAP Migration Assistant tool; however, the following data is still not part of the migration EAP version yet: