Use the Analyse and Assess Tool

Check out the following sections to learn how to analyse an export of a Jira instance:

Upload an export to assess and analyse

Follow these steps to start using the Analyse and Assess tool.

Create or get a script export from the Jira instance with ScriptRunner you want to work with.
Tip: See the Script Registry export from ScriptRunner for Jira Data Center documentation for details on how to create a script export.
Open the ScriptRunner Migration Suite, and log in with your Atlassian ID or email.
Navigate to the Analyse and Assess tool using the tile or Analyse on the left-hand menu.
Enter an Instance Name for the export.
Select a Project.
If you want to create a new project:
1. Select Projects on the left-hand navigation.
2. Select Create Project.
3. Enter a Project Name.
4. Select the Visibility of the project. You can choose to Share with organization or Only me.
5. Select Create Project.
Drag and drop or upload your script export zip file to the File field.
Select Analyse.

Your export uploads to the list. When it is finished, the Status changes to Completed.

Understand your results

Select See details on your analysis to view your results. These definitions will be helpful:

Info: Information that may be helpful to you in your migration.
Ready to Migrate: These configurations are ready for migration. They may include informational messages about possible cloud limitations, but the configuration is otherwise complete. A rewrite will still be required, but all necessary components exist in ScriptRunner Cloud.
Review Recommended: These are configurations with warnings that might not be blockers, but they do signal areas requiring script adjustments, testing, or acceptance of functional limitations in the Cloud environment.
Critical Findings: These are configurations with at least one critical blocker. The next step is to decide whether the configuration needs to be migrated to Cloud, can be migrated, or replicated differently. Blockers occur when:
- The feature is not supported in Cloud.
- Scripts rely on Java APIs or server-side features missing from Cloud's REST API-only architecture, requiring complete rewrites.
- Integrations require direct database or file system access, which cannot be migrated and need alternative solutions or may block migration.

When your results are ready and the Overview tab is selected, you will see the Migration Readiness and Feature Breakdown sections.

Tip: For more information about the Export and Bulk Convert features, visit Bulk Convert Your Scripts.

Migration readiness

The following sections help you analyse your entire export as a whole:

Overall Progress: progress bar to show how many configurations are ready for migration.
Script Breakdown: Shows how many scripts are unique and duplicated.
Critical Findings: Shows how many critical findings you have.

Feature breakdown

The second section you'll see on the Overview tab is the Feature Breakdown:

You can select one of the feature categories from See details to see more information. Once you select a feature, you'll see information focused on the migration readiness of that specific feature.

You'll still see the same progress bar with the status of scripts.

Then, for each configuration, you'll see the number of Observations, Critical findings, Review items, and a Status. To see more information, select See details.

Details

Each script overview shows the number of information messages, things to review, and critical findings.

It also includes the following tabs:

Analysis findings: Lists all messages for the configuration, along with next steps and more information.
Configuration: An overview of the selected configuration.
Script analysis: If applicable, it shows an inline review of the script for the selected configuration, displaying info, warning, and blocker messages.
Conversion output: This is where your conversion data is stored. Descriptor fragments and files are stored here.

Tip: These findings are tagged with an Info, Review, and Critical.

Info: Helpful information for your migration.
Review: These are configurations with warnings that might not be blockers, but they do signal areas requiring script adjustments, testing, or acceptance of functional limitations in the Cloud environment.
Critical: These are configurations with at least one critical blocker.

On the Analysis Findings tab of the configuration, you'll have options for next steps:

Explain this configuration: Select this for a detailed explanation of the script.
Convert this configuration: If applicable, you can select Convert this configuration to attempt to convert the Data Center script to a Cloud script.

Note: Selecting Explain the configuration or Convert this configuration moves you into the ScriptRunner Migration Agent.

Export your results

Use the Export button on the main analysis page to export your scripts to a PDF report or the Dev and Deployment Tool.