/
Migration from Data Center to Cloud

Migration from Data Center to Cloud

Owned by Technical Communications
Last updated: yesterday at 6:51 pm by Pooja Gopalnaidu

On this page:

Overview

This page explains limitations and differences between the Data Center and Cloud versions of the app.

For more information on the migration process using JCMA, refer to this page.

Limitations

The following fields are not supported during migration:

  • Username or user ID for user fields such as Assignee, Reporter, and so on

  • Specific components

  • Versions 

  • Issue security levels

  • Status

  • Labels

  • Specific values in custom fields

  • Entry substitution variable

  • Epic issue type includes

  • All the above-mentioned fields for subtask cloning

Differences between Data Center and Cloud versions of the app

The following table lists the differences between Data Center and cloud versions of the app:

Feature

Data Center

Cloud

Feature

Data Center

Cloud

Clone behavior configuration

Supports a property file based configuration.

Provides easy to use configuration screen to define clone operations that control the clone behavior.

Custom clone operations

Supports a maximum of 16.

Supports any number of clone operations.

Clone options:

  • copy attachments

  • copy watchers

  • copy worklogs

  • copy comments

  • Copy versions

  • Copy components

  • copy subtasks

  • copy subtask estimates

  • copy parent reporter

  • copy parent versions

  • copy links

  • copy epic issues

  • copy epic issue subtasks

  • copy epic issue subtask estimates

Supports all the clone options.

Supports all the clone options.

Images or any form of media added to rich text editor issue fields are copied to the cloned issue only if Copy attachments is selected. If not, a broken image is displayed in the respective field of the cloned issue.

 

Mapping fields from original issue to a new value in the target issue conditioned on original issue field values:

  • Set target project

  • Set target type

  • Set target component

  • Set target version

  • Set link type

  • Set link direction

Supports mapping all issue fields.

For more information, refer to the Mapping keys section in the Clone properties page.

Supports mapping all issue fields.

Setting standard and custom fields for subtasks

Supported.

Not supported.

Single clone conditions:

  • Projects

  • Issue types

  • Status

  • Roles

  • Project category

Supports all single clone conditions.

Supports all clone conditions except Project category.

Roles are supported based on the user groups defined on the Settings page.

Bulk clone conditions:

  • Projects

  • Roles

Supports all bulk clone conditions for Data Center only.

Roles are supported based on the user groups defined on the Settings page.

Clone properties:

  • fieldExcludes

  • fieldIncludes

  • ignoreFields

  • projectIncludes

  • issueTypeIncludes

  • retainCommentsOriginalDate

  • retainWorklogsOriginalDate

  • epicIssueTypesIncludes

Supports all clone properties.

Supports only:

  • Ignore fields (Not applicable to subtasks)

  • Field excludes

  • Project includes

  • Issue type includes

  • Keep original comment date

The Keep original comment date option should be manually selected on the Clone Plus for Jira page.

Post cloning processing

Functions as expected.

Functions as expected.

Bulk Clone

Supported.

Supported.

Localization

Not supported.

Supported in Spanish, French, German, and Italian.

Advanced field type - User Picker (multiple users)

Supported.

Supported.

Problem reporting

If you experience any problems or behavior changes that are unexpected, refer to Troubleshooting or open a ticket with us. This helps us identify and prioritize fixes and improvements.

Need support? Create a request with our support team.

Copyright © 2005 - 2025 Appfire | All rights reserved.