Question
Can projects and issues signed with eSign be migrated (exported/imported) between separate Atlassian cloud sites.
Note: In June 2025 eSign added a Copy Signatures utility that can assist with moving signature data between sites. See Copy Signatures - Transferring between Cloud Sites .
Answer
Yes, though there are some considerations to preserve data integrity. See below.
Signature Data Storage
eSign for Jira signature data is stored as content properties on the project issues within the Atlassian cloud site. No signature data is stored externally by the eSign servers.
The eSign signature data contains an embedded digital signature for integrity verification and compliance purposes. Any changes to the data will be detected and display a warning message.
The PDF Signature Archive file, optionally attached to the issue after finalizing, is a regular PDF file attachment. These files will be migrated with all other issue attachments.
Signature Data Integrity Warnings
-
If issue keys are renamed during the import the signature verification warning will be raised.
-
The Atlassian import tool may present an option to “Fix URL’s” on import. If this is used the tool will search and replace the old cloud URL with the new cloud URL in all Jira data, including the signature meta data. Do not enable this option if you want to preserve signature integrity.
When a data integrity problem is detected, the warning message is displayed in the Signature panel above the historic (and migrated) signatures. No additional signatures can be captured without an admin reset of the signature data to restore integrity.
Migration Tools
eSign Copy Signatures
In June 2025 eSign added a Copy Signatures utility that can assist with moving signature data between sites. See Copy Signatures - Transferring between Cloud Sites .
Atlassian Cloud Backup/Restore
If Projects and Issues are exported from Site A and imported to Site B, the following behavior would be expected.
-
If the Atlassian issue import includes issue properties then the imported issues will display the pre-existing signatures visible on the page.
-
The PDF Signature Archive attachments would continue to be accessible on the imported issues and contain the history of signatures from the old site.
-
Active signature data verification should still be valid provided the Issue Key did not change. If the Issue Key did change, then an administration “clear signature data” function will need to be performed before capturing additional signatures.
-
eSign Project Settings are similarly stored as project properties within Jira so migrating a project should bring across the settings. Any imported settings should be reviewed, as references to custom fields, groups, roles, etc may be different in the new site.
Atlassian Copy Product Data - Not Recommended
At this time (June 2025), the Atlassian Copy Product Data feature does not copy all issue data. See https://support.atlassian.com/organization-administration/docs/what-product-data-is-copied/ As it does not copy issue properties this means signature data will not be copied with this tool. Only the PDF Signature Archive (attachment) would be migrated with this tool.
Deep Clone for Jira by Code 49
The third party app, Deep Clone for Jira ( https://marketplace.atlassian.com/apps/1218652/deep-clone-for-jira ) does have the ability to migrate issues between Atlassian cloud sites/instances, including issue properties. This tool can be used to move signed issues.
Please connect with the vendor (Code 49) for questions and support on this tool.
Additional Notes
-
Enable the PDF Signature Archive option (in App Settings) and Finalize all issues with signatures prior to export/import. This will generate and attach the Signature Archive as a PDF Attachment on the issue, providing a permanent immutable record of the signatures (on the original site).
-
eSign for Jira also includes a CSV Signature import feature, where a CSV file can be used as a source to import legacy signatures to existing issues. See Signature Import and Migration for more information.