What isn't migrated with the Jira Cloud Migration Assistant

[Sofia Quintero]

Hello

I´m learning about migrations from Jira server to cloud, and i was looking at the confluence information related What gets migrated with the Jira Cloud Migration Assistant.      

And i saw that there ara some features that are not migrating to cloud by the asistant, like:  project´s Custom Fields, project´s Workflow functions, project´s Links to issues, Dashboards.

How is possible to handel this? Without losing information from custom flelds the workflow´s customizations

[Walter Buggenhout]

Hi @Sofia Quintero,

Having done some migrations myself, I can tell you that migrating today is a complex process. It is absolutely crucial to assess the complexity of your current server instance and plan ahead.

On the bright side, I have seen the migration tools improve with every step along the way. There is definitely a lot of effort going into solving issues along the way. But certain things need to be fixed manually (before or after the migration). Stuff like creating dashboards manually, configuring cross-project boards again from scratch, cleaning up migrated fields, schemes and other things that get duplicated.

My best advice would be to work with migration support and/or a solutions partner that has done the job and knows what to expect. That way you can evaluate whether the time to migrate is now, what the cost and effort for manual steps would be and what you should indeed do to mitigate the risks.

[Sofia Quintero]

@Walter BuggenhoutThank you for answer me, i understand that is a complex process.
Regarding the question, how would you handel the custom´s fields information?