/
Migrate to Cloud

Migrate to Cloud

Summary

We do not support the migration of archived projects. Templates or checklists that are attached to the archived Jira project are ommited. If you experience any issues with migration, please ensure that the archived projects are unarchived.

Multiple Checklists for Jira are available for all hosting options - Jira Cloud, Jira Server, and Jira Data Center. The feature set and the user interface on all of those options are the same, which means that you can freely migrate to another hosting without any loss of features or the need to onboard users with the app again.

The migration guide for Jira is available here: Jira Cloud Migration Assistant | Atlassian Support.

The following data will be automatically migrated from Jira Server/Data Center to Cloud:

  • Checklists

  • Checklists history

  • Project templates

  • Global templates

  • Automations

  • Statuses

  • Settings

  • Permissions

How to migrate data

Checklists support migration during or after the project migration. This means that you can first export your projects, and then, after confirming everything is ok, decide to export checklists data or do it at the same time. No matter which way you choose to migrate, the steps are the same.

  1. Create a new migration

  2. Configure everything the same way as you migrated your projects:

    1. same destination cloud site

    2. same migration stage

      image-20260403-081536.png

  3. Click Choose migration options

  4. Click select in projects section

    image-20260403-081710.png

  5. Select App data only

    image-20260403-081734.png

  6. Select projects you want the checklists to be exported from

    image-20260403-081813.png

  7. Continue with migration

If you select App Data Only, the issue you already migrated will not be altered in any way except for the checklist data. These data are: issue properties and the Checklists progress custom field.

Please be aware that migration replaces the checklist data present on your cloud. For example, if you created a Project template in Project A and added a checklist to an issue A-1, and select this project A in your migration, your data on the cloud will be replaced if this project has templates and checklists on DC.

 

Migration workflow and what Passed means

Checklist migration, when selected to migrate alongside projects or when selecting app data, only works the same, so you can decide if you want to migrate 2 things at the same time or not.

When migrating data, be aware that we OVERWRITE existing data. For example, if your users started using your cloud instance before migration finished, you risk replacing their checklists or templates with your DC version.

Migration starts by moving all your Settings, Templates, Automations, Statuses, and Permissions. This shouldn't take long, even on instances with thousands of users.

Most of the time is spent migrating checklists and checklist history. We move project by project, issue by issue, and migrate the data. At certain times, we log progress in the logs(more about it in the section logs below), where you can see the current progress.

Important: what we consider a passed migration.

We try to migrate every checklist, but sometimes a work item can be deleted, which prevents the checklist from being added. We decided that problems like this will NOT stop the migration and will instead be logged as a warning in the log file.

Another similar problem is when a project is restricted from Checklists, and we don’t have permissions to either view or edit work items in this project. A similar approach applies here. We log it as a warning and do not stop the migration.

Log file

How to access it?

1 Open the migration
2 Open the app migration menu (highlighted below)

image-20260327-105704.png

3 Download logs

image-20260327-105832.png

4 Open with tools like Excel

General info

During or after migration, a log file with the current status is available to you. We recommend downloading it at least once every 4 hours because of Jira DC limitations(where the log file is cut after ~4.5 hours, and you can’t preview old messages).

What can you find in a log file?

Status

Status: IN_PROGRESS | Progress: 16 | Message: globalTemplates

First is the lien that should show up very often. It tells you the status, Progress percent, and what is currently being migrated.

Problematic work items

[Issue data migration] Failed issues checklists migration. Likely by missing permissions or not existing on cloud: 10334

It tells you which work items we had problems migrating. The most common cause is the work item being deleted/moved on the cloud, or our app not having edit and browse permission to a project.

Important note

Please be aware that we try to migrate work items up to 4 times. Sometimes the logs can show 100% while we are still trying to migrate the problematic work items. It happens when a lot of work items encounter this problem. If it ahppens don’t worry, and give us a few more minutes to complete all tasks.

Limitations:

Non-native Jira Workflow Functions are currently not supported by the Jira Cloud Migration Assistant. This means, they must be manually re-created on the cloud site if you’d like to continue using them.

This affects: post-functions, validators, conditions. Please note that if there was any Checklists-related validator added to a transition, such a transition of issue will not work on Cloud after migration until it is manually deleted and re-added.

 

 

Do you have any questions or feedback? Feel free to contact us here