Migrate checklists from Checklist for Jira, My ToDo, Elements Checklist

Moving to Jira Cloud? We’ve got you covered!

Smart Checklist supports migration from Checklist for Jira Enterprise, My ToDo and Elements Checklist Data Center to Jira Cloud ⭐️

1 Overview
2 Import checklist data
3 Imported data
- 3.1 Checklist for Jira Enterprise
- 3.2 My ToDo
- 3.3 Elements Checklist
4 Migrate Smart Checklist to Cloud
5 Support during migration

Overview

Migrate to enterprise-grade Smart Checklist in Cloud while preserving checklist data from other checklist vendors and unlocking advanced Cloud capabilities such as Rovo Agent, Checklist Dashboards, and Advanced Automations.

Migrate to Smart Checklist in Cloud in 3 steps

Install Smart Checklist in Data Center
Migrate data from Checklist for Jira Enterprise, My ToDo, or Elements Checklist on Data Center to Smart Checklist for Data Center in one click
Migrate Smart Checklist data from Data Center to Cloud using JCMA ✅

Below, you’ll find a more detailed app comparison and the migration steps to follow.

Import checklist data

Preconditions

Install Smart Checklist in Data Center
Enable Smart Checklist for relevant projects
By default, Smart Checklist is enabled for all projects. If you want to test the migration on specific projects first, you can limit Smart Checklist to those projects only.

Migration steps

Migrate Checklist data
Go to Manage apps → Smart Checklist → Import Checklists Tab and choose the corresponding app to migrate checklist data from:

Choose the Import Options:

Override existing Smart Checklist items: Replace existing checklist items with those from the third-party app recomended
Append to existing Smart Checklist items: Adds imported items to the bottom of existing checklists.
Add to issues with empty Smart Checklist data only: Imports only into issues with no existing Smart Checklist items.

Click “Run import” to import data
A progress bar will appear, showing the import status. This may take some time.
Done! Review Import results ✅
Once the import is complete, the following details will be displayed:

The date and time of the last import
The number of successfully migrated checklists
Errors (if any)
A link to download a detailed log (for sharing with the support team, if needed)

Review results

Import using API

In addition to the user interface, you can run project-specific imports directly using the REST API.

REST API Endpoint

Use the following endpoint to start the migration process for selected projects:

POST /rest/railsware/1.0/migration

Request Body Parameters

The request body should be sent in application/json format and include the following fields:

migrationOption (string): Specifies how the data is handled during the migration.
- Options: OVERRIDE, APPEND, ADD_IF_EMPTY.
migrationType (string): Specifies the source app to migrate from.
- Options: ELEMENTS, MY_TO_DO, CHECKLIST_FOR_JIRA.
projectIds (array of numbers, optional): A list of project IDs to be included in the migration.
dryRun (boolean, optional): Use this option to preview the migration process. When true, the system will generate logs indicating which issues would be affected without making any changes.

Example of Request body

The following example demonstrates how to migrate checklists from the Elements Checklist app to Smart Checklist, using the OVERRIDE option for two projects:

{
    "migrationOption": "OVERRIDE",
    "migrationType": "ELEMENTS",
    "projectIds": [11001, 10900]
}

Checking Migration Status

You can verify the status of a migration process using the following endpoint:

GET /rest/railsware/1.0/migration?migrationType=MY_TO_DO

This will return the current state of the migration for the specified migrationType, allowing you to see whether it has been completed.

Imported data

During migration, checklist data from third-party apps is transformed to fit the Smart Checklist functionality. Elements that are not supported are either simplified or skipped.

Checklist for Jira Enterprise

Feature	Migrated to Smart Checklist
Checklist in Issues	✅ Yes Multiple fields per issue are imported into a single Smart checklist with fields/checklist names turned into headers
Checklist formatting	✅ Yes Headers Items Descriptions imported as Details User assignees Due dates Mandatory items URLs and Jira Issues Links Text formatting (bold, italic etc.) URLs and Links to Jira issues
Checklist Templates	✅ Yes Project context is preserved for templates
Global Items	✅ Yes Imported as regular items to checklists. You can save them as Linked Templates to preserve Global Items functionality
Item statuses	✅ Yes

☝️ Checklist Priorities, Automations, Permissions, Workflow Validators are not migrated and needed to be manually reconfigured. All features are supported on Smart Checklist Cloud.

💡HINT: Read more about Smart Checklist Cloud vs Checklist for Jira by Herocoders Cloud comparison here → Marketplace Comparison

My ToDo

Feature	Migrated to Smart Checklist	Displayed in Smart Checklist

Feature	Migrated to Smart Checklist	Displayed in Smart Checklist
Statuses	✅ Yes It's highly recommended to manually create the same custom statuses you had in My ToDo in Smart Checklist before the import. If, during import, some statuses are missing, they will be created with a similar name but with “Unchecked” state as default in Smart Checklist
Links	✅ Yes Links are supported and migrated in this format: `- [marketplace](https://marketplace.atlassian.com/apps/1211170/my-todo?hosting=datacenter&tab=versions) - link to Atlassian marketplace - [https://community.atlassian.com/t5/Jira-Service-Management/Setting-default-value-for-priority-field/qaq-p/770467](https://community.atlassian.com/t5/Jira-Service-Management/Setting-default-value-for-priority-field/qaq-p/770467)`
User mention	✅ Yes All users present in the User management under the instance and are mentioned in the checklists will be migrated successfully. Full name will be displayed
Date	✅ Yes Dates are supported and will be rendered accordingly
Numbered/bullet point hierarchical lists	✅ Yes As we are not supporting hierarchical lists it will be migrated as one item and rendered as number/bullet point lists
Text Formatting	✅ Yes Italic and code text is supported
Mandatory items (flagged items)	✅ Yes All mandatory items (that are flagged) are supported and imported as mandatory items with a red asterisk in the upper right corner of the checkbox

Elements Checklist

Formatting types	Description	Displayed in Smart Checklist
Multiple panels (checklists)	✅ Yes Unlike our product, Elements Checklist allows users to have more than one panel (checklist). When importing, the different panel names will be formatted into `<h3>` headers. The names of the attributes will be formatted into the <h6> headers in a row separated by `\|`.
Separators	✅ Yes "Separators" in the Elements Checklist are similar to our headers functionality. They start with: `---` `***` `___`
Block quotes	✅ Yes Block quotes are rendered as one item
Lists (Ordered/Unordered)	✅ Yes Lists are rendered as one item
Tables	✅ Yes Tables are rendered as one item
Links	✅ Yes
Images	✅ Yes
Text Formatting	✅ Yes Italic, bold, strikethrough and code text is supported
Headers	✅ Yes All 6 headers are supported and will be rendered accordingly
Formulas	⚠️ Partially Only basic formulas are supported All the number attributes together with the result field will be rendered as a row separated by \|
Files	Files are not supported. They will be rendered with id and file name

Limitations for import from Elements Checklist

Elements Checklist panels can have a structure with different attribute types, and each panel can include a combination of these attributes. Before starting the import, keep the following considerations in mind:

Checkbox Attribute Type: To ensure that Elements Checklist items with checkboxes appear as checklists in Smart Checklist after migration, include the Checkbox attribute type in the panel.

☝🏼NOTE: If the Checkbox attribute type is absent in the panel, items will be imported and displayed as plain text without checkboxes.

Rendering Attribute Values: All values for the attribute types configured for the panel will also be shown in a row, separated by |.

Multiple Panels: If an issue has multiple panels configured, each panel will be rendered with its name as an h3 header. The names of the attributes will appear in a row, separated by |, with an h6 header, followed by the checklist items.

☝🏼NOTE: Note that template migration from Elements Checklist is not supported.

Combination of Attribute types	Displayed in Smart Checklist
Text + User + Version + Checkbox
Text + Date + Issue + Checkbox
Text + Component + Number + Checkbox
Calculation + Checkbox
Text (multi-line) + Checkbox
Text + Select list + File + Checkbox

Migrate Smart Checklist to Cloud

If you want to proceed with migration to Cloud, follow these steps:

Preconditions

Ensure you’re using the latest app version ✅
Install Smart Checklist in Cloud ✅
Install the latest Smart Checklist (Forge) app from the Atlassian Marketplace in your Cloud environment.

Migration steps

Run the migration with JCMA
You can start with selected projects to test the migration and verify results before performing the full migration.
Run data synchronization in Cloud
After the migration is complete, run data synchronization in Manage apps → Smart Checklist → Global settings → Synchronize data.
This step ensures proper app functionality by synchronizing data across Forge storage, custom fields, and entity properties.
Verify migrated data
After migration, review the issues with migrated checklist data in Cloud instance.
Done! Migration completed ✅

Support during migration

Our support team is here to assist you throughout the whole migration process – from sandbox testing to production migration!

📩 Contact us anytime
📞 Need a live call? Reach out to our support team to book a session with a technical team.
📖 Check more detailed documentation for Cloud migration here -> Migrate Checklists from Jira Data Center to Jira Cloud