Migrate Checklists from Jira Server/ Data Center to Jira Cloud
If you and your team are moving from Jira Server/ Data Center to Jira Cloud, be sure - your checklists will be safely migrated as well.
☝🏼NOTE: For the features difference - check theServer & Data Center vs Cloud Comparison for Smart Checklist
There’re two methods of Jira Server to Cloud migration:
☝🏼NOTE: Make sure you are aware of recommendations from Atlassian on Server → Cloud migration and plan it properly
Contents 👇🏼
- 1 Jira Site Import
- 2 Jira Cloud Migration Assistant (JCMA)
- 2.1 For version 6.0.0 and higher
- 2.1.1 Preconditions
- 2.1.2 JCMA flow
- 2.1.3 Post actions
- 2.1.4 Synchronize Data on Cloud Instance
- 2.2 FAQ about Smart Checklist add-on migration in versions 6.0.0 and higher
- 2.2.1 1. What data from Smart Checklist for Jira. Pro addon will be migrated from Server to Cloud?
- 2.2.1.1 Checklist items
- 2.2.1.2 Statuses
- 2.2.1.3 Templates
- 2.2.1.4 Other
- 2.2.2 2. I had custom fields “Checklists” and “Smart Checklist Progress” created on Cloud before I run JCMA, I don’t see migrated addon data in the Jira issues, what can I do?
- 2.2.3 3. Will Smart Checklist global settings on the Server be migrated to Cloud?
- 2.2.4 4. How access rights to Smart Checklist are migrated from Server to Cloud?
- 2.2.1 1. What data from Smart Checklist for Jira. Pro addon will be migrated from Server to Cloud?
- 2.3 For version 5.6.0 and lower
- 2.3.1 Pre-condition
- 2.3.2 Migration
- 2.3.3 Templates Migration
- 2.1 For version 6.0.0 and higher
- 3 Can I Migrate my Smart Checklist for Jira Server/ Data Center License to Jira Cloud?
Jira Site Import
Check how to use Jira Site Import to migrate from server to cloud
Your checklists will be migrated automatically.
Jira Cloud Migration Assistant (JCMA)
Check how to use the Jira Cloud Migration Assistant to migrate from server to cloud.
For version 6.0.0 and higher
Preconditions
Server/Data center
Update the Smart Checklist for Jira Pro add-on to the latest version.
Update Jira Cloud Migration Assistant (JCMA) to the latest version.
Cloud
Install the latest Connect version of the Smart Checklist for Jira Pro addon on your Cloud instance;
☝🏼IMPORTANT: The recently released Forge version of Smart Checklist does not support JCMA migration yet. If you need to migrate your checklist data, you’ll need to install the Connect version of the app first. Once the migration is complete, you can then switch back to the Forge version.
How to migrate using JCMA (workaround for Forge users):
Step 1: Uninstall the Forge version of Smart Checklist
Go to Jira Settings → Apps → Manage Apps.
Find Smart Checklist (Forge version) in the list.
Click to expand the app details.
Click Uninstall and confirm the removal.
⚠️ Warning: Uninstalling the Forge version will result in the loss of any checklists and templates created using it. This is due to Atlassian's policy on app data retention upon uninstallation.
Learn more 👉🏼 https://developer.atlassian.com/platform/forge/storage-reference/hosted-storage-data-lifecycle/#app-reinstallation
Step 2: Enable private listings and development mode
Go to Jira Settings → Apps → Manage Apps.
Scroll down to the Settings section.
Enable both checkboxes
Confirm the changes and refresh the Manage Apps page to see the changes.
Step 3: Install the Connect version of Smart Checklist
Stay in Manage Apps.
Click Upload app.
Enter the following URL to install the Connect version of Smart Checklist:
https://pro.jirachecklist.com/atlassian-connect.json
Click Upload and confirm the installation.
Step 4: Migrate data using JCMA
Follow the JCMA migration steps outlined in our detailed guide: 👉🏼 Migrate Checklists from Jira Server/ Data Center to Jira Cloud | JCMA flow
🔹 Important: Before updating to the Forge version, make sure to synchronize checklist data on your Cloud instance. Learn more 👉🏼 Synchronize Data
Activate your Smart Checklist for Jira. Pro addon license/trial;
Do not create custom fields `Checklists` and `Smart Checklist Progress` in advance.
JCMA flow
Navigate to Administration > System > Select “Migrate to cloud” in the left column.
Step 1: Assess your apps.
Select Smart Checklist as an app that is `Needed in cloud`:
Step 2: Prepare your apps.
Connect to your cloud instance.
Check that you have Smart Checklist for Jira. Pro addon installed.
Agree to migrate addon data.
Step 3: Assess and prepare your users.
Connect to your cloud instance.
Click “Begin assessing”.
Fix invalid emails if needed.
Choose from the offered options what to do with users that have invalid emails.
Click “Review and apply”.
Click “Apply to all migrations”.
Step 4: Review all email domains.
Review and mark email domains as trusted so that you migrate users with only email domains you trust.
Click “Done”.
Step 5: Migrate your data.
Click “Create a migration”.
Click “Connect to cloud”.
Enter the name of the migration.
Select migration stage.
Select Cloud instance.
Click “Choose migration options”.
There are two available options: “Migrate all data” and “Choose what to migrate”.
Select “Choose what to migrate”.
Select Projects, Users and Groups, Customers, and Apps to migrate.
Run pre-migration checks and fix errors if needed.
Review migration.
Run migration.
Post actions
Wait until your migration finishes and check its status for Smart Checklist for Jira. Pro addon:
If the migration status of the Smart Checklist for Jira. Pro addon data is “Completed” - the server part of the migration is successfully finished, you can wait for a few minutes and check your data on the Cloud instance:
In case during migration of the data some issues occur with data exporting from Server or connection to Cloud - migration status will be failed with error message available in the details:
You can check detailed logs for Smart Checklist migration by opening the page: /plugins/servlet/railsware/migrationlog
☝🏼NOTE: Smart Checklist content is migrated together with your project data.
This means you can’t migrate Smart Checklist content for projects that are already available in the Cloud instance.
Synchronize Data on Cloud Instance
After migrating to the cloud, Smart Checklist data is stored in the database. However, some functions may not work correctly as they rely on data stored in issue properties and custom fields.
To resolve this, we recommend to Synchronize Checklist Storages after completing the JCMA migration.
☝🏼NOTE: For detailed instructions, see the guide here: Synchronize Data
FAQ about Smart Checklist add-on migration in versions 6.0.0 and higher
1. What data from Smart Checklist for Jira. Pro addon will be migrated from Server to Cloud?
We did our best to migrate all the data, but unfortunately, due to differences in Server and Cloud versions - there are some data types that will be available on Cloud in a different way or not available at all. Please see details information in the table below:
Data type | Migration support | Visibility on Server | Visibility on Cloud |
---|---|---|---|
Checklist items | |||
Checklist items with different markup:
| fully supported |
|
|
Checklist items with dates | Supported, different UI |
|
|
Checklist items with real assignees | Supported, different UI |
|
|
Checklist items with not-existed assignees | Supported, different UI |
|
|
Statuses | |||
Default statuses | fully supported |
| |
Custom statuses | Supported, ORDER not KEPT |
|
|
Templates | |||
Manual global / project templates (with trigger = none) | fully supported
| global project | global
project |
Global / project template with trigger “Issue created” without additional conditions | fully supported |
|
|
Global / project template with trigger “Issue created” with “Issue Type” condition (is one of / equals) | fully supported |
|
|
Global / project template with trigger “Issue created” with “Issue Type” condition (all issue types) | fully supported |
|
|
Global / project template with trigger “Issue created” with “Issue Type” condition (is not one of / does not equal) | Partially supported |
|
|
Global / project template with trigger “Issue created” with any conditions different from “Issue Type” | Partially supported |
|
|
Global / project template with triggers “Issue updated”, “Issue transitioned” with any extended conditions | Partially supported |
|
|
Global template with “Multiple projects” selected | Supported, different logic |
| Template will be saved as “project template” in migrated projects |
Other | |||
“Modify Smart Checklist” post function | NOT supported |
| not migrated, as feature not available in Cloud |
“Smart Checklist Completed” validator | NOT supported |
| not migrated, as Cloud has different implementation |
Smart Checklist history | NOT supported |
| not migrated |
2. I had custom fields “Checklists” and “Smart Checklist Progress” created on Cloud before I run JCMA, I don’t see migrated addon data in the Jira issues, what can I do?
In this case, after migration you will have duplicated custom fields:
Smart Checklist Addon on Cloud is using “Checklists” and “Smart Checklist Progress” custom fields to sync data in, so after migration to have migrated data saved to the addon database (and visible in the addon) - you need to synchronize data from custom field to addon database.
Note: this process runs in the background and may take some time before all the data finishes synchronizing.
3. Will Smart Checklist global settings on the Server be migrated to Cloud?
Smart Checklist addon has the next settings based on versions:
Server / Data center
SC Addon visibility per Project
Display statuses for checklist items
Strikethrough checked items
Show on the customer portal
Notify assignees
Cloud
SC Addon visibility per Project
Display statuses for checklist items
Strikethrough checked items
Show on the customer portal
Notify assignees
Settings that are available only in Server - cannot be set up on the Cloud version.
Settings that are available in both versions are set up separately on different instances and are not migrated during JCMA migration.
4. How access rights to Smart Checklist are migrated from Server to Cloud?
In the Server version - access to Smart Checklist is managed by Jira permissions, so permissions are migrated together with users and groups via the JCMA tool to Cloud.
On the Cloud instance, you can proceed with using default Jira permissions or configure custom permissions for the Smart Checklist add-on.
For version 5.6.0 and lower
Pre-condition
"Checklists" custom field (mandatory) and "Smart Checklist Progress" custom field (optional) must be added to your Jira Server instance and must keep checklists' values.
Check the instructions on adding Checklists and Smart Checklist Progress custom fields to Jira Server (actual only for versions lower than v.5.0.0).
Please check if you use Custom Fields (Checklists
, Smart Checklist Progress
) for your Cloud instance before migration. They are optional for Cloud, but can be added manually by Jira Admin.
Log in as a user with the JIRA Administrators global permission.
Choose the cog icon at the top right of the screen, then choose Issues.
Select Fields > Custom Fields to open the 'Custom Fields' page.
Search for “checklist“ and check if there are two Custom Fields available:
Checklists
,Smart Checklist Progress
If there are no results, then you can safely proceed with migration using JCMA tool.
If the fields are present, please continue reading below:
If you would like to migrate Jira Server / Data Center to Jira Cloud instance with pre-created Custom Fields it will cause additional migrated Custom Fields creation which will not be available for Smart Checklist. These additional fields will store all the data from Jira Server / Data Center: Checklists (migrated)
, Smart Checklist Progress (migrated)
.
In this case you would need to copy all information from Checklists (migrated)
to Checklists
to restore the Smart Checklist data for each ticket.
At the same time, Smart Checklist Progress (migrated)
field can be removed, because when you copy data to Checklists
the Add-on will recalculate the existing Smart Checklist Progress
field accordingly.
Please note:
If you add the Checklists
custom field after some time of using Smart Checklist, it is important that you first run the storage migration on the server side to ensure that all data is synced. Then you can proceed with migration to the cloud instance.
Migration
Run your migration with Jira Cloud Migration Assistant tool
custom fields “Checklists” and “Smart Checklist Progress“ will be created on the target instance (learn more about the Custom Fields Setup) with checklists content
Then go to Apps → Manage Apps → Smart Checklist → Global Settings → Synchronize checklist storages
Click “Synchronize” button
The data from “Checklists” custom field would be transferred to a database and checklists per Jira issues will be created.
NOTE: the process may take a while. Make sure to run it out of working ours of your organization/
Templates Migration
Templates won’t be migrated automatically at this moment. You have to re-create them manually on the target Cloud instance one by one.
Follow the steps below
Can I Migrate my Smart Checklist for Jira Server/ Data Center License to Jira Cloud?
Unfortunately, no. Smart Checklist for Jira Server/ Data Center license is a one-time purchase with optional maintenance, whereas Cloud purchases are recurring subscriptions. As such, existing Server/ Data Center app licenses cannot be transferred or credited to Cloud. These are independent licenses that need to be paid for separately.
If you already purchased your Jira Server/ Data Center license via the Atlassian Marketplace, you may contact Atlassian Support to see if you are eligible for a refund.