Guide For Migrating To Smart Checklist From A Different Checklist Add-on

Add-ons, especially smaller ones, can be “behind the scenes”, meaning people may not remember the brand or the add-on name. Sometimes, we have cases of people contacting our support, but they are using another checklist add-on. 😅

That said, there will be times when you’ll feel the need to migrate between different add-ons, as some may offer specific bits of functionality your team requires. Maybe the add-on you were using is not supported anymore. Perhaps your team requires more customizable permissions. Or there’s a need for certain specific integrations like JMWE or Deep Clone. Or maybe you are looking for an add-on that’s available on Jira Data Center? Whichever the case, you can migrate your checklists into Smart Checklist.

This article will cover migration from:

  • CSV
  • Trello
  • Issue Checklist
  • My To Do

Please note that you will need Jira Admin permissions to export and import checklists.

Importing issues from CSV

Please note that you must have the Checklists custom field in your instance before the import. 

  1. Prepare a proper CSV file containing checklists. Either manually or by exporting from Jira.
    • Manually: Make sure that the formatting keeps new lines. You can download a CSV import example here.
    • Exporting from Jira: You can do it via the Issues Search form.
  1. Clean up CSV, leave only needed columns (fields), e.g., Issue Key (for future mapping Jira issues), Summary, Checklists, Smart Checklist Progress.
    • If issues from more than 1 project are to be imported – then leave the Project column in CSV.
  2. Go to System → Import and Export → External System Import → CSV.
    • Jira Server.
    • Jira Cloud.
  3. Choose a CSV file.

  4. Map fields.
    • Map Issue Key CSV field to Issue Key Jira field and check ‘Map field value’ (by that, field values will be taken for updating a ticket).
    • Map Summary CSV field to Summary Jira field. 
    • Map Checklists CSV field to Checklists Jira field, however, make sure to leave the ‘Map field value’ checkbox empty! Otherwise, checklist value won’t be imported.
  5. Begin import.
    • Always do test runs on test issues/values!
  6. Once the import is finished – the “Checklists” custom field in proper Jira Issues will get updated with Checklists values from CSV.

Importing checklists from Trello

Here’s a fun bit of random trivia: We developed Smart Checklist when our team outgrew Trello, and the checklist functionality was missing from Jira. Therefore, we needed both the tool and a way of importing our data.

The Smart Checklist exporter power-up for Trello allows you to convert your Trello Checklists into either CSV or TXT – both formats are supported by Smart Checklist – and then migrate them into Jira.

We already have a detailed guide on integrating Jira and Trello. You can take a closer look at the process of exporting your checklists there, or look at this video for more tips.

Migrating from Issue Checklist to Smart Checklist

Smart Checklist allows you to import your checklists from Issue Checklist in a few steps. 

NOTE 1: Issue Checklist custom field must be available for the migration to succeed. You can check whether it is available or not by accessing Issue Checklist settings from your Global Settings. From there, you’ll see if the Save checklist data to Jira custom fields setting is disabled or not. 

NOTE2: It’s highly recommended to manually create the same custom statuses you had in Issue Checklist in Smart Checklist before the import. If, during import, some statuses are missing, they will default to the TODO status.

Once you are sure that th  Save checklist data to Jira custom fields  setting is enabled, follow these steps to migrate your checklists into Smart Checklist. 

  1. Navigate to Apps > Manage your apps > Smart Checklist Settings.
  2. Click on the “Import Checklists” tab.
  3. Click on the Projects link to redirect you to the “Projects” tab.
  4. Toggle Smart Checklist on for the projects for which the import needs to be done.
  5. Come back to the “Import Checklists” tab.
  6. If you want to replace checklist items with the new imported values – Select the checkbox “Override existing Smart Checklist items”.
  7. Click “Read more” to get more details on the import process and formatting conversion.
  8. Click “Import”. The confirmation pop-up will be shown.
  9. Click the “Import” button in the pop-up, and a pop-up with the message “Import has started successfully” appears. The “Import” button will be disabled, and a tooltip “There’s already an import in progress.” will be present.
  10. The importing process will take some time. Reload the page manually to see the import result.
  11. Once it is completed, the date and time of the last import will be displayed. A message with the number of successfully imported checklists will be shown. Additionally, a link to the detailed log is present.

Formatting differences

There’s a slight difference between the syntaxes of Smart Checklist and Issue Checklist. We will convert the syntax automatically when importing data. You don’t need to convert anything yourself. But just FYI, here are the main differences. Perhaps this information will come in handy if you use syntax in some third-party automations.

Multiple checklists

As I mentioned, Smart Checklist does not have multiple checklist functionality. Our team is working on adding this feature at the moment. However, if you wish to migrate now then the different checklist names will be formatted into the <h1> header during the migration.


The separators used by Issue Checklist are similar to Smart Checklist’s header functionality. They start with —.

These separators will be formatted into the <h2> header tag during the migration. 


As mentioned before, we suggest that you create the same custom statuses you had in Issue Checklist in Smart Checklist before the import.

In case you choose to ignore this step, all of the statuses will default to the ToDo status during the migration.


If additional mailto data (subject, body, etc.) is available in the brackets, <> will be added at the start/end of each link with a space.

Migrating from Issue Checklist: FAQ

Q: What happens when an import fails?
A: Each project imports independently. So, whenever an import fails, it will fail only for that specific project. Then, also, we halt the importing for that project.

Q: One of my imports failed in the middle of the process. Is it possible to roll back?
A: No.

Q: Only one of my projects failed to import. Is it necessary to re-run the importing on all of them?
A: No, you can enable only the projects you want to import. Remember that.

Q: If I try to re-import, will I have duplicates?
A: Yes. However, there is an option to check “Override existing Smart Checklist items” that will replace all existing checklist items with the new imported values.

Q: What to do if the app says that migration has finished, but my custom fields aren’t updated yet?
A: Custom fields are updated in a background job after importing, so it might take a little longer than the importing itself. However, you can always “Synchronize storages” to sync custom fields.

Migrating from My To Do

My To Do checklist app is no longer available on the Atlassian Marketplace as part of Atlassian’s commitment to stand with Ukraine. This means that My to Do users are no longer able to renew their subscriptions. Our support team has received several requests regarding assistance with migration and we have developed a script that will help you import your data into Smart Checklist quickly and relatively easily. 

The migration relies on exporting your data in a CSV format. Please make sure that you will be including the following fields for the export to succeed.

SummaryThe name of a Jira taskPrepare migration data from My ToDo to Smart Checklist
Issue keyKey of a Jira taskSC-1339
Custom field (To Do List)JSON Array of My ToDo items[{'id': 'checklist_item_1',
'linkedIssueKey': '',
'type': 'done',
'mandatory': ''},
{'id': 'checklist_item_2',
'linkedIssueKey': '',
'type': 'done',
'mandatory': ''},
{'id': 'checklist_item_3',
'linkedIssueKey': '',
'type': 'done',
'mandatory': ''},
{'id': 'checklist_item_4',
'linkedIssueKey': '',
'type': 'todo_undone',
'mandatory': ''},
{'id': 'checklist_item_5',
'linkedIssueKey': '',
'type': 'done',
'mandatory': ''},
{'id': 'checklist_item_6',
'linkedIssueKey': '',
'type': 'done',
'mandatory': ''}]  

Once the CSV document is ready, you’ll need to launch the colab file. This file will prepare the migration file. 

  1. Go to the colab file
  2. Upload your CSV to the colab.
  1. There’s a “Run” button next to each of the cells. Click these buttons one by one. 
  1. You will see a list of CSV files you have uploaded after running this cell.
  1. Paste the filename from the previous list into the field.
  1. You’ll see this screen if the operation was successful.
  1. You can grab the prepared CSV and import it into Jira. We’ve talked about this type of import a little earlier on in this article. 

Try Smart Checklist for free!