(new) 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.
There’re two methods of Jira Server to Cloud migration:
Make sure you are aware of recommendations from Atlassian on Server → Cloud migration and plan it properly
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 5.7.0 and higher
Preconditions
Server/Data center
update the Smart Checklist for Jira. Pro addon to the latest version
update Jira Cloud Migration Assistant (JCMA) to the latest version
Cloud
install the latest version of the Smart Checklist for Jira. Pro addon on your Cloud instance
activate your Smart Checklist for Jira. Pro addon license/trial
do not create custom fields `Checklists` and `Smart Checklist Progress` in advance
JCMA flow
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: Create and run new migration.
Enter the name of the migration.
Select Cloud instance.
Select Projects, Users and Groups, and Customers to migrate.
Review migration settings and fix errors if needed.
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
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.
FAQ about Smart Checklist add-on migration in versions 5.7.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 | * all dates are visible in same color | * dates in the past, current and future visible in different colors |
Checklist items with real assignees | Supported, different UI | * id (username/login) is visible | * user full name is visible |
Checklist items with not-existed assignees | Supported, different UI |
|
|
Statuses | |||
Default statuses | fully supported |
| |
Custom statuses | Supported, ORDER not KEPT |
| * after migration it is needed to return needed order manually |
Templates | |||
Manual global / project templates (with trigger = none) | fully supported
| global project | global
project |
Global / project template with trigger “Issue created” without additional conditions | Partially supported | * template is applied to all issues types | * template can be applied only manually |
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 | * template applied based on conditions | * template migrated without triggers (can be applied only manually) |
Global / project template with trigger “Issue created” with any conditions different from “Issue Type” | Partially supported | * template applied based on conditions | * template migrated without triggers (can be applied only manually) |
Global / project template with triggers “Issue updated”, “Issue transitioned” with any extended conditions | Partially supported | * template applied based on conditions | * template migrated without triggers (can be applied only manually) |
Global template with “Multiple projects” selected | Supported, different logic | * template is visible on “Global templates” tab | 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.
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 https://railsware.atlassian.net/wiki/spaces/CHKSDC/pages/2349925102) 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.