Intentionally migrate Jira issues to the cloud without attachments

Bryan Guffey_7wc7xl

I'm testing some features in Jira Cloud and want to move a Jira DC project with over 100K Jira issues but would like to not move the 461GB of attachments because I'd like this to complete in under a year, lol. 

I'm working in a sandbox, so the easiest answer would be to just find the folder for all of the attachments and hide it from Jira, but I'm not sure that wouldn't break the JCMA.]

Alternatively, I could write a script to delete all the attachments, since this is just a sandbox, but I'd like to keep the data if possible. 

Has anyone else run into this problem and do you have any suggestions? 

Trudy P Claspill

Hello @Bryan Guffey 

There is a change request about being able to intentionally exclude attachments from migration in JCMA.

https://jira.atlassian.com/browse/MIG-1076

In my current migration the stakeholders had moved attachments from the Jira server to a network share to recover space on the Jira server. JCMA attempts to migrate the attachments but cannot find them. JCMA is built to recognize this error and keep going. This error seems to be realized faster than the time it would take to actually move the data.

Also, in my current migration I moved a total of over 2.3 TB of data and over 2.3 million issues in 142 projects. There was an additional 400 GB of attachments that could not be found due to being on the network share.  I first ran batches of Attachments Only migration plans, for the projects where I knew the attachments could be found. Then I migrated the projects (issues, users, groups, filters, agile boards, dashboards) in another set of migration plans that included the projects where the attachments were not accessible.

FWIW, all together it took a total of about 45 hours.