Rate this page:
This page explains the security features and guidelines of the app migration platform that can protect app data from unauthorized access, malicious or accidental changes.
The security of customer data is crucial to ensure that your customers can use your apps with confidence. The app data you export and the mappings you access can contain Personally Identifiable Information (PII) which is subject to 'Right to erasure' through GDPR.
It is best practice to only export the app data you need for migration.
Use access scopes to inform Jira or Confluence admin users about the type of mappings, product data, and app data that you choose to migrate. The access scopes you declare will be visible to the admin user on the user interface of the Jira or Confluence Cloud Migration Assistant. Your app data migration can continue if the admin user consents to the access scopes that you declare.
There are two types of access scopes:
Product data and app data access scopes declare the type of data that you choose to migrate to the Atlassian secure cloud storage.
Migration tracing access scopes declare the type of mappings that your server and/or cloud app will access.
Read our docs for information on declaring access scopes.
In order to comply with user privacy requirements, we do not recommend storing the export app data or mapping file/s for longer than needed.
If you choose to download the exported data from cloud storage, you must (at a minimum) follow guidelines for user personal data reporting to receive notifications for 'Right to erasure' requests during the migration.
In order to meet security and compliance requirements, we have placed the following limits on accessing data and mappings exported to the cloud storage location:
The app migration platform will delete all the exported app data after 12 days and user mappings after 14 days once you receive the above notifications.
Rate this page: