Switching · Checklist Flow

Switching from HeroCoders Checklists 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, once HeroCoders' custom field sync is on. HeroCoders import was run live once, on 17 October 2026 on our own test site with HeroCoders Checklists Pro (trial), on one work item, after its Sync checklists to Custom Fields setting was turned on. The text parser has not changed since; the migration page around it did (field preselect, 30 October) and was not run live. Not run on production 3.1.0. The other app is only read, never changed, the dry run writes nothing, and every import run can be undone.

What moves

The checklists HeroCoders copies into its "Checklist Text" field: items and headers.
Checked items as checked, skipped items as N/A, mandatory items as Required, descriptions as notes.
Several HeroCoders checklists on one work item become several named Checklist Flow checklists; a single one lands in the default checklist.
Checklist for Jira Enterprise (formerly Okapya) has its own entry, Checklist for Jira Enterprise, in the same list of apps. It reads the same "Checklist Text" field when its sync is on, so turn the sync on, run the dry run first and compare a few work items.

What does not move

HeroCoders templates, global checklists and its history: they are not readable by other apps.
Dates and @mentions: they stay in the item text.

Before you start

HeroCoders writes the "Checklist Text" field only when its administrator turned on Sync checklists to Custom Fields. Turn it on and wait until the sync progress on HeroCoders' Global Settings page reaches 100%: until then a work item's field stays empty (in our test on 17 Oct 2026 it filled as soon as the checklist changed). Then migrate. Without the sync, Checklist Flow finds nothing to import. Either field works: "Checklist Text" or "Checklist Text (view-only)".

How

A Jira administrator opens Jira settings, Apps, Checklist Flow settings, tab Switch from another app, and chooses HeroCoders Checklists and its Checklist Text field. 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 HeroCoders 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 HeroCoders 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 HeroCoders Checklists?

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