Key Migration Steps

Abstract

Follow the steps to successfully migrate your Server/Data Center to Cloud using the Migration Assistant EAP

Get Access to EAP Migration Assistant App

The first step is to obtain access to the EAP Jira Cloud Migration Assistant App . The feature flag for the EAP in Jira is managed by Atlassian. Once it is confirmed that the feature flag is turned on, you should reach out to Tempo Support team to enable the feature for your Cloud instance.

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.

migration_app_assess.png
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.

Once you install Tempo, it's very important that you take the following steps to configure your instance:

  1. Set up internal issues in your Jira projects.

    The migration process can expose internal issues to people without the proper permissions. Given the subsequent privacy concerns, we recommend that you configure internal issues immediately after you configure Tempo in your new Cloud instance. This may entail:

    • Archiving your internal issues and creating new issues for Jira projects

    • Implementing security schemes, or

    • Simply moving the internal issues to other projects with limited permissions

    Note

    If you want your internal issues from your Server instance to remain private, be sure to create new internal issues. Reusing old internal issues could expose personal data in the migrated worklogs due to the way data is stored in Tempo Server.

  2. Re-examine your project permission settings.

    The project permission settings can be different on Tempo Cloud than Tempo Server. For instance, Tempo Cloud has the View issues hours permission option that does not exist in Tempo Server. Make sure to examine this and other permissions to determine if adjustments are needed.

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.

    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 runt 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.

migration_dashboard.png

Select View details to see detailed in formation 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.

Verify that Data Migrated as Intended

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

  • Worklogs

  • Teams and Team Roles

  • Permissions

  • Workload and holiday schemes

  • Accounts, account categories and customers

  • Approvals and plans

  • Custom field values

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.

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.

Update Worklogs in Cloud Instance

Update the worklogs in your new Cloud instance with missing parameters, for example billed hours and worklog attributes. These are a few things to keep in mind when doing so:

  • Worklog attributes from the type DYNAMIC_DROPDOWN are not supported on Jira Cloud and need to be converted to a static list (type STATIC_LIST) values.

  • The values from the worklog attributes for each worklog are exported with the worklog servlet and the REST API as plain text/numeric values with exception of worklog attributes from the type ACCOUNT (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 cannot be edited afterwards.

  • If you have a worklog attributes of the type DYNAMIC_DROPDOWN, 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.

Update Tempo Account and Team Custom Fields

The Tempo Account and Team Custom Fields for the Jira issues in the new Cloud instance must be updated. This can be done using Jira Cloud REST API.

Feedback and Support

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