--- title: "Migration readiness analysis" canonical: "https://support.appfire.com/space/JMWE/3655991309/Migration%20readiness%20analysis" format: markdown --- JMWE for Jira Data Center now includes an additional tool to assist you in your migration to Jira Cloud - Migration readiness! Use Migration readiness to analyze your Data Center configurations before moving from Jira Data Center to Jira Cloud. The analysis evaluates the JMWE automations in your current instance and identifies configurations that are ready to migrate, need review, or have critical migration blockers. Migration readiness analysis does not perform a migration or change your JMWE configurations! Use the results to plan migration work before you run Jira Cloud Migration Assistant (JCMA). Note : Other issues can arise during migration that the readiness report will not identify! For example, a post function may use a custom field provided by a third party plugin - this type of issue cannot be identified until a migration is actually performed. Please test your migrations thoroughly in a sandbox instance. Open Migration readiness analysis The analysis runs against the JMWE automations available in your instance. Log into your Jira instance as an Administrator. From the Administration menu click Manage apps . Under Jira MISC WORKFLOW EXTENSIONS click Migration Readiness . The readiness tool will run automatically when you first open it - you don’t need to start it manually. It will rescan every time you access it and update accordingly. Review the migration readiness summary. See below for more information Understand the readiness summary The readiness tool (Figure 1, right) is divided into two tabs - Extensions and Actions . Extensions are any configurations (post functions, conditions, and validators) added to workflow transitions as well as Shared extensions ; Actions include Event-based actions and Scheduled actions . Each tab includes a summary of the migration effort for the JMWE configurations in your instance. Metric Description Readiness score A progress bar displaying the ratio of configurations that are ready to migrate to the total number of configurations. Total configurations Total number of JMWE configurations included in the analysis. Ready to migrate Configurations with no detected migration issues. Needs review Configurations that can migrate but require attention during or after migration. Critical Configurations that can't migrate because no supported Cloud alternative or workaround is available. Review extensions and actions Use the Extensions and Actions tabs to review individual JMWE automations and their migration findings. Both tabs include several filters to help locate your extensions: Search - Search for an extension or action by name. Statuses - Select one or more readiness statuses to filter the list. Location/Type - Select the location of the extension or type of action (Workflow, Shared extension, Scheduled action, or Event-based action). Location name (Extensions only) - Filter the list by a specific location. Projects - Select one or more projects where your extension or action is configured. Finding types - Select one or more types of finding. Options not supported - The extension or action includes options that are not supported within the equivalent JMWE for Jira Cloud extension or action. Extension not available on cloud - The specific extension does not exist in JMWE for Jira Cloud, either through deprecation or absorption into native Jira. JQL expression found - The extension or action includes a JQL expression; JQL expressions may need to be converted to Nunjucks on Jira Cloud, or they may need to be adapted for that platform. Groovy script found - The extension or action includes Groovy scripting, which is unsupported in Jira Cloud. Figure 2 - Extension findings for migration readiness Each row (Figure 2, above) shows the configuration name, related information, and readiness status. This includes: Configuration - The name of the extension or action. Click the name of the configuration to open it in a new tab. Location type and Location (Extensions only) - The type of location - Workflow, for example - and the name of the location. Type (Actions only) - The type of action. Transition (Extensions only) - If the extension is added to a workflow transition, it’s name will be listed here. Project (Actions only) - The Jira projects where the action is configured. Findings - The specific readiness findings. Click Show more to expand the details and view general remediation information. Readiness - The readiness status of the extension or action. Note: If a workflow is associated with multiple projects, JMWE displays the project names as a comma-separated list. If the list exceeds the available space, point to the ellipsis to view the complete list. If an automation has multiple findings, the table displays the first finding. Use See more or expand the row to review the remaining findings. Review a configuration Select a configuration name in the migration readiness report to open its JMWE configuration in a new tab. Review the configuration alongside its findings to determine what needs attention before or after migration. Download the analysis report Download the migration readiness report when you need to review the results offline or share the analysis with others involved in migration planning. The downloadable report can includes separate tabs for Extensions and Actions, and includes the following information: Field Description Automation ID and Name Identifies the JMWE automation. Location Type and Location The specific location of the extension and its type. Type The action type. Project The associated project or projects. Workflow Transition The associated transition for workflow extensions. Actions don't have a transition. Findings Summarizes detected migration issues, such as a script rewrite requirement or an unavailable Cloud alternative. Readiness Shows whether the configuration is Ready, Needs review, or Critical. Migration findings Findings identify known differences between your Data Center configuration and what JMWE supports in Jira Cloud. For example, the analysis can identify scripts that require rewriting or configurations that don't have a supported Cloud alternative. JMWE also identifies unsupported third-party extensions used inside shared, scheduled, or event-based actions. These third-party extensions are reported as findings for the action and aren't listed as JMWE extensions in the Extensions table. After you migrate, use the Post migration page in JMWE for Jira Cloud to address migration errors and warnings that require changes in the Cloud configuration. You are viewing the documentation for Jira Data Center . Figure 1 - Migration readiness summary