Switching · Attestation Flow
Switching from Read & Confirm (MiddleCore) to Attestation Flow
Attestation Flow for Confluence 3.1.0 is the production version (30 October 2026). Last updated 20 October 2026. On the Atlassian Marketplace.
Export, paste, dry run, import, page by page. The switch starts from the export file that Read & Confirm (MiddleCore) gives you. The dry run writes nothing, and every import run can be undone.
What moves
#- Each page's export (Name, Status, Version, Confirmed At), as labelled imported history on that page. Built from MiddleCore's documentation; not yet tried with a real export.
- Names are matched to the page's required readers; add "name => account ID" lines for anyone else.
What does not move
#- Confirmations of pages you do not import: the export has no page column, so each page is imported on its own.
Before you start
#Export the confirmations of the page from Read & Confirm.
How
#On the page, open the Attestation Flow box, Import from another app, choose Read & Confirm (MiddleCore), paste the rows, click Dry run, then Import; Import appears only after a dry run of the same text.
Run both side by side
#Attestation Flow never changes Read & Confirm. Try one space first. Imported records appear on the page under Imported history, marked "Imported, not verified by Attestation Flow", with the app, the run, who imported them and when. They are history, not acknowledgements: readers still confirm the page in Attestation Flow, imported records carry no checksum or meaning and never carry over a minor edit, and the Attestation Flow audit chain records that the import happened, not the confirmations themselves.
Roll back
#Every import run can be undone; importing the same file again adds nothing twice.
Who can do it
#The requirement's owner on that page (a Confluence administrator can use the space page instead).
More on Attestation Flow: documentation, comparison with other apps.
Common questions
#Does the import change Read & Confirm (MiddleCore)?
No. Attestation Flow only reads what Read & Confirm (MiddleCore) 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 confirmations count as acknowledgements?
No. They are kept as labelled imported history and never count as an acknowledgement in Attestation Flow.
Who can run the switch?
The requirement's owner on that page (a Confluence administrator can use the space page instead).
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.