Hi Ivana and Remie,
Circumstances have conspired to make the end-of-2022 date look increasingly unlikely. We postponed the “uninstall / reinstall required…” issue in favour of other work, so State 1 is not yet GA. We’re currently working on the OAuth 2 piece of State 2 but have not started any State 3 work yet such as remote access to storage APIs.
The most recent update on all of this is my dev day talk from last month. We’re actively looking at Connect and Forge unification strategy, timelines etc. so I hope we have more to share in a little while.
As for migrating the database from Connect to Forge, the two tickets linked above will make it easier, but in the mean time I’m happy to discuss options for doing it without those features, or answer any other questions you have.
For example, if your migration work can fit within Forge limits, it should be possible to, from within a Forge function, fetch data from your Connect app server (you’ll need to implement some auth) and then use the storage APIs to store it in Forge storage. You could also make use of Web Triggers to push the data in from the connect app server.
Hope that’s helpful,
James Hazelwood
Atlassian