Switching · Checklist Flow

Switching from Smart Checklist 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 Smart Checklist's own field. The other app is only read, never changed, the dry run writes nothing, and every import run can be undone.

Run live once, on 17 October 2026 on our own test site with Smart Checklist Pro (trial) installed, with Checklist Flow 2.7.0: dry run, import, Undo and a second import matched sections, Required, N/A, ticks and the Definition of Done result. The importer changed afterwards (priority and custom statuses, the field's format map, preselecting the field; 29 and 30 October), and those changes have not been run live. Not tested with the Free edition. Smart Checklist Free reaches end of support on 15 December 2026: see Smart Checklist Free end of support.

What moves

Every Smart Checklist on the work items your JQL finds, read from Smart Checklist's own field ("Smart Checklist", or "Checklists" on older installs): items, sections, mandatory items, done and skipped states. Several checklist tabs become named checklists.
Done items as checked, skipped items as N/A, mandatory items as Required.
Assignee and due date (when written as YYYY-MM-DD), where Smart Checklist wrote them in its text, and details lines as notes.

What does not move

Smart Checklist templates and its change history: they are not readable by other apps. Save templates again in Checklist Flow, or install them from its template library.
Priority and custom statuses move only where they can: priority (High, Medium, Low) is imported. A status (a [Failed] prefix, or a symbol such as ~ for In Progress or your own) is set when the work item's project has a status with the same name; otherwise its name stays in the item text. Done and skipped items keep their checked and N/A state instead.

Before you start

On older installs that use the "Checklists" field, run Smart Checklist's Synchronize first, so the field holds the current checklists. The current "Smart Checklist" field needs no sync.

How

A Jira administrator opens Jira settings, Apps, Checklist Flow settings, tab Switch from another app, and chooses Smart Checklist and its field (Smart Checklist, or Checklists on older installs). 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 Smart Checklist 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 Smart Checklist 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 Smart Checklist?

No. Checklist Flow only reads what Smart Checklist 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?