Currently, migrating custom content from pure Connect to pure Forge isn't supported, but moving from pure Connect to Connect on Forge is. This leads to custom content types from Connect apps not being available after migrating the app to Forge. Custom content only becomes available when using the same API from within the Forge app.

Full support for custom content migration for pure Forge apps is crucial for partners to make informed decisions and effectively plan their migration paths. The absence of this support could hinder the adoption of Forge and affect the functionality of key applications.

The lack of support for custom content migration to pure Forge results in these content types being unavailable post-migration, which is a significant blocker for partners relying on these features.

At the moment, there is no internal timeline, roadmap update, or official notice regarding when custom content migration will be fully supported for pure Forge apps

By addressing this issue, we aim to facilitate a smoother migration process for partners and enhance the Forge platform's capabilities. This will ultimately lead to better planning and decision-making for partners and improve the overall user experience.

Proposed Solution:

• Investigate the possibility of supporting custom content migration from pure Connect to pure Forge, as this is currently unsupported.

• Provide interim solutions to maintain access to custom content while a definitive one is not available.