How can I retain the user specific fields like assignee while doing CSV import to migrate issues?

[Eshita Bhadoria]

Hi, 

I am migrating my project from my company-owned JIRA to client-owned JIRA, both JIRA is on cloud. I am using CSV migration because there is no other way for cloud to cloud migration. The major problem that I am facing is I am not able to retain the assignees, reporters, etc in the target system. 

As I understand, these user-specific fields are showing first and last names in exported CSV file, so I went and created users with the same first and last name in the target system before doing the import. I am doing this because these users have company-given email ids and I don't want CSV import to create users on its own with random email prefixes but unfortunately this did not work for me. CSV import created new users with some random email prefix. 

For example, my email is eshitabhadoria@xyz.com (consider XYZ is my company domain name) and my first and last name in CSV was Eshita Bhadoria, so I went and create the user in target JIRA with email eshitabhadoria@xyz.com and Eshita Bhadoria as my first and last name. I mapped the Assignee field and chose the map value. While mapping value I was able to see Eshita Bhadoria in the mapped value and I thought JIRA correctly mapped my name, but in the next step, I saw that a new user got created and when I checked in user management a new user with email ebhadoria@xyz.com was created with the inactive state. So, ebhadoria is the random string i am talking about. 

I have looking to migrate approx 7000 issues and it's impossible to assign tickets to correct assignees manually. Hoping to get some help from the community. 

[Matt Doar]

You can avoid changing the Summary of existing issues by having an empty Summary column in your CSV. The original Summary is not modified in this case. You could try the same trick with Assignee - have a column but leave it blank and see what happens when you test it with one issue

[Eshita Bhadoria]

Thanks for your response. I am trying to migrate tickets from one Jira could to another so basically I am creating new tickets in target Jira. I think your solution would have worked perfectly if would be updating existing tickets via CSV import. 

[Trudy Claspill]

I think in your import data the user information needs to be either the user email address that matches a user account that already exists in your destination Jira system, or the Jira user account id that matches to a user account that already exists in your destination Jira system.

I got that from the "Tips" section of this page:

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

[Eshita Bhadoria]

I think having email instead of first and last name will help but I looked for a way to put email in the assignee column in CSV but I could not find one. 

I think the solution with id will not work because ID is Jira created field which I can't control. 

Thanks for your help. Let me know if you know the way to put email in csv. 

[Trudy Claspill]

I don't think you can automatically get the user's email when you are exporting the data to CSV. That is a modification you would have to make to the data after exporting it and before importing it.