Ever since Atlassian announced that they will be ending Server support by February 2, 2024, more and more companies are considering to shift from Jira Server to Jira Cloud. While migrating Jira data between environments is straight-forward, it can be challenging to migrate add-on data to the Cloud.
In this post of our Top 10 Apps Evaluated series, we discuss the migration journey for BigGantt – Gantt Chart for Jira developed by SoftwarePlant.
To learn more about the series, take a look at our introductory post: Jira App Migration: Top 10 Apps Evaluated.
Transferring BigGantt data from Server to Cloud is difficult. There are some feature discrepancies between environments, migrating is an entirely manual process, and there is little documentation available to support your migration.
Proceed on your own with caution.
| Feature Compatibility |  |
| Migration Complexity |  |
| Migration Method |  |
| Migration Support Available |  |
| Supported Jira Migration Methods |  |
Feature Compatibility
Since the fundamental architecture of Jira Server is different from Jira Cloud, there are certain limitations to the features available on Cloud. Some of the key missing features on BigGantt Cloud include:
- Dashboard gadgets
- Creating Jira sub-tasks in your gantt chart
- JQL hints when you type in Quick filters or Search box
For a complete list of missing functionality in Jira Cloud, refer to BigGantt’s Server and Cloud feature comparison.
In order to decrease the feature discrepancies that exist between both environments, SoftwarePlant continues to develop more features and bring increased functionality to BigGantt Cloud.
Migration Method and Complexity
Currently, migrating with a full site import or the Jira Cloud Migration Assistant (JCMA) are not compatible methods of transferring BigGantt data from Server to Cloud.
At this time, you have to manually input all of your BigGantt data from Server into your Jira Cloud instance.
Migration Support Available
Even though there are no supported Jira migration methods, BigGantt provides some insight on the migration tools they are developing to provide customers with a smooth migration experience to the Cloud in the future. You can read more about it on SoftwarePlant’s Server to Cloud Migration article.
If you have any questions specific to your migration, you can always contact SoftwarePlant by submitting a support ticket.
Possible Challenges
Migrating BigGantt data is time consuming and entirely manual.
The lack of feature parity between the server and cloud versions may be problematic for some teams. We recommend you review the differences closely to determine how this impacts your team so that you can adjust your processes and expectations accordingly.
We are here for you! Do not hesitate to contact us when you need help with your Jira migration.
Resources: