[Cloud-Migration] Pre-migration checks / data preparation errors
Asked by Martin Fredrich:

Hi,

I would like to migrate a Jira Service Management project from server to cloud. The project is heavily customized and there are currently 229047 issues and 158 GB of attachments in this project.

Now I get errors in the pre-migration checks / data preparation. The log file says:

```

2024-03-23 14:54:19.192764 ERROR <Project-Name> project-export We couldn't export Change Group 4361869 (on Issue XX-12345). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=1592". [JCMA 000]
```

<br />

This entry exists a total of 13932 times.

I could not find anything about this specific error on the trouble-shooting pages, nor on the community pages.  
Is there a workaround for this?

Kind regards,  
Martin


Answers:
author: Walter Buggenhout
body: Hi [@Martin Fredrich](/t5/user/viewprofilepage/user-id/3883986),

Just trying to interpret the message, it seems as if there is something odd with a group or organization linked to an issue with key XX-12345. That key is so specific that I doubt if this is real or just a sample message. If the issue really exists, I would try to see if there's any strange groups or organisation listed on it / maybe try to find out if you can identify the organisation with id 1592 in your server instance.

If that doesn't shed any more light, the next best step is to create a support ticket directly with [Atlassian migration support](https://support.atlassian.com/contact/#/).

Hope this helps!

comments: author: Martin Fredrich
body: Hi [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225),

thank you for your quick answer!

xx-12345 was just an example.

The project has the key "CS". And unfortunately it is not just one ticket that generates the error message, but there are always different ticket and change group IDs.

Here are some lines of the log:

```
2024-03-23 14:57:48.054389100 ERROR CS project-export We couldn't export Change Group 3505015 (on Issue CS-185387). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=442". [JCMA 000]
2024-03-23 14:57:48.304392200 ERROR CS project-export We couldn't export Change Group 3949585 (on Issue CS-203336). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=649". [JCMA 000]
2024-03-23 14:57:49.788773600 ERROR CS project-export We couldn't export Change Group 3699264 (on Issue CS-192498). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=543". [JCMA 000]
2024-03-23 14:57:50.148141700 ERROR CS project-export We couldn't export Change Group 3961094 (on Issue CS-204163). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=590". [JCMA 000]
2024-03-23 14:57:50.538782300 ERROR CS project-export We couldn't export Change Group 3961105 (on Issue CS-204164). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=649". [JCMA 000]
2024-03-23 14:57:50.773147800 ERROR CS project-export We couldn't export Change Group 4300152 (on Issue CS-226582). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=545". [JCMA 000]
2024-03-23 14:57:51.460643100 ERROR CS project-export We couldn't export Change Group 4225808 (on Issue CS-221596). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=721". [JCMA 000]
2024-03-23 14:57:52.601269 ERROR CS project-export We couldn't export Change Group 4086610 (on Issue CS-212545). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=831". [JCMA 000]
2024-03-23 14:57:53.241896700 ERROR CS project-export We couldn't export Change Group 4368085 (on Issue CS-230855). Reason: java.lang.NumberFormatException: For input string: "CustomerOrganizationImpl{id=512". [JCMA 000]
```

The way I interpret the error message, the JCMA tries to export a history entry (possibly from the changeitem / changegroup table) and gets a wrong data type (java.lang.NumberFormatException). But I could be completely wrong here.

I have taken a look at some of the tickets. There are no links to other tickets or projects. However, all checked tickets are under a certain security level. Could this be the source of the error?


author: KHAJABANDENAWAZ KHAJABANDENAWAZ
body: Help me sir


author: Joseph Chung Yin
body: [@Martin Fredrich](/t5/user/viewprofilepage/user-id/3883986) -

I agreed with [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) stated. In my option, I highly recommend that you reach out to Atlassian Support (<https://support.atlassian.com>) for them to assist you on the migration issues. As migration process is different between different users/companies, Atlassian Support would be the best POC for troubleshooting process.

Sorry.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.


author: Martin Fredrich
body: **UPDATE:**

My thoughts about the history and yours, [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) brought me here:

![cs0.png](https://community.atlassian.com/t5/image/serverpage/image-id/313993i09BD0943C5774C97/image-size/large?v=v2&px=999 "cs0.png")

should be loopk like that:  

![cs1.png](https://community.atlassian.com/t5/image/serverpage/image-id/313994i013366D0F97FC7D4/image-size/large?v=v2&px=999 "cs1.png")

There is probably actually a problem with the entry in the table. The conversion is done by an automatism and somehow something wrong is entered or the organization is not resolved correctly.


Tags: cloud

cloud-migration-assistant

jira-service-management

jira-service-management-cloud

jira-service-management-server