Learn about Atlassian organizations
New to administering Atlassian cloud products? Learn about Atlassian organizations and what it means to be an organization admin.
We plan to enable the copying of all boards, filters and plans in Jira in phases by September 2024. You will see it as a supported feature within the next few weeks.
Copy Jira or Confluence data from one instance of your cloud product to another without overwriting any existing data. You can copy data to a new or an existing site within the same organization or in a different organization.
| What is copied | What isn’t copied |
---|---|---|
Users and groups |
| Customer organizations that are not related to selected Jira Service Management projects |
Project types |
|
|
Project data |
|
|
Jira project data |
| - |
Jira Service Management project data |
|
|
Issue data |
| Some custom fields
|
Jira Software Boards |
|
|
Entities and permissions | Remote links |
|
Apps | - | Apps and app data. To migrate app data, contact the respective Marketplace Partner. |
Plans in Jira | Plans in Jira and plan in Jira data |
|
| What is copied | What isn’t copied |
---|---|---|
Users and groups |
| Any permissions settings (space or page) associated with groups will be lost during import unless a group with the same name already exists in the destination site. To maintain your groups' permissions settings, make sure all your groups have a corresponding group with the same name that already exists in the destination site before importing the space. An easy way to do this is to first import users and groups, then import any spaces. |
Space types (if selected) |
| - |
Confluence space data |
|
|
Page/blog data |
|
|
Entities and permissions | - |
|
User profiles | - |
|
Apps | - |
|
Was this helpful?