Switching
Switching from another app
Each of our apps can bring in what another app left behind, so a team can switch without retyping. Every path starts with a dry run that writes nothing, never changes the other app, adds nothing twice when run again, and can be undone run by run. Where the other app keeps its data on the work item or page, it is one dry run and one import; elsewhere you start from its export file. Imported approvals and confirmations are kept as labelled history: they never count as a sign-off or an acknowledgement in our apps.
Using Smart Checklist Free for Jira? Its vendor ends support on 15 December 2026: see what changes and your options.
Checklist Flow and Attestation Flow and Approval Flow are on the Atlassian Marketplace and can be installed from there.
Switching to Attestation Flow for Confluence
#From Comala Read Confirmations
An alternative to Comala Read Confirmations: Attestation Flow reads who confirmed each page in place, with one dry run and one import per space.
From eSign
An alternative to eSign for Confluence: Attestation Flow reads who signed each page in place, with one dry run and one import per space.
From Policy Acknowledgement (Rethought)
An alternative to Policy Acknowledgement by Rethought: export the Audit CSV, paste, dry run and import into Attestation Flow per space.
From QC Read and Understood
An alternative to QC Read and Understood: export, paste, dry run, import into Attestation Flow per space; imported confirmations are labelled history.
From Read & Confirm (MiddleCore)
An alternative to Read & Confirm by MiddleCore: Attestation Flow imports each page's export from the page itself, with a dry run first.
No import path yet, or not yet tried with real data:
From Confirm and Chase (Paperlatch): A Paperlatch article says its CSV export includes earlier rounds, and Attestation Flow's "Another app (CSV)" option reads a CSV with a page, a person, a version and a time. We have not seen a real export, so this has not been tried: check the dry run's column mapping first.
From QC Documents (page reviews): No import path. Its listing names page reviews but no export or import, so there is nothing for Attestation Flow to read. QC Read and Understood confirmations can be imported; see the QC Read and Understood guide.
Switching to Approval Flow for Jira
#From Approval Path
An alternative to Approval Path for Jira: Approval Flow carries over the approvals still open in one step and imports past history from its CSV.
From Group Sign-Off
An alternative to Group Sign-Off: Approval Flow reads its approval fields in place by JQL, one dry run and one import, pending approvers carried over.
From Herzum Approval
An alternative to Herzum Approval: export the history as CSV, paste, dry run, import into Approval Flow; imported history never counts as a sign-off.
From Jira Service Management or Jira Premium approvals
An alternative to Jira Service Management or Jira Premium approvals: Approval Flow reads the Approvals field and approver fields in place by JQL.
From Quorum Approvals
An alternative to Quorum Approvals for Jira: export its Reports CSV, paste, dry run, import into Approval Flow; imported history is labelled.
No import path yet, or not yet tried with real data:
From Approval for Jira (Candylio): Approval Flow has a Candylio option among its CSV imports, which reads common column names such as work item key, approver, decision and date. We have not seen a real Candylio export, so it has not been tried with one: check the dry run's column mapping before you import. Keep Candylio's history there while you run both.
From Sign for Jira (MyStatement): Its listing says the audit logs of signatures export to CSV, JSON or print. Approval Flow's "Another app (CSV)" option reads any CSV with a work item key column and recognisable headers, so an audit log export may import as labelled history. We have not seen a real export, so this has not been tried: check the dry run's column mapping first. Signatures never count as sign-offs here.
From eSign Signatures for Jira (Digital Rose): No import path. Its listing names a PDF archival snapshot report and an API, and says nothing about a CSV export, so we have nothing to read. Keep the signed records in eSign.
Switching to Checklist Flow for Jira
#From HeroCoders Checklists
An alternative to HeroCoders Checklists for Jira: turn on its custom field sync, then move to Checklist Flow with one dry run and one import by JQL.
From Multiple Checklists (SolDevelo)
Leaving Multiple Checklists for Jira (SolDevelo)? Checklist Flow reads its checklists in place: dry run, import by JQL, undo per run. Free up to 10 users.
From Smart Checklist Free
Smart Checklist Free for Jira loses support on 15 Dec 2026 (TitanApps). The dates, what changes, migration steps and your options: Pro, stay, or switch.
From Smart Checklist
An alternative to Smart Checklist for Jira: Checklist Flow, one dry run and one import by JQL, what moves, what does not, side by side and undo.
No import path yet, or not yet tried with real data:
From Didit Checklists: Checklist Flow cannot read Didit's checklist content. Copy each checklist's items and paste them into Import on the work item; plain lists and Markdown are understood.
From Native Checklists for Jira (Resilia Tech): No import yet. Its listing says each checklist is a Jira issue property, but we have not read that property's format, so Checklist Flow cannot read it. Copy the items as text and paste them into Import on the work item.
From Templify: Nothing to import. Templify's listing describes issue templates with default field values and issue hierarchies, not checklists, so there is no checklist data for Checklist Flow to read.
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.