Hello,
I wanted to ask what is the actually a recommended way how to migrate data used in a connect app (stored in a custom backend) to Forge.
The assumption is: connect is turned off by Dec 26 - so nothing relating connect stays in manifest if the app is to work properly
- if the first step would be to rewrite
connectModulesinto forgemodules- then the app gains access to forge storage features - which is perfect - but at which point the app actually migrates the data into forge?
Possible solutions I pondered upon
- simply configure a “remote” with FIT auth inside the manifest.yml - and the app would be pulling data from the custom backend - and as the user interacts with the app - it would either pull data from the remote, or directly save data into forge storage. This is extremely bad way how to do it. Not only the app gets complicated, but it will be ineligible for Runs on Atlassian badge
- or, I think there must be some way, how to configure some kind of “migration of data”. Meaning - once a user updates the app to the version which is fully on Forge - with Runs on Atlassian badge - the app is installed as empty app. On the first run - the user would be prompted to somehow trigger a mandatory “data migration”
I have found this App migration guides https://developer.atlassian.com/platform/app-migration/prepare-cloud-app-forge/ - but so far it seems like this relates to server/dc apps, rather than cloud connect → forge .
Does anybody have some recommendation?