We’ve introduced a new security feature that assists you in reviewing the domains of your user emails and ensuring that your organization trusts them. The new feature in the Jira Cloud Migration Assistant lists all the email domains of your user base. You’ll need to review the email domains and mark those domains as trusted before migrating them. Learn how to review email domains for migration

We’ve introduced a new security feature that assists you in reviewing the domains of your user emails and ensuring that your organization trusts them. The new feature in the Jira Cloud Migration Assistant lists all the email domains of your user base. You’ll need to review the email domains and mark those domains as trusted before migrating them. Learn how to review email domains for migration

Version 1.7.4 marks the general availability version of Advanced Roadmaps migrations. Learn more about Advanced Roadmaps enhancements and bug fixes

This version also adds a new error check that will warn you if some of the Jira Service Management entities have exceeded Cloud limits.

This version also fixes some bugs:

• MIG-1169 and MIG-1171 – Jira Work Management error check preventing migration
• MIG-1092 – null value in JQL field preventing Jira Work Management migration

Also, start upgrading to Jira Cloud Migration Assistant 1.7.3 or higher. Learn more about this announcement

Version 1.7.4 marks the general availability version of Advanced Roadmaps migrations. Learn more about Advanced Roadmaps enhancements and bug fixes

This version also adds a new error check that will warn you if some of the Jira Service Management entities have exceeded Cloud limits.

This version also fixes some bugs:

• MIG-1169 and MIG-1171 – Jira Work Management error check preventing migration
• MIG-1092 – null value in JQL field preventing Jira Work Management migration

Also, start upgrading to Jira Cloud Migration Assistant 1.7.3 or higher. Learn more about this announcement

We’ve rolled out a new version of media APIs to help with your Server to Cloud migrations. This will provide a stable and reliable migration experience when migrating attachments and other media files. Learn more about this announcement.

Version 1.7.3 adds new checks on the ‘Check for errors’ screen that will:

• validate if all the issues under a project align with the issue type scheme attached with the project
• provide details about project export errors instead of showing them post migration

This version also fixes some bugs related to:

• MIG-1063 – projects not being migrated when the Service Level Agreement (SLA) goal has a default value of "No target”
• MIG-1077 – unrecognized field in the SLA
• MIG-559 – translation logic causing duplicated issue statuses after migration
• MIG-944 – automation rules failing during import

We’ve rolled out a new version of media APIs to help with your Server to Cloud migrations. This will provide a stable and reliable migration experience when migrating attachments and other media files. Learn more about this announcement.

Version 1.7.3 adds new checks on the ‘Check for errors’ screen that will:

• validate if all the issues under a project align with the issue type scheme attached with the project
• provide details about project export errors instead of showing them post migration

This version also fixes some bugs related to:

• MIG-1063 – projects not being migrated when the Service Level Agreement (SLA) goal has a default value of "No target”
• MIG-1077 – unrecognized field in the SLA
• MIG-559 – translation logic causing duplicated issue statuses after migration
• MIG-944 – automation rules failing during import

Version 1.7.1 includes improvements to the ‘Select projects’ screen:

• New filters to locate inactive projects. You can show projects that haven’t been updated in the last 30 or 90 days.
• Show 50 or 100 rows/projects per page.

This version adds:

• support to export workflow scheme conditions
• support of Custom Field User Filter to migration
• a check for epic links on issues at the epic hierarchy level and above
• a new column to the migration dashboard to show the time when the migration was created

This version fixes some bugs related to:

• MIG-880 – import errors in Jira Service Management migrations
• MIG-1053 – using version 1.6.9 of the migration assistant to migrate Jira Service Management projects
• MIG-1051 – request type fields having no translations in cloud
• MIG-1035 – editing apps selection

Version 1.7.1 includes improvements to the ‘Select projects’ screen:

• New filters to locate inactive projects. You can show projects that haven’t been updated in the last 30 or 90 days.
• Show 50 or 100 rows/projects per page.

This version adds:

• support to export workflow scheme conditions
• support of Custom Field User Filter to migration
• a check for epic links on issues at the epic hierarchy level and above
• a new column to the migration dashboard to show the time when the migration was created

This version fixes some bugs related to:

• MIG-880 – import errors in Jira Service Management migrations
• MIG-1053 – using version 1.6.9 of the migration assistant to migrate Jira Service Management projects
• MIG-1051 – request type fields having no translations in cloud
• MIG-1035 – editing apps selection

Version 1.7.0 includes improvements to ensure that the migration assistant is compatible with Jira 9.0.

Version 1.7.0 includes improvements to ensure that the migration assistant is compatible with Jira 9.0.

Version 1.6.9 fixes some bugs related to:

• MIG-1003 – Sprint Reports not showing correctly after migration
• MIG-541 – removing an error message for sprint field in the post-migration report
• The ‘Prepare your apps’ step looping between the ‘Connect to cloud’ and ‘Choose your destination cloud site’ screens
• Advanced Roadmaps plans not migrating when running SQL Server
• Archived Jira Service Management projects not being exported
• Migration being blocked when workflows aren’t configured properly
• Migrating notification schemes that relate to custom event types

Version 1.6.9 fixes some bugs related to:

• MIG-1003 – Sprint Reports not showing correctly after migration
• MIG-541 – removing an error message for sprint field in the post-migration report
• The ‘Prepare your apps’ step looping between the ‘Connect to cloud’ and ‘Choose your destination cloud site’ screens
• Advanced Roadmaps plans not migrating when running SQL Server
• Archived Jira Service Management projects not being exported
• Migration being blocked when workflows aren’t configured properly
• Migrating notification schemes that relate to custom event types

Version 1.6.8 adds a new check and recommendations for heap size in the ‘Check for errors’ screen.

Version 1.6.8 also fixes the bug (MIG-965) related to migrating all users when selecting only users and groups related to the selected projects.

This version also fixes the bug (MIG-279) related to an expired authentication token when connecting to your cloud site.

Version 1.6.8 adds a new check and recommendations for heap size in the ‘Check for errors’ screen.

Version 1.6.8 also fixes the bug (MIG-965) related to migrating all users when selecting only users and groups related to the selected projects.

This version also fixes the bug (MIG-279) related to an expired authentication token when connecting to your cloud site.

Version 1.6.7 adds support for migrating attachments only for selected projects. Breaking your attachment and project data migration into different stages can reduce downtime.

Version 1.6.7 also includes improvements for Advanced Roadmaps migrations:

• The ‘Check for errors’ screen lets you remove user-defined custom fields from the migration
• The ‘Review your migration’ screen shows the migration progress and total count of plans
• Migrate plans where a filter is an issue source
• Migrate plans which have cross-project boards as an issue source
• The post-migration report includes the number of plans that were migrated

This version also fixes some bugs related to:

• MIG-928 – support for skipping the migration of transitions
• MIG-935 – not importing the status ID from deleted statuses
• MIG-750 – missing conditions for JSU Automation Suite for Jira Workflows
• Getting an error when a duplicate user also has an invalid email

Version 1.6.7 adds support for migrating attachments only for selected projects. Breaking your attachment and project data migration into different stages can reduce downtime.

Version 1.6.7 also includes improvements for Advanced Roadmaps migrations:

• The ‘Check for errors’ screen lets you remove user-defined custom fields from the migration
• The ‘Review your migration’ screen shows the migration progress and total count of plans
• Migrate plans where a filter is an issue source
• Migrate plans which have cross-project boards as an issue source
• The post-migration report includes the number of plans that were migrated

This version also fixes some bugs related to:

• MIG-928 – support for skipping the migration of transitions
• MIG-935 – not importing the status ID from deleted statuses
• MIG-750 – missing conditions for JSU Automation Suite for Jira Workflows
• Getting an error when a duplicate user also has an invalid email

Version 1.6.6 marks the beta launch of Advanced Roadmaps migrations. You can now migrate Advanced Roadmaps plans and their associated projects, users, groups, and single-project boards. Learn more about migrating Advanced Roadmaps plans.

This version also fixes some bugs for Jira Service Management migrations:

• MIG-885 related to queues and comments failing to export
• MIG-894 related to SLAs failing to export
• MIG-896 related to approvals failing to export
• MIG-900 related to request types failing to export

Version 1.6.6 marks the beta launch of Advanced Roadmaps migrations. You can now migrate Advanced Roadmaps plans and their associated projects, users, groups, and single-project boards. Learn more about migrating Advanced Roadmaps plans.

This version also fixes some bugs for Jira Service Management migrations:

• MIG-885 related to queues and comments failing to export
• MIG-894 related to SLAs failing to export
• MIG-896 related to approvals failing to export
• MIG-900 related to request types failing to export

Version 1.6.5 marks the beta launch of Jira Service Management (formerly Jira Service Desk) migrations. You can now migrate Jira Service Management projects, users, groups, and customers. Learn more about how to migrate Jira Service Management data.

This version also fixes some bugs:

• MIG-855 related to the Done button not being clickable when using Discoverable Listener for app migration.
• MIG-814 related to apps with only Data Center and cloud versions not appearing with correct data in app assessment.

Version 1.6.5 marks the beta launch of Jira Service Management (formerly Jira Service Desk) migrations. You can now migrate Jira Service Management projects, users, groups, and customers. Learn more about how to migrate Jira Service Management data.

This version also fixes some bugs:

• MIG-855 related to the Done button not being clickable when using Discoverable Listener for app migration.
• MIG-814 related to apps with only Data Center and cloud versions not appearing with correct data in app assessment.

Version 1.6.3 adds support for app migration:

• The app migration feature is publicly available for you to migrate app data from server to cloud
• You can assess and select apps for migration based on the migration success rate of each app
• View Migration Assistant home interface changes

Version 1.6.3 also includes improvements:

• Support to migrate Version Picker and Multi-version picker types, their issue values, and their histories in issues with limitations on edge cases
• Users explicitly used in Notification Schemes are exported as well to prevent migration failures
• Fixed supported workflow rules appear as unsupported in the pre-migration report
• Now you can only export and migrate custom fields, issue types, and issue statuses that belong to the projects migrated in a plan

This version also fixes some bugs: MIG-254 and MIG-766

Version 1.6.3 adds support for app migration:

• The app migration feature is publicly available for you to migrate app data from server to cloud
• You can assess and select apps for migration based on the migration success rate of each app
• View Migration Assistant home interface changes

Version 1.6.3 also includes improvements:

• Support to migrate Version Picker and Multi-version picker types, their issue values, and their histories in issues with limitations on edge cases
• Users explicitly used in Notification Schemes are exported as well to prevent migration failures
• Fixed supported workflow rules appear as unsupported in the pre-migration report
• Now you can only export and migrate custom fields, issue types, and issue statuses that belong to the projects migrated in a plan

This version also fixes some bugs: MIG-254 and MIG-766

Version 1.5.7 adds support for URL custom field migration.

Version 1.5.7 also adds support for project picker custom field migration.

This version also fixes the bug (MIG-665) related to app migration for early access program (EAP) customers. If you are interested in joining the app migrations EAP, you can complete the EAP survey.

Version 1.5.7 adds support for URL custom field migration.

Version 1.5.7 also adds support for project picker custom field migration.

This version also fixes the bug (MIG-665) related to app migration for early access program (EAP) customers. If you are interested in joining the app migrations EAP, you can complete the EAP survey.

Version 1.5.6 includes minor improvements that enhance performance and increase reliability.

Version 1.5.6 includes minor improvements that enhance performance and increase reliability.

Version 1.5.4 adds support for the early access program (EAP) for app migrations. If you are interested in joining the app migrations EAP, you can complete the EAP survey.

Version 1.5.4 also improves how the Activated Date field in sprints is migrated from Jira versions older than 8.7.1.

This version also fixes some bugs:

• MIG-602 related to users and groups migration failure, caused by selecting the option to migrate users and groups referenced in projects in version 1.5.3
• MIG-588 related to users and groups migration failure, where selecting to migrate groups that have Jira Service Management access only will cause the migration to fail
• MIG-281 related to the history of some custom fields not being migrated

Version 1.5.4 adds support for the early access program (EAP) for app migrations. If you are interested in joining the app migrations EAP, you can complete the EAP survey.

Version 1.5.4 also improves how the Activated Date field in sprints is migrated from Jira versions older than 8.7.1.

This version also fixes some bugs:

• MIG-602 related to users and groups migration failure, caused by selecting the option to migrate users and groups referenced in projects in version 1.5.3
• MIG-588 related to users and groups migration failure, where selecting to migrate groups that have Jira Service Management access only will cause the migration to fail
• MIG-281 related to the history of some custom fields not being migrated

Version 1.5.2 includes improvements to error logging and a fix for the bug (MIG-558) that prevents table columns from sorting correctly.

Version 1.5.2 includes improvements to error logging and a fix for the bug (MIG-558) that prevents table columns from sorting correctly.

Version 1.5.1 adds support for the Users in Group condition in workflow migrations. You can find the complete list of supported workflow rules here.

Version 1.5.1 adds support for the Users in Group condition in workflow migrations. You can find the complete list of supported workflow rules here.

Version 1.5.0 includes a minor bug fix that improves performance and increases reliability. This release also fixes the bug (MIG-520) related to user migration failure.

Version 1.5.0 includes a minor bug fix that improves performance and increases reliability. This release also fixes the bug (MIG-520) related to user migration failure.

Version 1.4.9 fixes the bug (MIG-177) related to migrating boards and projects with the following:

• Multi select custom fields
• Cascading select custom fields

This release also includes a minor bug fix that improves performance and increases reliability.

Version 1.4.9 fixes the bug (MIG-512) related to Jira core only server support.

Version 1.4.9 fixes the bug (MIG-177) related to migrating boards and projects with the following:

• Multi select custom fields
• Cascading select custom fields

This release also includes a minor bug fix that improves performance and increases reliability.

Version 1.4.9 fixes the bug (MIG-512) related to Jira core only server support.

We’ve made it simpler to configure your migration options and track your progress with the new tasklist format. Through tasks, you can systematically make selections for Projects, Users and groups. The same screen also shows a summary of your selections before you proceed to check for errors.

Version 1.4.7 also fixes the bug (MIG-277) related to issues migrated with sprint history entries.Update (on 20 Jan 2021): There is a small UI bug that appears in this release where the wrong text is displayed when you first land on the "Choose your migration options" page. This is resolved once you select projects to migrate.

We’ve made it simpler to configure your migration options and track your progress with the new tasklist format. Through tasks, you can systematically make selections for Projects, Users and groups. The same screen also shows a summary of your selections before you proceed to check for errors.

Version 1.4.7 also fixes the bug (MIG-277) related to issues migrated with sprint history entries. Update (on 20 Jan 2021): There is a small UI bug that appears in this release where the wrong text is displayed when you first land on the "Choose your migration options" page. This is resolved once you select projects to migrate.

Version 1.4.6 increases the workflow rules migration capabilities from 8 types of workflow rules to a total of 32. This significant increase includes rules ranging from conditions, validators, and post-functions. You can get the complete list of supporting workflow rules and how to handle invalid rules here.This release also fixes bugs (MIG-281) related to custom field changes not getting recorded in the issue history after migration. The fixes are specific to sprint, single select, and epic link custom field.

Version 1.4.6 increases the workflow rules migration capabilities from 8 types of workflow rules to a total of 32. This significant increase includes rules ranging from conditions, validators, and post-functions. You can get the complete list of supporting workflow rules and how to handle invalid rules here.This release also fixes bugs (MIG-281) related to custom field changes not getting recorded in the issue history after migration. The fixes are specific to sprint, single select, and epic link custom field.

The ‘Review your migration’ screen allows you to view your migration data in a new structured format. It starts with highlighting whether the pre-migration checks were successful or not (includes errors and warnings). This is followed by a summary of the current migration configuration. You can then switch tabs to view details about what is included (users and groups / projects) in your migration or to download the pre-migration report, post migration report, and error logs.

This release also adds ‘Configuration items' to the pre-migration report. It lists all the custom fields and workflows that are part of the migration.

The ‘Review your migration’ screen allows you to view your migration data in a new structured format. It starts with highlighting whether the pre-migration checks were successful or not (includes errors and warnings). This is followed by a summary of the current migration configuration. You can then switch tabs to view details about what is included (users and groups / projects) in your migration or to download the pre-migration report, post migration report, and error logs.

This release also adds ‘Configuration items' to the pre-migration report. It lists all the custom fields and workflows that are part of the migration.

The new post migration report gives more details about the data migrated to your cloud site. The report includes the following:

• Summary data on what successfully migrated and what didn’t migrate
• List of items that require your attention, for example, items that were not supported via migration

Once you run the migration, you can download the post migration report (.zip file) from the ‘Review your migration’ screen.This release also adds summary data in the pre-migration report showing a list of entities that are expected to migrate and not migrate.Version 1.4.3 also fixes the following:

• MIG-263 The migration failure (error message: request to media failed”) detected while exporting attachments is now fixed.
• MIG-233 The missing issues caused due to re-importing projects with changes in sprint (active/future/closed) data in server and cloud are now handled based on the sprint data in the server as the source of truth.
• MIG-238 You can now migrate historical issues and project keys.

The new post migration report gives more details about the data migrated to your cloud site. The report includes the following:

• Summary data on what successfully migrated and what didn’t migrate
• List of items that require your attention, for example, items that were not supported via migration

Once you run the migration, you can download the post migration report (.zip file) from the ‘Review your migration’ screen.This release also adds summary data in the pre-migration report showing a list of entities that are expected to migrate and not migrate.Version 1.4.3 also fixes the following:

• MIG-263 The migration failure (error message: request to media failed”) detected while exporting attachments is now fixed.
• MIG-233 The missing issues caused due to re-importing projects with changes in sprint (active/future/closed) data in server and cloud are now handled based on the sprint data in the server as the source of truth.
• MIG-238 You can now migrate historical issues and project keys.

The new pre-migration report will help you analyze to-be-migrated data, including problems and list practical alternatives for a smooth migration process.The report includes the following:

• List of items that require your attention, for example, items that are not supported via migration
• List of users and groups that are part of the migration

You can download the pre-migration report (.zip file) from the ‘Review your migration’ screen.

Version 1.4.2 fixes the bug (MIG-271) related to failure of duplicate email check validation under the ‘Check for errors' screen.

The new pre-migration report will help you analyze to-be-migrated data, including problems and list practical alternatives for a smooth migration process.The report includes the following:

• List of items that require your attention, for example, items that are not supported via migration
• List of users and groups that are part of the migration

You can download the pre-migration report (.zip file) from the ‘Review your migration’ screen.

Version 1.4.2 fixes the bug (MIG-271) related to failure of duplicate email check validation under the ‘Check for errors' screen.

Version 1.4.1 incorporates the following changes:

• Displays the number of occurrences for the affected projects and filters during the anonymous access check under ‘Projects’ in ‘Check for errors’ screen
• Adds a column in the users and groups report specifying whether or not group membership will be preserved

Bug fix:

This version also fixes the bug related to migrating issues with fractional time estimates.

Version 1.4.1 incorporates the following changes:

• Displays the number of occurrences for the affected projects and filters during the anonymous access check under ‘Projects’ in ‘Check for errors’ screen
• Adds a column in the users and groups report specifying whether or not group membership will be preserved

Bug fix:

This version also fixes the bug related to migrating issues with fractional time estimates.

This new security check under ‘Projects’ in the ‘Check for errors’ screen will notify if projects, boards, or filters are prone to anonymous access post migration. Anonymous access means that the data will be available to the public and searchable online. You can choose whether or not to grant public access before the migration.

To review affected projects, boards, and filters, you can download the .csv file.

This new security check under ‘Projects’ in the ‘Check for errors’ screen will notify if projects, boards, or filters are prone to anonymous access post migration. Anonymous access means that the data will be available to the public and searchable online. You can choose whether or not to grant public access before the migration.

To review affected projects, boards, and filters, you can download the .csv file.

Version 1.3.6 (MIG-141) offers more control and flexibility for migrating users and groups. With previous versions only migrating all users and groups, this release enables you to migrate users and groups relevant to selected projects. Such as users and groups referenced in configuration, fields, and content of the project.

To get a consolidated list of users and groups that are ready for migration, you'll be able to download .csv file.

Version 1.3.6 (MIG-141) offers more control and flexibility for migrating users and groups. With previous versions only migrating all users and groups, this release enables you to migrate users and groups relevant to selected projects. Such as users and groups referenced in configuration, fields, and content of the project.

To get a consolidated list of users and groups that are ready for migration, you'll be able to download .csv file.Learn more about migrating users and groups with the Migration Assistant.

Version 1.3.5 fixes the bug (MIG-231) related to attachment failures during migration. This release also fixes some minor issues.

Version 1.3.5 fixes the bug (MIG-231) related to attachment failures during migration. This release also fixes some minor issues.

Version 1.3.4 supports the migration of archived projects ('Choose projects you’d like to migrate' screen) from your on-premise instance to cloud.

Version 1.3.4 fixes the following:

• Additional email validations (MIG-222) - This detects users with invalid email address domain in the ‘Check for errors’ screen.
• Null priority (MIG-136) - The issues with null priority will now successfully migrate to cloud.
• Missing comments (MIG-210) - The comments will now migrate with null characters. During the migration, the null characters are replaced with spaces.

Version 1.3.4 supports the migration of archived projects ('Choose projects you’d like to migrate' screen) from your on-premise instance to cloud.

Version 1.3.4 fixes the following:

• Additional email validations (MIG-222) - This detects users with invalid email address domain in the ‘Check for errors’ screen.
• Null priority (MIG-136) - The issues with null priority will now successfully migrate to cloud.
• Missing comments (MIG-210) - The comments will now migrate with null characters. During the migration, the null characters are replaced with spaces.

Version 1.3.3 fixes a bug (MIG-216) where project roles were not being migrated.

Version 1.3.3 fixes a bug (MIG-216) where project roles were not being migrated.

Version 1.3.1 fixes the bug related to the error message: "Unable to resolve media file ID for attachment". During an ongoing migration, if attachments are added to the exporting projects real time, the migration will no longer fail.

Also, some HTTP conflicts (status code 409) are fixed in this release.

Version 1.3.1 fixes the bug related to the error message: "Unable to resolve media file ID for attachment". During an ongoing migration, if attachments are added to the exporting projects real time, the migration will no longer fail.

Also, some HTTP conflicts (status code 409) are fixed in this release.

App assessment steps you through the assessment process to streamline your decision-making process. Assessing your apps before testing and running your migration helps reduce the potential for delays when you are ready to migrate.

You can review the apps currently being used, see which apps are available in cloud, and decide which apps to migrate using one simple tool.

With the v1.3.0 release you can now:

• install apps you have marked as ‘needed in cloud’
• review app availability
• see app usage on server
• see if migration paths exist.

App assessment helps you to identify what differences there are between server and cloud versions

Learn more about using app assessment from the user documentation here.

App assessment steps you through the assessment process to streamline your decision-making process. Assessing your apps before testing and running your migration helps reduce the potential for delays when you are ready to migrate.

You can review the apps currently being used, see which apps are available in cloud, and decide which apps to migrate using one simple tool.

With the v1.3.0 release you can now:

• install apps you have marked as ‘needed in cloud’
• review app availability
• see app usage on server
• see if migration paths exist.

App assessment helps you to identify what differences there are between server and cloud versions

Learn more about using app assessment from the user documentation here.

Version 1.2.0 introduces compatibility with Jira Data Center. This app can be installed and used on Jira Server or Data Center version 7.6 or later. Before migrating, check what data can be migrated with the Jira Cloud Migration Assistant.

Version 1.2.0 introduces compatibility with Jira Data Center. This app can be installed and used on Jira Server or Data Center version 7.6 or later. Before migrating, check what data can be migrated with the Jira Cloud Migration Assistant.

Version 1.1.5 fixes the bug identified in MIG-195

Version 1.1.4 includes minor bug fixes and improvements to error logging.

Version 1.1.3 includes minor bug fixes and preparation work for future compatibility with Jira Data Center.

Version 1.1.1 includes bug fixes and minor UI enhancements. You can now view a list of the projects selected when reviewing your migration plan.

Version 1.1.0 includes bug fixes, UI enhancements and the addition of a beta version of the app assessment feature (currently available in the Confluence Cloud Migration Assistant).

The app assessment feature is still being actively developed, and some functionality may be missing.

This release fixes some known bugs including: https://jira.atlassian.com/browse/MIG-140

This release includes fixes for some bugs found after the initial release.

This is the initial public release of the Jira Cloud Migration Assistant, allowing you to migrate individual projects from Jira Server to Jira Cloud. This version is compatible with Jira Software and Core on server only and is not compatible with Jira Service Desk or Jira Data Center. You can install it on Jira Server version 7.6 or later. Learn more about how the migration assistant works.