nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Data Center to AGC Migration

Tankem Williams

I recently completed a migration from Jira Data Center to Jira Cloud AGC using the Jira Cloud Migration Assistant(JCMA). The migration process is still ongoing, but overall it has gone smoothly. That said, not everything was perfect. Below is a summary of my experience, including both successes and challenges. I welcome any feedback or recommendations.

Discovery: The discovery phase follows the same approach as a standard migration to public Jira Cloud. There are no additional requirements specific to AGC during this stage.

User Management: We used Active Directory for user management, which worked as expected and aligns with standard enterprise practices.

Sandbox Environment: AGC does not provide traditional sandbox environments. Instead, Atlassian provisions multiple separate sites that can be used for testing purposes.

Migration Process: Pre-migration checks are consistent with public cloud migrations, and the overall migration process follows the same workflow.

Apps: Many Marketplace apps are not immediately FedRAMP compliant, which adds additional effort. Xray is now fully FedRAMP compliant in AGC; however, its migration path differs slightly. Atlassian must install Xray on the target site, and it is highly recommended to have Xray support available during pre-migration checks and migration activities.

What other issues are you facing with DC to AGC migration?

Comments

John Morales_hjumvz

other Jira DC to Jira Cloud migration considerations.

Jira Integrations

if you have developed integration with Jira and specifically with Jira custom fields and their corresponding internal identifies, aka Jira Field IDs, when migration to Jira Cloud, these Jira Field IDs will change and you will need to review and update your integrations. This also include Jira JQL and Confluence Pages with the Confluence Jira Macro to be updated.

Jira APIs

if you have developed integration with Jira DC APIs you will need to review and update to the Jira APIs that support Jira Cloud. In addition, be aware of the Jira Cloud API rate limiting constraits. You may need to factor this within your integration or automation leveraging the Jira Cloud APIs.

Adaptavist ScriptRunner for Jira

You will need to revisit any Jira JQL leveraging the Adaptavist ScriptRunner JQL enhancements as ScriptRunner does not migrate well from Jira DC to Jira Cloud

Zoriana Bogutska_Kolekti

Hi @Tankem Williams

Have you migrated your Confluence to AGC, too?

My team created a version of the Mosaic app for AGC. It includes key formatting features such as Tabs, Numbered Headings, LaTeX, Cards, Banner, Tooltip/Footnote, and full-page templates for tech and non-tech teams.

Tankem Williams

Great insight, unfortunately this post is mainly for Atlassian Government Cloud (AGC) not Jira public cloud. In AGC, Scriptrunner is not yet FedRamp compliant as far as I know and does not have a migration path into AGC. Everything you have mentioned is very true and correct in Jira Public Cloud.

Tankem Williams

Hello @Zoriana Bogutska_Kolekti Yes, Confluence migration into AGC is currently ongoing. I will share with you the experience and things to look forward to once completed.