Cloud Migration Resources
Planning a Jira Cloud migration? These resources can help you get started:
→ JSU Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
Migrating with the Jira Cloud Migration Assistant (JCMA)
This information is correct as of August 2025.
JSU Automation Suite for Jira Workflows (JSU) is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA) for app migrations. This means that you can automatically migrate most of your JSU workflow automations from your Server or Data Center instance to your Cloud instance.
It is highly recommended that you test your migration on a staging Cloud instance so you can become familiar with the results before proceeding with a migration of your Server or Data Center app data to your production Cloud instance.
You should also review our feature parity page, particularly the references to Screen Security Configuration on Jira Cloud and the behavior of the Perform As User feature in JSU Cloud.
How to navigate to the Jira Cloud Migration Assistant add-on
It is recommended to always use the latest available version of the Jira Cloud Migratio ‘Assistant (JCMA)’ section of the Jira administration settings.
Select Administration > System.
Under IMPORT AND EXPORT in the left sidebar, select Migrate to cloud. The Migration Assistant home page is displayed.
Before you can commence a migration, you need to complete the steps outlined in the JCMA tool to assess and prepare your apps. This guide will give a brief overview of how to do this with JSU. It is highly recommended to become familiar with Atlassian’s 
Jira Cloud Migration Assistant | Atlassian Support while preparing your instance and other apps for a Cloud migration.
How to include JSU in your app assessment
Assess your apps: Select which apps you want to include in your migration. All apps must have a decision status selected before you can proceed to the next step.
Select View app assessment.
Find JSU in the list of apps and select Needed in Cloud from the Status dropdown.
When you’re happy to proceed, select Done.
Prepare your apps: Next, follow the prompts to link your Jira Cloud instance to the JCMA tool.
Select Begin preparing on the Prepare your apps panel on the Migration Assistant home page.
Select the required destination Cloud site, then select Choose cloud site to link your chosen cloud instance.
Select Continue to navigate through the remaining preparatory steps, then click Done.
Migrate your data
When you are ready, go to the Migrate your data panel on the Migrations Assistant home page and select Create a migration to begin your migration activity. If you have already performed a migration, you can select Create a migration on the Migrations dashboard page.
Select Connect to cloud.
Select the Choose what to migrate option.
Edit the options as required. For the Apps option, select All to ensure JSU is included in your migration activity.
Select Run pre-migration checks.
The migration assistant displays the results of all the pre-migration checks. Expand the relevant check to review any possible issues.
Under Apps, select View app vendor checks.
JSU has implemented two app vendor checks to help your JSU data migrations run smoothly.
JSU’s vendor check is compatible with JCMA versions earlier than 1.9.5, or with version 1.9.14 and later. SeeApp vendor checks | Atlassian Support to learn more about app vendor checks. Follow the steps to resolve any issues before proceeding, or download a report to help with post-migration cleanup as described in the next sections.
Select Continue to move to the Review stage of your migration, then when you are ready, select Run to commence your Cloud migration which includes your JSU app data.
Reviewing the status of your migration
After starting the migration, you can review its progress by returning to the Migrations dashboard. Your Jira data will be migrated first, followed by your app data.
Click View details to see more information about the migration activity.
The app-migration stage is the last step of the migration activity. Once this stage is complete, you can expand to view more information, including a link to the JSU Cloud Post-Migration Report.
The post-migration report will show a summary of INCOMPLETE if any warnings or errors were found during the migration. JSU relies on the JCMA tool to move across any workflows, resolutions, transitions, etc., to configure your workflow rules correctly on your cloud site.
Post-migration report and cleanup
Click the link in the expanded section to open a new tab with your post-migration report for this specific migration. To view any of your post-migration reports on your cloud instance, go to Admin Settings > Apps > JSU Automation Suite for Jira Workflows > Reporting.
The examples on this page were created using our original beta Migration report.
From January 2023, our Migration report contains additional details and features to help you to identify and resolve any problems with your workflows post-migration. You can see an example of the new report is in our release documentation.
The report now includes:
The rule name, workflow, and transition with links to take you directly to the appropriate pages in your Jira instance.
Sortable columns to help you organize the issues in a way that suits you best
A Resolved checkbox to help you keep track of problems as they are fixed
Looking at the post-migration report, we can see there are two warnings reported: one Missing resolution and one Missing transition.
These are because JSU couldn’t find a specific resolution and transition required to configure some features correctly on the cloud instance. This specific scenario is likely to be caused by one of three scenarios:
The JCMA tool didn’t migrate that specific resolution and transition for unknown reasons
The JCMA tool didn’t migrate that specific resolution and transition because they already exist on the Cloud site but with different IDs
The JCMA tool migrated that specific resolution and transition but in doing so gave them new IDs which don’t match the Server configuration
At this stage, we can say that JSU has successfully performed an app-migration to the Cloud.
All that remains is the specific clean-up of workflow rules relating to any warnings identified
Let’s compare the workflow rules on both platforms: how they were originally on our Server instance and how they look after being migrated to the Cloud instance.
Server
Our server workflow contains three JSU post-functions, one of each for Linked Transition, Clear Field Value, and Update Any issue Field.
Cloud
All three have been successfully migrated to the Cloud, but the Linked Transition has a visible error.
Our Cloud post function is missing a value for the Transition field, while the Server field contains the “Done” transition.
The Missing transition warning from the post-migration report, showed that a transition with ID “31” couldn’t be found. This is likely the missing field, so let’s fix it.
First, look at the specific configuration of this post function on the Server instance compared to the Cloud instance.
Server
Cloud
On your cloud instance, edit the misconfigured post function and ensure the correct values are added to the Transition values (in our case, the same workflow with transition “Done” and ID “31”), and then click Update to save your changes.
After updating the post function, the error no longer appears. After you’ve resolved all issues on your workflow, remember to publish it.
You’ve now successfully migrated to Cloud with all of your JSU workflow rules included!
Feedback wanted!
How did your migration go? Was this guide helpful? Still have questions?
Please feel free to contact us through our support channel, and we’ll be happy to assist.
Need support? Create a request with our support team.