Switching · Checklist Flow
Switching from Multiple Checklists (SolDevelo) to Checklist Flow
Checklist Flow for Jira 3.1.1 is the production version (1 November 2026). Last updated 1 November 2026. On the Atlassian Marketplace.
One dry run and one import, read from SolDevelo's issue properties; no field to choose. The other app is only read, never changed, the dry run writes nothing, and every import run can be undone.
Tested on 17 October 2026 on our own test site with Multiple Checklists installed, using a test build whose SolDevelo importer is the same as in Checklist Flow 2.7.0 and 3.0.0.
What moves
#- Every checklist SolDevelo stores on the work item (its issue properties): item text, with formatting removed, required, and completed as checked.
- Several checklists on one work item become several named Checklist Flow checklists with the same names; a single checklist lands in the default checklist.
What does not move
#- SolDevelo's custom status names, people and dates on items: their meaning is not documented, so they are not mapped.
- SolDevelo templates and history.
Before you start
#Nothing to prepare: SolDevelo's data is already on the work items.
How
#A Jira administrator opens Jira settings, Apps, Checklist Flow settings, tab Switch from another app, and chooses Multiple Checklists (SolDevelo). Enter a JQL (start with one project), click Dry run: it writes nothing and shows how many work items and items would be imported, and which work items are skipped and why. Then click Import. The page works through the work items in steps and continues on its own until done.
Run both side by side
#Checklist Flow only reads the data of SolDevelo and never changes it, so both apps can run while you compare. A work item that already has a Checklist Flow checklist is skipped, unless you tick Add below an existing Checklist Flow checklist; the import then goes into the default checklist, above any named checklist.
Roll back
#Undo this import under Earlier runs removes the items that run added; items people added since stay. Running the same migration again adds nothing twice, and work items whose SolDevelo checklist changed after the import are listed for you instead of being imported a second time. Each work item's history records the import: from which app, by whom and when.
Who can do it
#Jira administrators, with or without a paid Checklist Flow licence.
More on Checklist Flow: documentation, comparison with other apps.
Common questions
#Does the import change Multiple Checklists (SolDevelo)?
No. Checklist Flow only reads what Multiple Checklists (SolDevelo) left behind and never changes it, so both apps can run side by side while you compare.
Can I see what will be imported before anything is written?
Yes. Every path starts with a dry run that writes nothing and shows what would be imported and what would be skipped.
Can I undo an import?
Yes. Every import run can be undone, and running the same import again adds nothing twice.
Who can run the switch?
Jira administrators, with or without a paid Checklist Flow licence.
Atlassian, Jira, Confluence and Jira Service Management are trademarks of Atlassian. Other product names are trademarks of their owners and are used only to identify those products. Stanki Guild is not affiliated with, endorsed or sponsored by Atlassian or by any vendor named on this page.