Moving data between Atlassian Government Cloud sites

You can move data between existing Atlassian Government Cloud sites by using our data transfer feature. Note there are some limitations in regards to data parity.


Plan your migration to Atlassian Government Cloud

Before you begin, review the key considerations for migrating your apps to Atlassian Government Cloud apps.

Attributes

Details

Available apps

Eligibility

User tiers

  • Jira and Confluence: 201+ users

  • Jira Service Management: 26+ agents

Academic discounts

Contact us to check eligibility

Community discounts

Not applicable

Atlassian app integrations

  • We evaluate integrations for FedRAMP compliance before making them available.

  • To request a specific integration, contact your Carahsoft or Atlassian sales contact.

Webhooks

Assess the security of any external URLs you configure for webhooks.

Data security policies

See Apply a default configuration to a policy control

Security and compliance

See Understand Government Cloud security and compliance

Atlassian Government Cloud operates under a shared responsibility model for FedRAMP Moderate. More about the shared responsibility model


Migration tooling

Data transfer feature

To move data between Atlassian Government Cloud sites, you’ll use our data transfer feature that you might know from Atlassian Cloud migrations. The data transfer works in a similar way, however there are a few items that can’t be migrated, as shown in the data parity table below.

Learn more about data transfer

What data is and isn’t migrated

The data transfer feature supports migrating the majority of entities and configuration items, however there are still things we can’t migrate. Review the list of what’s supported so you know what to expect and what needs to be left behind.

What Jira data is copied

What Confluence data is copied


Limitations and data migration parity

Limitations related to migrations or migrated data.

Type

Details

✅ Core products

You can migrate our core products:

  • Jira

  • Jira Service Management

  • Confluence

✅ Users and group

Full parity with regular data transfer:

What data is copied

⚠️ Jira data

In addition to items listed in What Jira data is copied, the following data isn’t migrated:

❌ Dashboards

⚠️ Jira Service Management data

In addition to items listed in What Jira data is copied, the following data isn’t migrated:

❌ Knowledge base

❌ Help center

❌ Virtual agent

❌ Jira Service Management widget

❌ Assets

✅ Confluence data

Full parity with regular data transfer:

What Confluence data is copied

⚠️ Marketplace app data

The number of available Marketplace apps is limited. For supported apps (view the list), the data is not migrated using the data transfer feature. You need to check with the Marketplace partner if a manual migration pathway is available.


Key differences

Key differences across the migration journey.

Coordinating migrations with Support

Your migration will be coordinated and supported by Atlassian Support and Migration teams. If you’re planning to move, make sure to notify them about your plans. You will need to get your new site provisioned by us.

Provisioning sites and apps

New site with Jira or Confluence that you want to move your data to need to be provisioned by Atlassian. In Atlassian Government Cloud, you’re unable to provision sites and apps yourself. See the page below for more details on how to request new apps:

Add users and apps to Atlassian Government Cloud subscriptions

Still need help?

The Atlassian Community is here for you.