Migrating from Jira Server + Data Center to Jira Cloud

Licensing: We’re happy to assist our customers migrate to Jira Cloud from Jira Server or Jira Data Center. To alleviate any concerns about paying for "double licensing" during your transition we will provide discount codes so you will only have to pay for one platform (either Cloud or Server/Data Center). We’ll do this by verifying your active license on one platform and we’ll provide a promotion code for the license on the other.

Associations from Git data: Indexing Jira issues via commit messages is the same in Jira Server + Data Center as Jira Cloud. All the associations will be preserved.

Manual commit associations: At this time, manual commit <--> Jira issue associations cannot be migrated automatically but request BigBrassBand Support for instructions on how to check.

Self-hosted Git servers: When connecting a self-hosted git server to Git Integration for Jira Cloud the git server must have a publicly addressable + route-able address. GitHub.com, Azure DevOps, GitLab.com and other services hosted on the “public cloud” work without any administrator interventions.

For more information, see: Allowlist (whitelist) BigBrassBand Cloud

Known Atlassian issue: We highly recommend testing your Jira migration to the Cloud on a test Jira Cloud site. AC-1528 is a bug in Atlassian Jira Cloud that breaks all Jira Cloud Atlassian Marketplace apps when a new project import is made. When migrating your users to Jira Cloud – we recommend installing and configuring the Git Integration for Jira Cloud app after all of your Jira users/projects/issues data is imported and verified.

If you need additional support - contact BigBrassBand Support.