Learn about security solutions and standards
Care about security? We do too. Learn what Atlassian does and what you can do too.
Move product data to another location
If a product shows COMING SOON on the data residency overview, it means self-serve is unavailable for products with more than 2 hours of downtime on Standard and Premium plans. We're working to offer this option, but if you have urgent needs, contact support.
Check if your products can be data resident. Go to admin.atlassian.com > Security > Data residency.
This feature is available for Jira Software, Jira Service Management, and Confluence with Enterprise, Premium, and Standard plans. It’s also available for Jira Work Management with Standard and Premium plans.
If data residency is available for your product, you can request to have your in-scope product data moved to a new location and pinned there so it’s held in place. You may need to do this to meet company data requirements. Or if you work in a regulated industry like finance, government, or healthcare, this may be a necessity for operating in a cloud environment.
Before you request a data residency move, you should understand how the move will affect your product and how we’ll manage it.
How a data residency move affects your product
Before requesting a data residency move, you should know that for:
All products – your product will be offline
While we’re moving your product to its new location, it will be offline and your users won’t be able to access it. This process takes around two to four hours, depending on the size and type of your data. You should, however, plan for your product to be offline for up to 24 hours.
This is due to how we schedule data residency moves. When you request a move, you select a 24-hour move window. We’ll start and finish your move during this time, but we cannot say exactly when. So you can follow our progress, we’ll email you when your move starts, and when it’s finished and your product is back online.
All products – linked sandboxes won’t be moved
When you create a sandbox, we automatically host it in the same location as the product that it's linked to. For example, if you create a sandbox for a product that’s pinned to the US location, we’ll pin your sandbox to the same location.
We don’t, however, move sandboxes with their linked product. For example, if you move the product to the EU location, we won’t move the linked sandbox and it will remain pinned to the US location. If you want to move the sandbox to the EU location, you’ll need to request a separate move.
All products – Marketplace apps won't move
While we're moving your product to its new location, its subscribed apps won't move automatically. We don't support a combined move of a product and its subscribed apps. As a result, apps that support data residency move have to be migrated and pinned separately from their product. The product data should move to a data residency location, then only you can request to move its app data to the same location. Learn more about data residency for Marketplace app.
Both product and its apps will be offline, during the data residency move for product.
Jira – products on the same site URL will all be moved together
The products in the Jira Cloud family are all built on the Jira platform. As a result, we move all Jira Cloud products on the same site URL together. If you have Jira Software Enterprise, Jira Service Management, and Jira Work Management on the same site URL:
moving one of these products will also move the other two products to the same location
all three products will be offline during the data residency move
all three products will be pinned to the new location when the move is finished
If you use Jira Service Management, you should note that while it's offline during a move your users will still be able to access features powered by Opsgenie as they’re not part of the Jira platform.
Jira – sandboxes on the same site URL will all be offline
When you move a Jira Cloud product sandbox, all your Jira Cloud product sandboxes on the same site URL will experience downtime. This is due to how the products in this family are all built on the same platform. Learn more about sandboxes
Confluence – changes made in editing mode won’t be saved
During a data residency move, while Confluence is offline, changes your users make to pages they have open in editing mode won’t be saved.
Confluence – search won’t work temporarily after a move
After a data residency move, when Confluence comes back online, it will be re-indexed. While this is happening, search won’t be fully operational and it may not function as expected. Re-indexing can take a few hours, but may take up to three days, depending on the size of your product data.
Data residency isn't available for the audit log
When you’re on the Cloud enterprise plan, we store your user-created activity in the audit log. However data residency isn’t available for this activity. If you’d like to exclude user-created activity from the audit log, update your activity settings in the audit log. Learn more about audit logs
Request a data residency move
Data residency moves must be requested at least three days in advance.
If data residency is available for your product, you can request for it to be moved to one of our available locations and pinned there.
To request a data residency move:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Data residency.
In the data residency table, select Request move.
This will open the request workflow where you can:
select the new location where you’d like your in-scope product data to be pinned and held in place
enter the 24-hour window when you’d like us to complete your move
Before you request a data residency move, you should understand how a data residency move affects your product.
How we manage your data residency move
When you request a data residency move, we gather information about your product, including the size of your product data. We do this to help us plan your move and make sure it goes smoothly.
If you have a small amount of product data, we’ll set up your move to run automatically. However, if you have a large amount of product data, our Support team will manage your data residency move. Throughout the move, they’ll communicate with you via a support ticket that you can access through the data residency page. We’ll let you know if our Support team is going to manage your move in the request workflow.
Regardless of how we manage your data residency move, you can check on its status on the Data residency page. To keep you up to date, we’ll also email you when the status of your move changes, including when your move starts, and when it’s finished and your product is back online.
How we move your product data
During a data residency move, we:
Create a copy of your product data in your chosen location.
Verify that the product data in the two locations match.
Delete the source product data in the original location.
We only delete your source product data content once we have confirmed that your product content is in your chosen location.
As for attachments, when a product is moved to a new location, its files stay attached to the page or ticket they were originally uploaded to. They won’t, however, be visible from the in-product media picker pop-up.
New in-product notifications are also pinned in the destination location, and old in-product notifications stay in the original location for up to 30 days.
Cancel a data residency move
You can cancel a data residency move as long as its status isn’t MOVE IN PROGRESS.
To cancel a data residency move:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Data residency.
Find the product in the data residency table.
Go to the Actions column and select Cancel move.
When you do this, the product’s status will change to CANCELING MOVE. After we cancel the move, this status will be replaced with the current AWS region that the product is in. We’ll also send you an email to confirm that your move has been cancelled.
Was this helpful?