Some apps may not need a server to cloud migration path.
Common examples we’ve found include:
Integrations to a 3rd party service (although post install steps like authentication and reconfiguration may apply).
Apps that rely entirely on core Atlassian Data and don’t store any data of their own.
Apps that add data to core data (e.g. macros) that use the same keys and format in server and cloud.
For customers this means that they only need to install the app in cloud and it “just works”.
We’ve found though is that we can’t - and more importantly our customers can’t - easily differentiate apps that don’t need to build migration paths from those that do.
Does this case apply to you? If so, how are you communicating this with your customers?
For anyone who is experiencing issues with the accuracy of the information presented in the Cloud Migrations Assistant (e.g. your app appears to be “not available in cloud” when you have a cloud version available or documentation for your feature differences that does not appear or your app appears to not support a migration from server to cloud when it does) please contact me!
We hope to make this more self service in the future.
@akassab Currently this is implemented just for Jira Server to Cloud migrations. We need to make some additional changes to support Confluence Server to Cloud migrations as well. We plan to add this in the next upcoming eazyBI for Confluence version.
I am not able to see the database migrator option on Jira server as i am trying to migrate to cloud. I had perform the test migration month ago that time the option was visible but as i am trying to do new migration but did see any option available. Can you please let me know why ? or do we have to enable any flag to get that option?