---
title: "JMWE Data Center to Cloud Migration Checklist"
canonical: "https://support.appfire.com/space/SUPPORT/2143617046/JMWE%20Data%20Center%20to%20Cloud%20Migration%20Checklist"
format: markdown
---
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** |
| --- | --- |
| App installation, version | - [ ] Confirm the **JMWE** app is installed and licensed (trial or paid) on the target Jira Cloud instance.<br>Ensure:<br>- [ ] **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](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?hosting=cloud&tab=overview)) is the highest compatible version with Jira Data Center. |
| 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:<br>- If you’re using JMWE DC >= 8.3.0, use the JMWE Workflow extensions administration page to build a list of your current extensions. See <u>[JMWE Workflow extensions](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461602949)</u> for details.
- Use an XML export in the workflow editor. Also, you can use [https://marketplace.atlassian.com/apps/1230311/app-usage-for-jira?hosting=datacenter&tab=overview](https://marketplace.atlassian.com/apps/1230311/app-usage-for-jira?hosting=datacenter&tab=overview).<br>- [ ] Gain a clear understanding of the feature differences between JMWE DC and Cloud. See [Migrating to Jira Cloud](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461471756) for a breakdown of migration steps.
- [ ] Review the [feature comparison](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465473954) for details on the differences between JMWE DC and JMWE Cloud, including updated post functions on JMWE Cloud. |
| 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. |
| 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** |
| --- | --- |
| 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 <u>[Post migration](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465473765)</u> page for details. |
| 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. |
| Verify migrated JMWE actions. | - [ ] Currently, [Shared extensions](https://appfire.atlassian.net/wiki/x/DoCIGw), [Event-based actions](https://appfire.atlassian.net/wiki/x/cICJGw), and [Scheduled actions](https://appfire.atlassian.net/wiki/x/3ICIGw) **are** migrated, but due to some feature differences, it is **highly recommended** that you verify these actions after migration. |
| 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.<br>- [ ] 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. |
| 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465504254)
- [ ] Ensure the “Jira Misc Workflow Extensions” add-on user in your Cloud instance is part of the following groups:<br>- `atlassian-addons-admin`
- `jira-admins-ABCD` (where `ABCD` is from your Cloud instance URL → `ABCD.atlassian.net`)
- `jira-servicedesk-users` or `jira-servicemanagement-users-ABCD` (if your Cloud instance has Jira Service Management installed), (`ABCD` is from your Cloud instance URL → `ABCD.atlassian.net`)<br>You can verify the above by running the following Nunjucks script in the <u>[Nunjucks and Jira expression tester](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465373737)</u> page of your Cloud instance:<br>```java
{{ "XXX-YYY-ZZZ" | userInfo | field("groups.items") | field("name") }}
```<br>Replace `XXX-YYY-ZZZ` above with the accountId of the “Jira Misc Workflow Extensions” add-on user in your Cloud instance (to get this info → click the “Lookup user…” button on the above tester page → select “Jira Misc Workflow Extensions” → click “Insert accountId”)<br>![image-20260108-111846.png](media://bcde0797-1bfe-4421-8627-75b8effa19b9)<br>If the JMWE add-on user is not in any of the above groups, contact <u>[Atlassian Support](https://support.atlassian.com/contact/#/)</u> to add the user to the required groups. |
| 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](https://appfire.atlassian.net/wiki/x/FADLGw)