Moving your Marketplace apps data to another location

An app, sometimes called an add-on or plugin, is an installable component that supplements or enhances the functionality of a product, such as Jira, Jira Service Management, and Confluence. An app is always linked, associated, or subscribed to a product. You can find all the available apps in the Atlassian Marketplace.

With data residency, you can control where your data is stored. Only some Marketplace apps support data residency.

Currently, we support a combined move of a product and some of its installed apps. This means that while we're moving your product to its new location, some of its installed apps will move automatically. However, some apps will have to be moved separately after the product has moved to the preferred data residency location.

This page provides detailed information on how data residency for Marketplace apps works.

Before you request a data residency move for apps, you should understand the different app statuses.

What are app statuses?

Many apps on the Marketplace offer the ability to pin and move data between locations. Currently, we have four app statuses:

• Pinned

• Eligible

• Not eligible

• No action available

Pinned

These apps are already pinned to the product location and store data in the same location. In some cases, the apps can also be pinned during installation; they don't need to be moved.
For example, say you have Confluence pinned to the USA location and install a new app supporting data pinning to the USA. If the app is installed after the product is pinned, it is also moved to the USA location. This app would show up in the Pinned tab.

Eligible

For an app to be eligible for a data residency move, it must support the following:

• data pinning in the same location as the product

• data movement between locations

• not currently pinned to the same location as the product

If the app supports only one or none of the above, then the app is considered to be not eligible. Only eligible apps can be moved to their product location.

Not eligible

If you have apps that are not eligible for data residency move, it can be because:

• they don't support data residency in the same location as the product

• they currently don't support data residency

Even when your apps are marked as not eligible, the app data stored within Atlassian products or systems may have moved to the selected location. However, the app will remain classified as not eligible because only a portion of the app data could be moved.

No action available

If you have apps that have no action available for a data residency move, it’s because some app partners declare that their apps don't need to be pinned or moved as:

• their apps exclusively store data within the Atlassian product or

• their apps don't store any data

How we manage data residency moves for Marketplace apps

We support a combined move of a product and some of its installed apps. While we're moving your product to its new location, some of its installed apps will move automatically. This means that some of the apps that support a data residency move will be moved along with the product. However, some apps will have to be moved separately after the product has moved to the preferred data residency location. There may also be apps that won't be able to move at all since they don't support data residency. Learn more about app statuses

When you request that an app be pinned to a new location:

• Some apps' data will move along with the product. Any associated apps installed or updated in the future that support automatic pinning will also be pinned to the selected location.

• Some apps' data will have to be moved separately after the product move is complete. These requests are handled by third-party Marketplace partners who operate the app. Atlassian will forward your data residency move request to the Marketplace partner responsible for moving the app data. Learn about how to move apps

While Atlassian supports multiple locations, each third-party Marketplace partner makes decisions that can impact the locations they support for the apps they build and operate. We recommend speaking to app partners and reviewing their documentation to understand how they help data residency. The third-party Marketplace partner must be onboarded on the developer platform and provide app data residency to support an app data residency move.

Request a data residency move for apps

To request a data residency move for apps:

1. Go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Security > Data residency.

3. In the data residency table, select View details.

4. Select the Eligible tab.

5. If you have eligible apps, select Move apps.

6. Review information about the steps involved in moving your eligible apps. Select Next.

7. Review the apps. Select Next.

8. Select the 24-hour move window. Select Next.

9. Review your app data residency move details. Select Submit request.

Some apps might already be pinned to your selected region, even if you haven’t explicitly chosen that region. Those apps might have been pinned during installation or pinned there to optimize performance. You can move your app data to another location of your choice, provided the Marketplace apps support data residency and your preferred location.

How does a data residency move for Marketplace apps affect your product?

While the Marketplace partners are moving your eligible app data to the requested location, the product will be offline, and your users won't be able to access it. This move can be scheduled up to 3 days in advance, and it takes up to 24 hours for all apps to move. You should, however, plan for your product to be offline for 24 hours during an app move.

When you request a data residency move for apps, you select a 24-hour move window. We provide this 24-hour window to our Marketplace partners to move the app. They will plan to complete your move during this 24-hour window, but we can't guarantee the exact time of the move since it depends on the Marketplace partner. As soon as the move is complete, your product and its apps will be back online.

Cancel a data residency move for apps

You can cancel a data residency move as long the status is MOVE SCHEDULED. You can’t cancel a move after the status has changed to MOVE IN PROGRESS.

To cancel a data residency move:

1. Go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Security > Data residency.

3. Find the product in the data residency table and select View details.

4. Check the Eligible tab.

5. Find the app for which you want to cancel the data residency move, and select Cancel move.

What if the apps fail to move to a location?

All eligible apps will move together in a single app data residency move. Once the app move is complete, the status for the apps that have successfully moved will change from ELIGIBLE to PINNED.

Sometimes, you may notice that an app has failed to move to the new location. This is when you will see the status as PROBLEM OCCURRED.

You can try to move the app again by scheduling another app data residency move. However, if the problem persists, we recommend that you contact the app vendor to understand the reason for the failure and support.

To contact the app vendor:

1. Go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Security > Data residency.

3. Select View details for the product you want to know more about.

4. Select the Eligible tab.

5. Select the information icon next to the PROBLEM OCCURRED status in the table. The app vendor's available contact details will appear in a dialog.

6. Select Contact the app vendor. It will take you to the support page for the app’s listing on Atlassian Marketplace.

During a data residency move for your apps, you will see the following statuses in the Eligible tab:

• MOVE IN PROGRESS indicates that the app data is being moved

• PROBLEM OCCURRED indicates that the app data failed to move; this status only applies until the move is completed. Apps that have failed to move will be eligible to move again once the move in progress is completed. If this problem persists, contact the app vendor.

Email notifications

Once you initiate the apps migration, you will receive an email when the move:

• is scheduled

• is in progress

• is completed

• is cancelled

• has failed