Plan your Cloud to Atlassian Government Cloud migration
Check what your Atlassian Government Cloud migration will look like, what the limitations are, and how to prepare for your migration.
Overview of Atlassian Government Cloud
Learn about Atlassian Government Cloud, including feature availability, security and compliance, and the details of how Atlassian apps and user management works.
Manage Atlassian Government Cloud
Feature availability in Atlassian Government Cloud
Plan your migration
Before you begin, review the key considerations for migrating your apps to Atlassian Government Cloud.
Attributes | Details |
|---|---|
Available apps |
|
Eligibility |
|
User tiers |
|
Academic discounts | Contact us to check eligibility |
Community discounts | Not applicable |
Atlassian app integrations |
|
Webhooks | Assess the security of any external URLs you configure for webhooks. |
Data security policies | |
Security and compliance |
Atlassian Government Cloud operates under a shared responsibility model for FedRAMP Moderate. More about the shared responsibility model
Migration tooling
You can migrate data from Atlassian Cloud to Atlassian Government Cloud through a self-serve path within Atlassian Administration.
Read how to migrate to Atlassian Government Cloud
What data is and isn’t migrated
We support 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 migrated (including Jira Service Management)
What Confluence data is migrated
Limitations and data migration parity
Limitations related to migrations or migrated data.
Type | Details |
|---|---|
⚠️ Products | The following Atlassian apps can be migrated:
|
✅ Users and groups | Users and groups are migrated without any limitations. |
⚠️ Ability to migrate selective data | All your data from your Atlassian Cloud environment will be migrated into your Atlassian Government Cloud environment. However, you cannot selectively move specific data entities, such as specific spaces or users. To move selected entities, first migrate them to another Atlassian Cloud environment, then to your Atlassian Government Cloud environment. |
⚠️ Space data | The majority of data related to projects or spaces is migrated, however you should review the list of data parity as there is a number of items that aren’t supported. How important they are will depend on your usage: |
⚠️ Marketplace app data | The number of available Marketplace apps is limited. Browse the Atlassian Government Cloud collection Supported apps can’t be migrated automatically. You need to check with the Marketplace partner if a manual migration pathway is available. |
⚠️ Data recovery | If the migration fails, Jira data can be automatically rolled back from the Atlassian Government Cloud environment. For Confluence, a manual cleanup is required before you attempt to migrate again. |
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 environment provisioned by us.
Provisioning organizations and sites
Your Atlassian Government Cloud environment, including organization, sites, and Atlassian apps, such as Jira or Confluence, are provisioned by Atlassian when you start the onboarding. You’re unable to provision apps yourself, but you can request new apps, if needed.
For details, see Get started with Atlassian Government Cloud.
One-way data transfer
Due to security and compliance restrictions, you can only transfer data from Atlassian Cloud to Atlassian Government Cloud. You can’t move data outside of your Atlassian Government Cloud environment.
Destination must be reset before migration
To prepare for migration, the Atlassian Government Cloud environment must be reset before data can be migrated from Atlassian Cloud. The Jira site in Atlassian Government Cloud will be automatically reset when the migration begins. Ensure that there are no existing spaces in the destination’s Confluence site before beginning the migration.
Identity and user management
An identity provider is required as single sign-on is the only way for users to log in. Your identity provider will also be pre-configured (connecting IdP, verifying domain, configuring single-sign on) by Atlassian based on the details you provide. Google Workspace is not supported as an identity provider in Atlassian Government Cloud.
For details on what’s needed to set up your identity and user management, see Get access to the Atlassian Government Cloud environment.
Marketplace apps
The number of Marketplace apps is still limited, as Marketplace partners need to build a version of their app specifically for Atlassian Government Cloud. You can check if your app is supported by viewing available hosting types on Atlassian Marketplace (e.g. Cloud, Data Center, Atlassian Government Cloud). Alternatively, you can review the list of available apps in Manage apps for Atlassian Government Cloud.
Licensing and Atlassian Guard features
Atlassian Government Cloud has a separate subscription plan from Free, Standard, Premium, or Enterprise that you might know from Atlassian Cloud. Additionally, the Atlassian Guard subscription (required for Enterprise features, such as connecting identity providers) is not required, because the key Enterprise features are already included in your Atlassian Government Cloud subscription.
Was this helpful?