Dear SugarCRM Support Team,
We are planning to upgrade our custom SugarCRM Mobile application from version 45.0.657-1.4.2-2 to 87.0.850-1.4.2-2 and would like to seek your guidance before initiating this activity.
Our existing mobile application includes extensive customizations developed using Cordova and Backbone-based components, as supported in version 45. In the newer SugarCRM Mobile versions, we understand that there has been a significant architectural shift, with React-based technology introduced and much of the functionality migrated away from Cordova and Backbone.
In this context, we would appreciate your advice on the following:
- Whether upgrading from v45 to v87 would require a complete or partial rewrite of our existing mobile custom code due to the transition to React.
- Which legacy mobile customization frameworks or APIs are deprecated or no longer supported in the latest versions.
- Recommended migration strategy or best practices for converting existing Cordova/Backbone-based customizations to the React-based mobile framework.
- Availability of any official documentation, migration guides, or tools to support this conversion.
Additionally, from a long-term support perspective, we would like your guidance on:
- Which SugarCRM Mobile versions or upgrade paths are best suited for long-term stability and support.
- Recommendations on how to design or refactor mobile customizations to minimize rework in future upgrades.
- Any SugarCRM-supported standards or architectural guidelines we should follow to ensure our mobile application remains compatible with future releases.
Given the scale of these changes, we want to ensure our upgrade and redevelopment approach aligns with SugarCRM’s supported technologies and long-term roadmap, while avoiding unsupported customization patterns.
We appreciate your guidance and look forward to your recommendations on how best to proceed.
Thanks & Regards,
Chetan Ghaydar
