Learn about migrating Data Center to Atlassian Government Cloud
Check what your Atlassian Government Cloud migration will look like, what are the limitations, and how to get ready for your migration.
Overview
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
Migration tooling and strategy
Jira and Confluence migration assistants
During migration, you’ll use our migration tooling – Jira and Confluence migration assistants. The assistants not only move the data to Atlassian Government Cloud, but also include features that make sure your data can be moved, for example user assessments.
What is Jira Cloud Migration Assistant?
What is Confluence Cloud Migration Assistant?
Migration strategy: Lift and shift
By default, you’ll follow the lift and shift strategy, migrating all relevant projects or spaces simultaneously, rather than in phases. This approach minimizes manual post-migration cleanup and prevents issues like configuration drift or duplicate entities. However, for complex instances, the migration team may recommend a phased approach.
Learn more about the lift and shift strategy
What data is and isn’t migrated
The migration assistants 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 is migrated for Confluence
Migration planning and support
Your migration will be supported and coordinated by our Support and Migration teams. This includes going through the following migration phases with our guidance:
Assess: Assessing your footprint, dataset, and migration needs.
Plan: Planning the migration strategy, scope, and requirements.
Prep: Preparing your environment, including data cleanup and pre-migration checklists.
Test: Testing your migration and conducting User Acceptance Testing (UAT).
Migrate: Running a production migration and validation.
Post-migration: Completing post-migration tasks, validation, cloud adoption.
For details on each phase and the teams involved, see:
What your migration will look like
Limitations and data migration parity
Limitations related to migrations or migrated data.
Type | Details |
|---|---|
✅ Core products | You can migrate our core Data Center products:
|
✅ Users and groups | Full parity with regular migrations. |
✅ Project or space data | Full parity with regular migrations. |
❌ Assets from Jira Service Management | The key difference is lack of support for migrating Assets from Jira Service Management, which also applies to regular migrations. Check the roadmap below to see the est. release date. |
⚠️ Marketplace app data | The number of available Marketplace apps is limited, and they’re currently migrated manually. If your app is supported (view the list), you need to check with the Marketplace partner on possible migration paths. |
❌ Cloud Migration Trials | We don’t offer Cloud Migration Trials, you need to purchase an Atlassian Government Cloud subscription. |
For all differences, including configuration differences on the cloud side, see Differences in Atlassian Government Cloud migrations.
Roadmap and planned features
We’re working on improving the migration journey, especially when it comes to data parity.
Feature | Details | Est. release date |
|---|---|---|
Assets migration | Migration of Assets from Jira Service Management. | December, 2025 |
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. Our teams will get involved after you purchase Atlassian Government Cloud. and start onboarding. During this time, your new environment will be provisioned by Atlassian.
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.
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 provider. 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 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 on the page linked below.
For details, see Manage Marketplace apps for Atlassian Government apps.
Other differences
For all differences, including configuration differences on the cloud side, see Differences in Atlassian Government Cloud migrations.
Get started with your migration
Get started by joining Atlassian Government Cloud and provisioning your environment.
Get started with your migration to Atlassian Government Cloud
Was this helpful?