Understand how copying affects your billing
When you copy data, you may get billed depending on the number of users you migrate and your plan on the destination.
Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change
Who can do this? |
When you add teams or reorganize your existing teams, you may need to move your data from one instance of your Jira or Confluence Cloud to another. You can move users, projects, spaces, and related data within or across organizations. Learn more about Atlassian organizations
Before you start copying data, here are some of the things you should know.
You can copy data from one instance of Jira or Confluence, known as the source, to another instance, known as the destination. The destination can be a new instance or an instance with existing data.
You need to be an organization admin and a app admin to copy data between instances of your app within that organization. To copy data to a different organization, you must be an organization admin and an app admin for both organizations. Learn more about admin permissions
Before you start copying data, make sure your source and destination has the same Atlassian and Marketplace apps. We don’t migrate marketplace app data yet. However, to avoid loss of data and to accurately link your data, you need to have the same marketplace apps on both source and destination.
To migrate marketplace app data, you’ll need to contact the respective Marketplace Partner.
We don’t recommend copying data from sandboxes to your production instances using the Copy app data feature. When you copy data from a production instance to a sandbox, we copy configurations such as custom fields. When you copy data back from the sandbox to the production instance using the Copy app data feature, we create duplicate configurations.
You may also want to understand:
Was this helpful?