Skip to main content
Skip table of contents

Migrating Between Cloud Instances with Checklists

This page describes how to use Atlassian’s Cloud Migration tool to migrate between two Cloud sites that have Issue Checklist.

Note that there are multiple options for performing migrations.

  • See this page to compare Atlassian’s cloud to cloud migration methods

  • This page provides alternative options for migrations with checklists.


  • You must be an organization and/or site admin on both the source and the destination site to perform the migration. See this page for more information on the required permissions.

  • Ensure that you have the same Jira products (Software, Work Management, Service Management) on both sites.

  • Make sure Issue Checklist for Jira Pro is installed on both sites.

  • Make sure the the Save local checklist items to Jira custom fields global setting is enabled on both sites.


Atlassian Cloud to Cloud migration is in Beta. Jira Service Management projects and Team-managed projects cannot currently be migrated. See this page for a full list of elements that are and are not migrated. If you need to migrate JSM and Team-managed projects, please see this page for other migration options.

Performing the Migration

  1. Navigate to Jira Settings > System and select Migrate cloud site from the left navigation menu.

  2. You will be taken to an overview page with more information about the migration process.

  3. When you are ready to proceed, click on Migration dashboard.

  4. Click Create new migration.

  5. Name the migration and select the destination site.

  6. Select the projects to migrate. Note that JSM and Team-managed projects cannot be migrated with this tool. For other migration options, please see this page.

  7. Migrate users and groups. The tool give you the option to do this in one step or separately.

  8. Do a final check to ensure there are no duplicate projects.

  9. Perform the migration.

Consolidate Checklist Custom Fields

Once the migration is complete, you will have duplicated copies of the Checklist custom fields on the destination site:

  • Checklist Completed

  • Checklist Content YAML

  • Checklist Progress

  • Checklist Progress %

  • Checklist Template

  • Checklist Text

  • Checklist Text (view-only)

  • Checklist Completed (migrated)

  • Checklist Content YAML (migrated)

  • Checklist Progress (migrated)

  • Checklist Progress % (migrated)

  • Checklist Template (migrated)

  • Checklist Text (migrated)

  • Checklist Text (view-only) (migrated)

At this point the checklist data is stored in the Checklist Text (migrated) custom field. Use the automation rule below to move the data into the Checklist Text field:

  1. Navigate to Project Settings > Automation (or Jira Settings > System > Automation rules).

  2. Click Create rule.

  3. Select the Scheduled trigger. The date and time will not matter. You can execute the rule from the automation interface.

  4. Click Save.

  5. Select New branch.

  6. Select Branch rule/related issues.

  7. Select JQL in the Type of related issues dropdown.

  8. In the JQL text field, enter “Checklist Text (Migrated)[Paragraph]" is not empty .

  9. Click Save.

  10. Add a New action under the new branch.

  11. Select Edit issue as the action and Checklist Text as the field to be edited.

  12. Type {{issue.Checklist Text (Migrated)}} in the text box.

  13. Click Save.

  14. Name the rule and Turn it on.

  15. Click Run rule.

If atlassian-addons-project-access does not have the appropriate permissions, you may need to change the Actor on the rule.

Atlassian has announced that they will be deprecating the atlassian-addons-project-access role in the upcoming months and that it will be included in project permission schemes and all issue security levels by default. Learn more.

Once the automation rule has moved the checklist data from the Checklist Text (migrated) field to the Checklist Text field, you can safely delete all of the migrated checklist fields from the destination instance.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.