Exporting to CSV to move to a new instance

[kdickason]

Let's talk exporting a Jira Project so it can be imported to a new Jira Server  (Data Center).

If I export to .CSV then import on the new server, what will be lost in the transfer?  Comments? Documents? Links? Workflows?  I need to know what I won't get.  Also, do I need to re-set up my users on the new server before the import?  I would love a concise answer to above (vs. a lot of links to pages and documents).  

I know .CSV is not the optimal way to move a project.  What is?  XML export of ____, zip up of attachments directory?  Please advise. 

[Trudy P Claspill]

How are you "exporting the project" specifically?

If you use the Issue Search screen to export issue data, that will not bring across any project configuration information - workflow, permissions, notifications, issue types, screens, etc. All that project configuration information will have to be set up in advance.

Additionally when you import that issue data CSV that will no create any custom fields that you had in the original instance.

Attachments will not automatically come across. There are methods that can be used such that Attachments can be imported when import an issue data CSV.

Issue History entries will not come across in that process.

Comments on issue can be included in the issue data CSV export and imported from CSV. Worklogs also can be brought across, I believe. Both may take some adjusting of the exported data to make it importable.

There are multiple articles available online that provide guidance on migrating projects between self-hosted Jira instances. Here are a few:

https://confluence.atlassian.com/adminjiraserver/migrating-projects-to-another-jira-instance-938847925.html

https://rozdoum.com/blog/how-to-migrate-jira-project-to-another-instance-without-disrupting-your-teams.html

https://ancaonuta.medium.com/how-to-migrate-a-jira-project-from-a-jira-instance-to-another-one-c774cbc04a1d