In this post we will be discussing our assessment on the cloud migration for ProForma: Forms & Checklist for Jira, developed by ThinkTilt which has been acquired by Atlassian.
To learn more about our Jira app migration evaluation series, take a look at our introductory post: Jira App Migration: Top 10 Apps Evaluated.
Shifting ProForma data to the Cloud is pretty straightforward as there is almost 100% feature parity between Server and Cloud environments, and lots of support resources available. All the same, you must be mindful of a few issues that can occur in order to have a successful migration.
| Feature Compatibility |  |
| Migration Complexity |  |
| Migration Method |  |
| Migration Support Available |  |
| Supported Jira Migration Methods |  |
Feature Compatibility
Almost all of the features available on ProForma Server, are available on Cloud. The only features that are not available on Cloud:
- ProForma API, which allows customers to access and manipulate data, and
- Integration with Refined Structure and Theme, which is used to build custom support sites with accessible answers.
In the Cloud version you can look forward to features such as linking Jira due date fields to a form field and integration with Deep Clone for Jira, neither of which are available in the Server version.
Migration Method and Complexity
To migrate ProForma data from Server to Cloud, you must complete a full site import which should transfer all of your data.
There is currently no support to migrate ProForma with the Jira Cloud Migration Assistant (JCMA).
Migration Support Available
If you have any issues with your transition to the Cloud, both ThinkTilt and Atlassian provide a variety of resources to help with your migration needs. Refer to the ProForma Documentation to understand the migration journey.
In addition, ThinkTilt is a close partner of ours at Highway Three so we can provide you with expertise and assistance with your migration.
Possible Challenges
During our ProForma migration testing, we discovered a few complications in the Server to Cloud migration journey. Firstly, ProForma must be notified of the migration date so that they can reset the internal key before your full site import. Resetting the internal key ensures that linked fields work correctly.
Secondly, there is no method to migrate individual projects, so all of your forms from all projects are migrated together. The only method to migrate projects separately is to use the JCMA which is presently not supported, but there are plans to integrate ProForma with the JCMA on their roadmap.
Resources: