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.
Before you start transferring Atlassian app data
Who can do this? |
When you add teams or reorganize your existing teams, you may need to transfer 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. What is an Atlassian organization?
Before you start transferring data, here are some of the things you should know.
Understand what source and destination means
You can transfer 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.
Check your permissions
For transfers using the existing experience, you must be an organization admin, an app admin, and a user of the apps you want to transfer data to and from. Give users admin permissions
After the units activation, the administration scope required for a supported transfer depends on its source and destination:
Transfer | Administration scope |
|---|---|
Within one unit | Organization admin, or unit admin of that unit. |
Between units in the same organization | Organization admin, or a unit admin who administers both source and destination units. |
Between organizations | The authorized administrators must provide the consent required by the supported transfer path. |
Add your Atlassian and Marketplace apps to your destination
Before you start transferring 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, contact the respective Marketplace Partner.
Data transfer in an organization with units
Supported cloud-to-cloud migration paths use units to determine eligibility. The service checks whether a transfer stays within the same unit or crosses the unit boundary.
Within a unit, users and groups are shared. When moving data across units, a user may need to be a member of the destination unit before they can access the transferred data.
Organization admins can initiate moves across any unit in the organization. Unit admins can only initiate moves for units they administer on both the source and destination units.
Before you start transferring data, confirm:
If the move is within one unit, across units, or to a different organization.
Transferring data to a different organization crosses unit boundaries and requires explicit consent from organization and unit admins in both the source and destination organizations.
You must confirm that your selected migration path supports Assets object schemas and objects. Other platform apps (like Rovo, Home, Teams, and Goals) don’t move with app data and must be planned separately.
Ensure the source and destination units have the same Atlassian and Marketplace apps to avoid data loss or broken links
Copy data from sandboxes to your production instances
We don’t recommend copying data from sandboxes to your production instances using the Data transfer 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 Data transfer feature, we create duplicate configurations.
Check copy limits
If your organization has activated Units, enforced copy limits apply to your transfer selection. Review the copy limits and support options before planning your transfer.
Other considerations
You may also want to understand:
Was this helpful?
Still need help?
The Atlassian Community is here for you.