Error while importing JIRA Server data to JIRA Cloud

[Deleted user]

When I impot the data, I get this message: An error occurred while importing:

Error importing data: cloud.atlassian.logmon.laas.api.PrivacySafeException: Privacy-safe boxing of a com.atlassian.jira.bc.dataimport.identity.UsersImportService$WrappingCrowdException

[Earl McCutcheon · Accepted solution]

Hello @[deleted] ,

We have the following support request in place for you to look into this further:

• https://getsupport.atlassian.com/browse/MOVE-15159

Please do reach back out through the support request for follow up communications about the user account in question and steps to fix to prevent disclosing any PPI on this public forum.

But I also wanted to relay the non-critical information on the initial findings here in case anyone else runs into the same issue,  Looking at the error in the logging we identified a user with an email that somehow got entered into the source instance in an incorrect format,  the format the account was in, was:

 user_name@domain.p

And having the ".p" is in an invalid format since it has only 1 character after the dot and is causing the import to bail out.  The steps to fix involve correcting the format on the source instance and generating a new backup, or modifying the existing backup manually to update all occurrences of the incorrectly formatted username.

Regards,
Earl

[Fábio W. [Atlassian]]

Hi!

In case you run into this error message while performing a site import in the Jira cloud, please refer to the following KB for additional guidance:

• Resolve user and groups synchronization error

We compiled some checks and verifications you can try before attempting a new import. We hope that helps.

Best,

Fábio

[Daniel Ebers]

Hi mtorbicki,

welcome to the Atlassian Community!

The error message during import happens in state "synchronizing users and groups". This is clearly visible from screenshot but the reasons are not.

The is one wild guess, that the server instance had more users that the cloud plan offers - but this can be surely wrong for your case.

Unfortunately, to say something precise more details would be needed.

With no doubt the error message should be improved - why there is a Suggestion open on this.
https://jira.atlassian.com/browse/MIG-162

And to conclude the best you can do for your current migration is what Philip said in the linked Suggestion - to reach out to Atlassian Support.

(...) because the error message is so unhelpful, I think your best option is to raise a ticket with Atlassian support. They will have the visibility to pinpoint the problem, which could be several different things. (...)

Cheers,
Daniel