Switching · Attestation Flow
Switching from eSign to Attestation Flow
Attestation Flow for Confluence 3.1.0 is the production version (30 October 2026). Last updated 29 October 2026. On the Atlassian Marketplace.
One dry run and one import, read from eSign's page data in the space. The other app is only read, never changed, the dry run writes nothing, and every import run can be undone.
What moves
#- Who signed each page and who is still invited, read from eSign's own page data on every page of the space you choose.
- eSign does not expose the time or page version of each signature there, so those stay empty and the record says so.
What does not move
#- eSign's PDF archives: they stay attached to your pages.
- eSign's signature verification.
Before you start
#Nothing to export: the data is already on the pages.
How
#In the space, open Attestation Flow - Space report, tab Import, choose eSign (read in place), click Dry run, then Import. A space without eSign data finds zero pages, without an error.
Optional: Also carry over who must read gives a page with no Attestation Flow requirement one naming the matched people. A page that already has a requirement is left alone.
Run both side by side
#Attestation Flow never changes eSign. 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
#Confluence administrators.
More on Attestation Flow: documentation, comparison with other apps.
Common questions
#Does the import change eSign?
No. Attestation Flow only reads what eSign 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?
Confluence administrators.
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.