JIRA MIGRATION | attachment in CSV is not getting imported correctly

[hitesh kumar dewangan]

Does anyone know how to migrate the attachments to another JIRA cloud instance using CSV? 

After Migration, I see that all the attachments are not accessible.

I am doing migration for my projects from the cloud instance A to B.

cloud A- mysiteA.atlassian.net
cloud B- mysiteB.atlassian.net

But I am facing constant problems with attachment migration. initially, I thought the issue was with using two different emails API token. (https://confluence.atlassian.com/cloudkb/importing-attachments-into-jira-cloud-using-csv-external-system-importer-966669960.html\) So, to verify I added my common email id hitesh.kumar@mysiteB.com in both JIRA and used the API token of JIRA cloud instance A but still the issue remains,

21/Jan/20 2:45 PM;sayedsarfaraz.hussain;image-20200121-091509.png;https://hitesh.kumar%40mysiteB.com:abcdef123456@globalenglish.atlassian.net/secure/attachment/44854/image-20200121-091509.png

[Earl McCutcheon]

Hello @hitesh kumar dewangan ,

Thanks for reaching out and restating the goal and problem statement, you are trying to migrate Issues from 'cloud A' to 'cloud B' using CSV import, but you are having an issue with the authentication.

For the user authentication information in the CSV you want to use a user with access to the issue in the source instance, and the URL to the source issue.  So the user and api key that you are using will be the user from Cloud A that has access to the source issue not the user from Cloud B whom is performing the import.

So if your image is hosted on "mysiteA.atlassian.net" and you are doing the CSV import  on "mysiteB.atlassian.net" the URL in the csv should be formatted so that the user account and API token for the user on mysiteA is used:

https://username%40<email_Domain_Connected_to_mysiteA>.com:abcdef123456@mysiteA.atlassian.net/secure/attachment/44854/image-20200121-091509.png

If this is not the case, what is the full error you are receiving, making sure to scrub the username and api token if visible.

Regards,
Earl