DC to Cloud migration guide
We’re excited to support you in your Cloud migration journey! This page guides you through migrating your custom field configurations, data, and workflow enhancements from Jira Data Center (DC) to Jira Cloud using the Enhancer Plugin for Jira (JEP).
Before you start
You must compare DC and Cloud features. The Cloud version of Enhancer Plugin for Jira is continuously evolving. While most Data Center features are available on the Cloud, there may be some differences. For a full comparison, please refer to the Differences between Cloud and DC versions page.
Some JEP workflow enhancements are not supported on Cloud. Review the JEP workflow enhancement module keys used in your Data Center instance to identify possible workflow behavior changes. For more information, refer to the FAQ page.
Enhancer Plugin for Jira relies on the integrity of issue history to generate field data. Ensure your DC instance has complete and consistent issue histories before starting the migration.
If you anticipate needing assistance from our support team, we recommend reaching out at least 3 months before your target migration date to ensure we have sufficient time and resources to support you.
Steps
Transfer your custom fields and their configurations from your DC instances to your Jira Cloud instance.
Add your Enhancer Plugin workflow conditions, validators, and post functions to your Jira Cloud workflows. These will become active once you publish the workflows.
Begin the recalculation process for existing issues. For best results, we recommend recalculating in batches of around 1,000 issues at a time, especially when testing.
Recalculation and performance considerations
Recalculating field data, especially for large volumes of issues, may take time depending on the number of issues and overall instance performance.
Approximate issue volume | Expected duration |
|---|---|
Up to 1,000 | A few minutes |
10,000+ | Several hours to a few days |
100,000+ | Several days or more |
These estimates may vary based on your instance size and other factors. If you have a large dataset, you can contact support for guidance on optimizing performance.
Keep in mind that we support recalculation for only one test instance, with a single test run. If you have multiple sandbox environments, choose one to verify the migration results.
When planning your timeline, please allow sufficient time before your go-live date to complete the process efficiently.
All recalculation and data migration actions are securely performed within your Jira environment or via established and secure channels. We do not store or transmit issue data externally. You can confidently proceed with the migration knowing that your data remains protected throughout the process.
After the migration
JEP - Issues From the Same Reporter panel visibility in Jira Cloud
In Jira Cloud, the JEP - Issues From the Same Reporter panel is not automatically displayed in work item views due to Forge limitations. After migration, the administrator needs to manually add the JEP panel to the work item layout to make it visible to all users.
Follow these steps to enable it:
Open any Jira work item.
From the top menu, click the Jira View app actions (cog icon) button.
Select JEP - Issues from the same reporter.
When the JEP panel appears, click the ⋯ button next to the panel name.
Click Show for all work items.
Once enabled, the panel will appear automatically on all work items for all users in your project.
Still have questions?
If you're planning a migration or recalculation job and think you’ll need support:
Contact us at least 3 months in advance.
Let us know your estimated issue count and timeline.
We're happy to assist, but please note that support resources are limited, and early contact helps avoid delays.