Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-66787

Server ID uses the wrong format and is invalid after migrating Jira from Cloud to Server

XMLWordPrintable

    • 7.07
    • 113
    • Severity 3 - Minor
    • 14
    • Hide
      Atlassian Update – 14 August 2025

      Hi everyone,

      This issue has been reviewed by the Jira Data Center Development team. As a result of our investigation, we have decided to freeze our work on this issue.

      XML Backup for Server in Jira Cloud has been discontinued effective June 30, 2025. As an alternative, you may utilize the CSV file import wizard to facilitate the export of data from Cloud to Data Center.

      We’re closing the ticket with the resolution Won't fix.

      If you require any assistance with utilizing the alternative import methods, please don’t hesitate to contact our support team. We're here to help and want to ensure you have the support you need

      Best regards

      Jakub Reczycki
      Software Engineer, JIRA Server

      Show
      Atlassian Update – 14 August 2025 Hi everyone, This issue has been reviewed by the Jira Data Center Development team. As a result of our investigation, we have decided to freeze our work on this issue. XML Backup for Server in Jira Cloud has been discontinued effective June 30, 2025 . As an alternative, you may utilize the CSV file import wizard to facilitate the export of data from Cloud to Data Center. We’re closing the ticket with the resolution Won't fix . If you require any assistance with utilizing the alternative import methods, please don’t hesitate to contact our support team. We're here to help and want to ensure you have the support you need Best regards Jakub Reczycki Software Engineer, JIRA Server

      Summary

      After the migration of data from Jira Cloud to Server, the user is required to generate a new license for any Jira application (such as Service Desk, Jira Core, and/or Jira Software). But they are unable to do so.   Further investigation found that the Server ID in the System Info page is displaying incorrectly in their restored system.  Rather than the proper four groups of four alphanumeric characters (A-Z 0-9), the Server ID appears to be using the old Cloud instance identifier which uses 32 hexadecimal characters (0-9 a-f) to identify the instance.

      Environment

      Jira Cloud (Source instance)
      Jira Server (Destination instance)

      Expected Results

      Displays the Server ID properly (Example: ABCD-EFGH-IJKL-MNOP )

      Actual Results

      Displays the Server ID incorrectly  (Example: 12ab3c78-da9d-451f-acab-52f90c9439c0 )

      Workaround

      You can update the Server ID by following the steps in the KB: Changing Server ID for Test Installations - Atlassian Documentation.

        1. 1.png
          1.png
          41 kB

              Unassigned Unassigned
              imazuki Irfan Mazli Mazuki (Inactive)
              Votes:
              43 Vote for this issue
              Watchers:
              54 Start watching this issue

                Created:
                Updated:
                Resolved: