Switching · Approval Flow
Switching from Herzum Approval to Approval Flow
Approval Flow for Jira 3.0.0 is the production version (30 October 2026). Last updated 1 November 2026. On the Atlassian Marketplace.
Export, paste, dry run, import. The switch starts from the export file that Herzum Approval gives you. The dry run writes nothing, and every import run can be undone.
What moves
#- Your approval history as Herzum exports it: in Herzum's History Management, filter what you need and click Download CSV.
- Approval Flow 2.10.0 does not read the dates of this export: Herzum names the column "Action Date" and writes dates such as "17/October/2026 21:34 GMT+2", which this version does not recognise, so imported decisions carry no time.
- The dry run shows which column became the person and the decision, and counts anything that will not fit: work items that no longer exist or that you cannot open, people the site cannot match, dates it cannot read.
What does not move
#- Herzum's approval configuration: it is not in the History Management export. Set up who must approve with Approval Flow's policies and rules.
Before you start
#Export the CSV from Herzum. On 17 October 2026 we read a real History Management export from our own test site with a test build; that test found the date problem described above. A paste can hold up to 4 MB and 20,000 rows; split bigger exports, nothing is imported twice.
How
#In Jira settings, Apps, open Switch to Approval Flow (or the Migrate tab of Approval Flow settings), choose In an exported file (CSV) and Herzum Approval, paste the file, click Dry run, then Import.
Optional: Also carry over pending approvals turns the people still pending into a Required Approval Flow requirement on that work item, so in-flight approvals continue here. With All of the pending people, every one of them must sign; the dry run says how many requirements it will create.
Run both side by side
#Approval Flow never changes Herzum. Try one project first. Imported records appear on each work item under Imported history, marked "Imported, not verified by Approval Flow", with the app, the import run, who imported them and when. They are history, not sign-offs: they do not satisfy a requirement, the workflow gate, the Approval status field or the certificate, and the Approval Flow audit chain records that the import happened, not the decisions themselves.
Roll back
#Every import run can be undone from the same page. Importing the same data again adds nothing twice. Requirements created by carry-over stay after an undo, so in-flight approvals are not lost.
Who can do it
#Jira administrators, in every edition.
More on Approval Flow: documentation, comparison with other apps.
Common questions
#Does the import change Herzum Approval?
No. Approval Flow only reads what Herzum Approval 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.
Do imported approvals count as sign-offs?
No. They are kept as labelled imported history and never count as a sign-off, toward the workflow gate or in the approval certificate.
Who can run the switch?
Jira administrators, in every edition.
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.