JCMA and Cloud Migration Tool Comparison

On this page:

1 Comparison between the Jira Cloud Migration Assistance (JCMA) and Cloud Migration Tool
- 1.1 Supported configuration
- 1.2 Feature Parity

Comparison between the Jira Cloud Migration Assistance (JCMA) and Cloud Migration Tool

Appfire’s Cloud Migration Tool and Atlassian’s Jira Cloud Migration Assistant (JCMA) can both migrate Jira Server/DC projects and their issues to Jira Cloud. Each app does it in its own way, but both offer safe and reliable migrations to Jira Cloud. This page describes the similarities and key differences between these two apps.

Supported configuration

First, let’s take a look at the configuration elements and data each of these apps can migrate:

JCMA - visit Atlassian’s What gets migrated with the Jira Cloud Migration Assistant document.
Cloud Migration Tool - visit the Supported Configuration Elements document.

Feature Parity

Now, let’s take a look at a more detailed comparison between the different features of the Cloud Migration Tool and Jira Cloud Migration Assistant (JCMA).

Features	Cloud Migration Tool paired with CMJ Cloud	JCMA

Features	Cloud Migration Tool paired with CMJ Cloud	JCMA
Jira Core configurations	Migrates all Jira Core configurations.	Migrates all Jira Core configurations.
Jira Software configurations	Migrates Jira Software configurations.	Migrates Jira Software configurations.
Jira Service Management configurations	Doesn’t migrate Jira Service Management configurations.	Migrates Jira Service Management configurations.
Advanced Roadmaps	Doesn’t migrate Advanced Roadmaps.	Migrates Advanced Roadmaps.
Archived projects	Doesn’t migrate archived projects.	Doesn’t migrate archived projects.
Issue data (standard fields)	Migrates standard fields.	Migrates standard fields.
Issue data (custom fields)	Migrates custom fileds.	Jira Server-specific custom field types not supported in the Cloud are not migrated by JCMA. For more info, check here.
Issue comments	Migrates issue comments.	Migrates issue comments.
Issue history	Migrates issue history.	Migrates issue history.
Issue attachments	Migrates issue attachments.	Migrates issue attachments.
Issue links	Migrates issue links.	Migrates issue links.
Agile boards	Migrates agile boards. Includes project boards automatically.	Migrates boards, but doesn’t update existing boards. Check the ‘Re-use existing configuration’ feature in the table for more information.
Agile boards (non-project)	Additional boards outside the project scope can be included and migrated.	Doesn’t migrate: Cross-project boards Boards not connected to the projects being migrated Boards that belong to inactive users
Filters	Migrates filters associated with boards being migrated. Doesn’t migrate filters on boards that are not migrated.	Migrates filters associated with boards being migrated. Doesn’t migrate filters on boards that are not migrated. Doesn’t update existing filters. Check the ‘Re-use existing configuration’ feature in the table for more information.
Dashboards	Can’t migrate dashboards.	Migrates dashboards.
Users	Migrates all users. Currently, can’t migrate only deactivated users because of a defect in Jira Cloud.	Can migrate active users. During the migration, inactive users in cloud are migrated as active users with site access but without any product access. This means they will not be counted as active Jira users for billing purposes. Can migrate deleted users only if they are associated with Server/DC projects being moved to Cloud, and will label them as "Former User".
Groups	Migrates groups. The group memberships of the users are not migrated.	Migrates groups.
User Transformations	Can map users using a JSON mapping file. All related configurations are updated automatically. This also includes many-to-one user mappings and a complete change of email domains and accounts.	Doesn’t offer user transformations during migration.
Group Transformations	A group can be matched to another one and all configurations are updated automatically.	Groups are not updated during migration.
User mentions	Migrates user mentions.	Migrates user mentions.
App data	We released an extension to the Cloud Migration Tool and CMJ Cloud pair called Cloud SPI. It currently allows migrating app workflows from Jira Server/DC to Cloud.	Marketplace partners (also known as app vendors) need to provide an automated migration path for the Jira Cloud Migration Assistant to migrate app data. Learn more about Jira apps with migration paths.
Create new configuration	Creates new configuration on the destination Jira site.	Creates new configuration on the destination Jira site.
Re-use existing configuration	Updates related configurations accordingly.	JCMA doesn’t change any existing configuration elements (previously migrated or not). If an entity in your migration has the same name as an entity in the destination site, a new entity will be created with the original name and a “(migrated)” tag. Learn more about how JCMA links data
Transformations	Project keys and names can be edited inline. Filters, workflows, and workflow schemes also can be renamed inline during the migration. JSON custom mapping allows editing projects, configuration elements and users during migration.	Doesn’t allow transforming configuration elements during migration.
Migration to next-gen projects	Can’t migrate a server/DC project into a next-gen project.	Can’t migrate a server/DC project into a next-gen project.
Post-migration report	Provides detailed migration report.	Provides a CSV file with migration report.

Cloud Migration Tool provides

Great capabilities for transforming configuration elements during migration. With Cloud Migration Tool’s transformations, you can achieve much more complex use cases than JCMA. Cloud Migration Tool allows you to upload a JSON file to customize how projects, configuration elements, and users will be migrated.
Learn more about the available transformations.
Data integrity - Cloud Migration Tool protects the data integrity in all cases.
Much better capabilities when there is an existing configuration on the destination Jira Cloud site. JCMA doesn’t update any existing configuration in the Cloud.
Learn more about how JCMA links data.