JMWE Data Center to Cloud Migration Checklist
To assist in your migration, you can use the following checklists for migrating JMWE from Data Center to Cloud.
Note: Migration from Jira Server is not supported, as the version of JMWE necessary for migration using JCMA or CMJ is not available on Server.
✅ Pre-Migration Checks
Checkpoint | Actions | |
|---|---|---|
| 1 | App installation, version | Confirm the JMWE app is installed and licensed (trial or paid) on the target Jira Cloud instance. Ensure: JMWE Data Center (DC) app is installed and licensed, and the version is 7.2.0 or later (preferably the latest), and JCMA (or Configuration Manager for Jira) is the highest compatible version with Jira Data Center. |
| 2 | JMWE DC usage and understanding JMWE DC vs Cloud | Identify where JMWE is used in your Jira DC instance to enable comparison after migrating to the Cloud. You can use one or more of the following methods for this:
Gain a clear understanding of the feature differences between JMWE DC and Cloud. See Migrating to Jira Cloud for a breakdown of migration steps. Review the feature comparison for details on the differences between JMWE DC and JMWE Cloud, including updated post functions on JMWE Cloud. |
| 3 | JMWE Cloud scripts | Convert the Groovy scripts used in JMWE DC to equivalent Nunjucks or Jira Expressions, and keep them ready for use after the migration to JMWE Cloud is complete. |
| 4 | Test migration | Perform a test migration to identify any potential issues in advance; this helps ensure a smoother Production migration. |
✅ Post-Migration Checks
Checkpoint | Actions | |
|---|---|---|
| 1 | Fix errors, warnings listed on the Cloud Post Migration page | On the Post Migration page of the target Cloud instance, review all the tabs and resolve the issues listed there. Refer to the Post migration page for details. |
| 2 | Replace Groovy scripts | For each migrated JMWE extension, replace any Groovy scripts with equivalent Nunjucks or Jira Expressions scripts as required by the specific JMWE extension. |
| 3 | Verify migrated JMWE actions. | Currently, Shared extensions, Event-based actions, and Scheduled actions are migrated, but due to some feature differences, it is highly recommended that you verify these actions after migration. |
| 4 | Recreate JMWE Conditions and Validators | Note: When migrating using JCMA, some JMWE Data Center Conditions and Validators that have Jira native versions will be converted to those Jira Cloud native equivalents. This is done automatically by JCMA, outside of JMWE’s control. Once the migration to Cloud is completed, replace the migrated Jira Cloud native workflow Validators and Conditions; you will need to manually recreate your JMWE Validators and Conditions, and add the Conditional Validation Jira Expression script, if any. |
| 5 | Permissions needed for JMWE add-on user on Cloud | Ensure your Jira Cloud instance aligns with all the points mentioned here: Verifying Your JIRA Instance Ensure the “Jira Misc Workflow Extensions” add-on user in your Cloud instance is part of the following groups:
You can verify the above by running the following Nunjucks script in the Nunjucks and Jira expression tester page of your Cloud instance: {{ "XXX-YYY-ZZZ" | userInfo | field("groups.items") | field("name") }}Replace  “Lookup user…” button If the JMWE add-on user is not in any of the above groups, contact Atlassian Support to add the user to the required groups. |
| 6 | Key workflow transition validations | Create test issues and execute key transitions to confirm JMWE functions as expected. |
For detailed information about migrating JMWE from Server or Data Center to Cloud, please refer to our migration documentation here: Migrating from Data Center