• Products
  • Documentation
  • Resources

What product data is copied

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 Jira data is copied and what isn’t

 

What is copied

What isn’t copied

Users and groups

  • Users and groups from active directories including Jira Service Management agents

  • Portal-only customer accounts and Atlassian accounts with Customer role assigned

  • Customer organizations related to selected Jira Service Management projects

Customer organizations that are not related to selected Jira Service Management projects

Project types

  • Company-managed projects

  • Jira software and business projects that are team-managed

    • Any related issues, entities, and configurations

    • Any project references within company-managed projects

  • Archived projects

  • Jira Service Management team-managed projects

 

Project data

  • Workflow functions

    • Validator: permission, required field, field changed

    • Condition: permission, allow only reporter, user in group, user in project role, field value

    • Post function: update resolution field, update issue field

    • assign to current user

    • assign to reporter

    • assign to lead

    • Links to Jira issues, Confluence pages, and web pages.

       

  • Project avatars

  • Custom issue type icons

  • Custom field language translations

  • Workflow functions

    • Condition: subtask blocking

    • Post function: clear field value, copy value from other field, delegating, update issue custom field

  • Notification schemes (Supported for team-managed projects only. For company-managed projects, projects added to the default schemes in cloud)

  • Automation rules (including project-level automation rules). More about import and export Jira automation rules

  • Mail handlers

  • Remote link histories

 

Jira project data

  • Project details:

    • Name

    • Key

    • Project type

    • Project category

    • Description

    • Project lead

    • Default assignee

  • Project roles

  • Issue types

  • Issue type scheme

  • Issue type screen scheme

  • Workflow scheme

  • Field configuration scheme

  • Workflows (links to the migrated workflow scheme with status and transitions)

  • Screens

  • Screen schemes

  • Status category

  • Permission schemes

  • Issue security (level, scheme, permission)

  • Issue rank

  • Epics (epic link)

    • Epic name

    • Epic color

    • Epic status

    • Issue rank

  • Original Estimate

  • Remaining Estimate

  • Flagged

  • Components

  • Environment

  • Sprints

  • Versions (affects versions, fix versions)

-

Jira Service Management project data

  • Queues

  • Request types

  • Request type groups

  • Customer organizations

  • Customer organization user association

  • SLA calendars

  • SLA Time Metric configuration

  • Approvals

  • Customer notifications

  • Reports

  • CSAT setting

  • CSAT comment

  • Portal settings

  • Language support

  • Features

  • Knowledge base

  • Jira automation

  • Email settings

  • Assets

  • Services

  • Forms (and form data attached to issues)

  • On-call Schedule

  • Change calendar

  • Chat

  • Widget

  • External resources

  • Login message

  • Site-wide announcement

  • Customized look and feel for help center

  • Help center home page layout

  • Issue collector

  • Versions

  • People

Issue data

  • Summary

  • Description

  • Issue type

  • Status

  • Priority

  • Resolution

  • Labels

  • Reporter

  • Assignee

  • Due date

  • Subtasks

  • Some custom fields

    • Text

    • Date

    • Number

    • Time

    • Labels

    • URL

    • Select list (single choice)

    • Select list (multiple choice)

    • Checkbox

    • Radio button

    • User picker (single, multiple)

    • Single and multi-version picker

    • Group custom fields

    • Multi-line text

    • Date of first response

    • Environment

  • @mentions

  • Watchers and votes

  • Issue links (including link types)

  • Attachments (media, files)

  • Comments

  • Comments with security

  • Story points

  • Time spent

  • Issue history

  • Issue work log

Some custom fields

  • Select list (cascading)

  • Project picker

  • Affected services

  • Responders

  • Asset object

 

 

Jira Software Boards

  • Boards linked to more than one project

  • Filters linked to more than one project

  • Filters not linked to any boards

  • Boards linked to one project only

  • Boards

    • Name

    • Administrators

    • Filters and permissions

    • Share permission

    • Location

  • Advanced board settings

    • Column names and status mapping

    • Swimlanes

    • Time statistic/estimation

    • Quick filters

    • Card colors

    • Subquery

  • Boards

    • Shared permission

 

Entities and permissions

Remote links

  • Global permissions

  • General configuration (e.g., timezone, language)

  • Dashboards

  • Boards with non-existent/deleted filters won't be migrated

  • Confluence links (links in destination site will continue to link to source site)

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

  • Scenarios

  • Unsaved changes from auto-scheduler

  • Saved Views

What Confluence data is copied and what isn’t

 

What is copied

What isn’t copied

Users and groups

  • 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)

  • Active spaces

  • Personal spaces

  • Archived spaces

-

Confluence space data

  • Space details:

    • Space logo

    • Name

    • Key

    • Categories

    • Description

  • Sidebar settings

  • Content status settings

  • Space permissions

  • Look and feel:

    • Themes

    • Space templates

    • Page layout (header and footer)

    • PDF export customizations

  • Pages & blogs (including archived items and items in the trash)

  • Analytics data

  • Space shortcuts

  • Related pages settings

  • Whiteboards

  •  Databases

Page/blog data

  • Title

  • Content (including history)

  • Labels

  • Restrictions

  • Comments (including history)

  • Attachments (including history)

  • Likes

  • Page restrictions

  • Links are migrated, but some links in destination site will continue to link to source site

  • Default page statuses

  • Stock Unsplash images in headers

  • Watched pages

  • Analytics data

  • Reactions

  • Custom uploaded images in headers

  • Custom emojis (page and in title)

  • Public links (these will need to be newly generated)

Entities and permissions

-

  • Site level settings

    • Configuration

      • General configuration (e.g., timezone, language)

      • Further configuration

      • Languages

      • Shortcut links

      • Global templates

      • Code macro administration

    • Security

      • Security configuration

      • Global permissions

      • Default space permissions

    • Look and Feel

      • Themes

      • Colour scheme

      • Site logo and favicon

      • Header and footer

      • Default space logo

    • Administration

      • Audit log

      • Application links

      • Application navigator

User profiles

-

  • User avatars (users will need to update their avatars after data copy)

  • Passwords (unless you've set up SSO, users will need to reset their passwords after data copy)

Apps

-

  • Apps and app data stored with the vendor (to copy app data, contact the respective Marketplace Partner)

  • Team Calendars

 

Still need help?

The Atlassian Community is here for you.