Smoother journeys to Jira Cloud with updated pre-flight checks

[#1]

Update notice

• Pre-flight check update: This blog serves as an update to the previous pre-flight check workflow.
• Combining Jira Work Management and Jira Software: For further details on the announcement of combining Jira Work Management (also known as Jira Core) with Jira Software, and other updates from Team '24, please visit this blog.
  • Impact on Jira Work Management: For more information on how this change affects Jira Work Management, please refer to this FAQ page.

If you haven’t heard, we’ve unified Jira Work Management and Jira Software into a single cloud product, Jira.

Because they were separated, migrating self-managed Jira products to cloud required matching products in both the host and destination sites.

With this unification, you can now easily migrate all Jira content simply using the Jira Cloud Migration Assistant (JCMA), allowing you to get up and running in Jira Cloud even faster.

What's New?

JCMA versions older than 1.12.6: Pre-flight checks for Jira Work Management availability will now pass automatically, allowing your migration to proceed.

JCMA versions 1.12.6 and newer: No pre-flight check for Jira Work Management availability is needed. Your migration can proceed without this check.

Now, you can migrate self-managed Jira products seamlessly without a Jira Work Management pre-flight check or assigning Jira Work Management product access permissions during your migration.

ℹ️ Migrated groups that had access only to Jira Work Management in the self-managed instance, and no other Jira products, will need their product access permissions updated to ensure they can access Jira Cloud. Please view our support documentation to learn how to identify affected groups.

For additional information and guidance on migrating to Jira Cloud, please view our migration resources, or reach out to our support team. Thank you!