Introduction to third-party migration agreement

Thank you for being a part of the early access program. This community site allows you to provide feedback through page or inline commenting. We will use your comments to improve our product and documentation. Anybody on the internet can view your comments. To know your rights and responsibilities as a customer of our cloud products, read our Atlassian Cloud Terms of Service.

This page goes into detail about the following:

  • app migration process and backend

  • role of the Marketplace Partner (vendor)

  • types of data the Marketplace Partner can access

  • how the ‘Agree to app migration’ page works

When an app migration is performed, the migration moves the app data from each server app to its cloud version on your cloud site. This can take place alongside a migration of a Confluence or Jira instance, or can be run alone.

The Marketplace Partner (vendor) that built each app has created a migration pathway to move the data, via the Atlassian platform known as the App migration platform. The diagram below demonstrates how the migration itself works.

It is very important to understand that the Marketplace Partner (vendor) who developed a particular app, will be performing the data migration. Atlassian has developed the App migration platform to be the conduit between the Marketplace Partner and yourself as the app user.

Data security and allowed access scopes

The App migration platform allows server apps to export your app data to cloud, and to access Confluence and Jira mappings. The access is very tightly controlled and restricted to a list of data types, or access scopes.

  • The Marketplace Partners who built the apps installed on your server instance, have documented the access scopes required to migrate the apps.

  • These access scopes are surfaced in the Cloud Migration Assistant so that you can consent to the Marketplace Partner accessing this data.

  • Marketplace Partners can only access this data for five days after a migration is commenced.

You can find the specific information and list of access scopes on the Security and Access scopes pages in Atlassian’s developer documentation.

For more context, read the data privacy guidelines for developers that Atlassian recommends.

Agreeing to a migration

Each Marketplace Partner app has different access scopes.

You must review and agree to each Marketplace Partner agreement before they can access your data to migrate.

Atlassian’s Cloud Terms of Service and Privacy Policy do not apply to any of the apps installed in your cloud site. Instead, each Marketplace Partner (previously known as app vendors) writes their own privacy policy and terms of use.

You must also review and agree to each Marketplace Partner privacy policy and terms of use before they can access your data to migrate.

Agreeing in the migration assistant

The following image shows the agreement screen included in the migration assistant for this EAP.

Some quick notes on this table:

  • Atlassian’s Cloud Terms of Service and Privacy Policy do not apply to any apps installed on your cloud site.

  • By installing apps on your cloud site, you agree to the Atlassian Marketplace Terms of Use and the Marketplace Partners privacy policy and terms of use.

  • You should review a privacy policy in detail before installing an app in your cloud site. 

  • You can find the privacy policy and terms of use for each app on the app listing in Atlassian Marketplace.

App migration agreement status messages

Status message

What you need to know

Status message

What you need to know

You have agreed to third-party automated app data migration for this app.

This app is ready to be migrated.

You must review and agree to this data migration policy, or your app data cannot be migrated.

As explained above, you need to review the supplied Policies and Terms of Service before this app is ready to be migrated.

The policy you agreed to have been updated. Review changes and agree again before your app data can be migrated.

If a Marketplace Partner makes any changes to their policy, you’ll need to review the policy again and agree. Otherwise your app data would be migrated under conditions you hadn’t agreed to.

This app does not require an app data migration to function on your cloud site. Install it, migrate your core data and you’re ready to go.

This means there is no data contained in the app to be migrated from server to cloud. You can just install the cloud version on your cloud site.

An automated migration path between alternative app selections is not available. Contact the app vendor for migration support.

If you chose an alternative app on the app assessment table to replace an app you have on your server, there can’t be a migration path. You’ll need to contact both Marketplace Partners if you want to migrate data from one app to another .

This app does not have an automated migration path. Contact the app vendor for migration support.

The vendor has not yet built a migration path for their apps. You should still contact the vendor, as they are likely have a manual migration process that you can follow.

This app version does not support app data migrations. You must update your server app version in order to agree to the relevant app migration policy.

The app you have installed supports an app data migration, but you need to update your server app to a version that supports app data migration.

 

When you click View policy, you will see a modal with the following details on it:

The modal above lists the following:

  • access scope of that particular Marketplace Partner

  • all the information they will need to access/see in order to migrate this app

 

There are three links in each modal:

  • Atlassian Marketplace Terms of Use (the same for each app)

  • The Marketplace Partner Privacy Policy (unique to each app)

  • The Marketplace Partner Terms of Use (unique to each app)

We strongly recommend you read each one, for each app.