Hi,
as vendor, we have a huge app dataset to migrate from Jira DC to cloud. Unluckily we are unable to provide one update for every migration in the future. At the moment it seems impossible for customers to just rerun an app migration with a given scope of projects in Jira with a new version of our migration support.
Is there already any way to help customers to support future migration path updates from our DC app?
In our plugin, we’re developing a separate JSON export from DC to Cloud, because it stresses customers a lot to synchronously migrate all plugins and the native data of Confluence.
The challenge is mapping the IDs of the Cloud entities to DC, so we try to choose which data we migrate as CCMA vs externally with JSON.
Hello,
At the moment it seems impossible for customers to just rerun an app migration with a given scope of projects in Jira with a new version of our migration support
We have reruns but only for failed and incomplete app migrations if we extend that to completed migrations does that cover your use case?
Or would you like something more flexible like running an app only migration with a given set of projects?
Hello,
stresses customers a lot to synchronously migrate all plugins and the native data of Confluence
Would you like to be able to remigrate a space and it only taking the delta of server and cloud? Kind of like whats being asked here for Jira? https://jira.atlassian.com/browse/MIG-865
we’re developing a separate JSON export from DC to Cloud
What feature would you like to see in CCMA, ability to migrate app data only for given spaces?